Connections
Run native operation
Runs a marketplace's own operation, as a Job.
POST/v1/connections/{id}/operations/{operationKey}
Coming soon
This route is not in the API yet. This page shows what it will do. Fields, examples and the playground arrive when it ships.
Send input and, when the target is a listing, target.listingId (the Listing must belong to the Connection). The answer is 202 with the jobId: a read runs as native_operation.read and a write as native_operation.write. The result stays in the Job items.
Safety: only registered operations run. An unknown key gives 404; input with an extra field, URL, header or credential gives 400; an unsupported operation gives 422; no permission gives 403. It is never a proxy.
When it ends, operation.completed or operation.failed arrives. The event does not carry the output: read it in Job items. Use the Idempotency-Key header.
Part of Capabilities.