Create a connector
Connect a Postgres source to Ardent
422 and the response body is the full preflight report — fix the failures it lists and retry.
Private-network and customer-cloud connectors
Private-network and customer-cloud connectors
environment_id and private_link_id are only valid together with use_environment: true. Add "allow_high_rtt_placement": true to accept a far-away placement despite higher latency.Authorizations
Ardent API key (sk-ard_live_… / sk-ard_test_…) or a dashboard session token.
Body
Connection details for the source database.
Connector name.
Project to create the connector in.
Service type. postgresql is the only supported value today.
Allow customer-cloud placement far from the worker region.
Source extensions to drop on branches instead of installing.
Customer-cloud environment; required when your org has more than one.
Organization to create the connector in. Inferred from your auth when omitted.
Private connection for the source database; needs use_environment.
Create the connector in a customer-cloud environment.
Response
The created connector row plus can_update/can_delete.
Connector ID.
Connector name.
Organization the connector belongs to.
Service type. postgresql today.
Whether the caller may delete this connector.
Whether the caller may update this connector.
When the connector was created.
Project the connector belongs to.
Current connector status.