Orbex ETL

Manage ETL jobs, source connections, crawlers, catalog records, and notebook or workflow runs.

Open Orbex ETL

Prepare and run a job

  1. Open Connections and configure the source used by the job. Test the connection and check resource permissions.
  2. Use Crawlers and the Data Catalog to inspect discovered metadata when that workflow applies.
  3. Create an ETL job, select its job type and script, and configure inputs, outputs, runtime, and retry settings.
  4. Run the job manually and inspect its run status, logs, and output before scheduling it.

Execution depends on configuration

Saving a job records its definition. Running a script requires the execution service and its selected data connections. Check a failed run’s returned message rather than treating a saved job as an executed transformation.

Notebook and pipeline workflows have their own runtime configuration. Source control deployment uses the declared repository paths and credentials.

API endpoints

Use your Genorbex deployment’s origin followed by the path below. Replace IDs with resources accessible to your account. Authentication and permissions are checked by each endpoint.

GET /api/orbex-etl/jobs

Lists accessible ETL job definitions.

Authentication: Genorbex account token and service/resource access; API-key support follows the endpoint’s authentication guard.

GET /api/orbex-etl/connections

Lists the configured ETL connections.

Authentication: Genorbex account token and service/resource access; API-key support follows the endpoint’s authentication guard.

POST /api/orbex-etl/jobs/{id}/run

Requests execution of an existing job; inspect the returned run status.

Authentication: Genorbex account token and service/resource access; API-key support follows the endpoint’s authentication guard.

Need help with your setup? Visit the Help Center or contact Genorbex.