Building a webhook integration? Read the webhook guide for signatures, retries, event schemas, and troubleshooting.

apiDeterministic

Submit agent artifact

POST /api/agents/work-orders/external/submit

Submit a validated external coding agent artifact to its claimed Agent Teams work order. The server verifies the live claim, bundle identity, bundle version, task type, artifact schema, and canonical evidence references, then stores the result for inspection and completes the preparation task. Submission does not approve, launch, mutate a campaign, or send outreach.

Parameters

workspaceId

string

Optional with an API key, inferred from the key.

workOrderIdrequired

string

No description.

claimTokenrequired

string

Lease token returned by claim-agent-work-order.

bundleIdrequired

string

Immutable execution bundle id returned by claim-agent-work-order.

bundleVersionrequired

number

Execution bundle version returned by claim-agent-work-order.

taskTyperequired

string

No description.

artifactrequired

object

No description.

Example

REST requestbash

curl -X POST "https://app.pipeline.help/api/agents/work-orders/external/submit" \
  -H "Authorization: Bearer $PIPELINE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"workOrderId":"00000000-0000-4000-8000-000000000000","claimToken":"00000000-0000-4000-8000-000000000001","bundleId":"aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa","bundleVersion":1,"taskType":"campaign_strategy","artifact":{}}'

Response

Success response schemajson schema

{
  "type": "object",
  "properties": {
    "workOrder": {
      "type": "object",
      "properties": {
        "id": {
          "type": "string"
        },
        "workspaceId": {
          "type": "string"
        },
        "status": {
          "type": "string"
        },
        "revision": {
          "type": "number"
        },
        "artifacts": {
          "type": "object"
        },
        "nextDecision": {
          "type": "object"
        },
        "updatedAt": {
          "type": "string"
        }
      },
      "required": [
        "id",
        "workspaceId",
        "status",
        "revision",
        "artifacts",
        "updatedAt"
      ]
    }
  },
  "required": [
    "workOrder"
  ]
}

HTTP errors

401: Missing or invalid API key.
403: Authenticated but not permitted for the workspace or resource.
404: The requested resource was not found.