API Referencev1

Runs, schedules and deployments API

Start and inspect flow runs, manage schedules and the dead-letter queue, deploy flow versions and decide approvals.

Updated 07/10/2026

On this page

All paths start with /api/console/connect unless shown otherwise, and need a session token.

Executions (runs)

POST /flows/:flowId/executions (connect.flow.execute)

json
{
  "environment": "sandbox",
  "idempotencyKey": "orders-2026-10-07T09:00",
  "correlationId": "scheduler-run-8841",
  "triggerType": "manual"
}
FieldNotes
environmentsandbox or production. Production needs an approved, active deployment (otherwise 403).
idempotencyKey, correlationIdRequired, 8–160 characters of A-Z a-z 0-9 . _ : -
triggerTypemanual, schedule or retry
triggerReferenceOptional

Returns the execution with status: "queued" and replayed: false. Replaying the key returns the original execution with replayed: true; reusing it for another flow or environment returns 409.

MethodPathPermissionDescription
GET/executionsconnect.execution.readFilters flowId, status; pageSize 1–100 (default 50)
GET/executions/:idconnect.execution.readExecution with steps, errors, executionMode and recovery (eligible and scheduled retries)
GET/executions/:id/stepsconnect.execution.readStep results
GET/executions/:id/recordsconnect.execution.readUp to 1,000 records
GET/executions/:id/records/:recordIdconnect.execution.readOne record with steps, errors and dead-letter state
POST/executions/:id/cancelconnect.execution.cancelRequests cancellation of an in-progress run
POST/executions/:id/retry-failedconnect.execution.retryRetries up to 100 open dead-letter records from the run
GET/monitoring/summaryconnect.monitoring.read24-hour summary: connections, executions, open dead letters, pending outbox events, enabled schedules

Schedules

MethodPathPermissionBody and notes
POST/flows/:flowId/schedulesconnect.schedule.manage{cronExpression, timezone?, name?, enabled?}. Five-field cron; time zone defaults to UTC.
GET/flows/:flowId/schedulesconnect.integration.readSchedules for the flow
PATCH/schedules/:idconnect.schedule.manageSame fields, all optional
POST/schedules/:id/pauseconnect.schedule.managePauses the schedule
POST/schedules/:id/resumeconnect.schedule.manageResumes it
DELETE/schedules/:idconnect.schedule.manageReturns {deleted: true}

Dead letter

MethodPathPermissionBody and notes
GET/dead-letter?status=connect.dead_letter.readUp to 500 records with error and execution record
GET/dead-letter/:idconnect.dead_letter.readOne record
POST/dead-letter/:id/retryconnect.dead_letter.manage{idempotencyKey?}. Only open and retry_failed records.
POST/dead-letter/retryconnect.dead_letter.manage{ids: [...]}, 1–100 IDs
POST/dead-letter/:id/ignoreconnect.dead_letter.manage{note?} (up to 1,000 characters)
POST/dead-letter/:id/resolveconnect.dead_letter.manage{note?}

Environments and deployments

MethodPathPermissionBody and notes
GET/integrations/:id/environmentsconnect.deployment.readThe integration's environments
POST/integrations/:id/environmentsconnect.deployment.manage{key, displayName, lifecycle: development, test, staging or production, connectionBindings?, runtimeSettings?}
GET/environments/:id/revisionsconnect.deployment.readDeployment revisions
POST/environments/:id/revisionsconnect.deployment.manage{flowId, flowVersionId, configuration?}. The version must be published.
POST/deployment-revisions/:id/decisionconnect.deployment.approve{decision: approved or rejected, comment}. 409 for self-approval.
POST/deployment-revisions/:id/activateconnect.deployment.manageActivates an approved revision
POST/deployment-revisions/:id/rollbackconnect.deployment.manageRolls back to the previous revision

A rejection comment must be 3–500 characters.

Approvals

These paths start with /api/console/approvals.

MethodPathPermissionBody and notes
GET/api/console/approvals?status=approvals.manage, or approvals.request for your own requestsUp to 100 requests
POST/api/console/approvalsapprovals.requestSee the request fields below
POST/api/console/approvals/:id/decisionapprovals.manage{decision: approved or rejected, reason} (3–500 characters). 403 for self-approval; 400 if expired.
POST/api/console/approvals/:id/cancelRequester or manager{reason}

An approval request has these fields:

FieldNotes
actionRequired
resourceTypeconnector_action, mcp_tool or credential_action
resourceIdOptional
environmentsandbox or production
payloadRequired
idempotencyKey, correlationIdRequired
expiresInMinutes1–1,440, default 30
requiredApprovals1–5, default 1

Trading partners (EDI)

/trading-partners manages B2B partners, their SFTP or AS2 channels, document profiles and documents:

profiles: X12 004010 850 and 810, EDIFACT D96A ORDERS, and CSV v1;

permissions: connect.partner.read to read and connect.partner.manage to write.

MethodPathBody
GET/trading-partners—
POST/trading-partners{name, partnerType?, identifiers?, dataClassification?}
GET/trading-partners/:id—
POST/trading-partners/:id/channels{channelType: sftp or as2, direction, configuration, secretReference}
POST/trading-partners/:id/profiles{standard, version, documentType, direction, validationRules?, mapping?}
POST/trading-partners/:id/documents{profileId, direction, payload, externalId?, storageReference?}
POST/trading-partners/:id/documents/:documentId/deliveries{channelId}

Need a hand?

Ask Nexra AI for implementation steps or error guidance.

Ask Nexra AI