not_found — Not found

What causes it

• No workflow, execution, batch, template, webhook subscription or delivery with that id is visible to this API client. Executions and batches are scoped to the client that created them, so a second client on the same account cannot see them.
• The path does not exist (`/api/v1/...` catch-all), or an artifact id is not attached to that execution ("Artifact not found.").
• `GET /batches/{id}/adverse_action_notices.zip` when no notices have been generated for any row ("No adverse-action notices have been generated for this batch.").
• A soft-deleted workflow.

How to fix it

1. List the collection with the same key and use an id from that response.
2. Check the path against the reference — ids are integers, and there is no trailing-slash tolerance on nested routes.
3. For artifacts, poll the execution until `status` is terminal; PDFs and notices attach after the run completes.

Operations that return it

Any operation can return this code, as can an unknown path under /api/v1.

See the API reference for the full list of operations.

Example response

HTTP/1.1 404 Not Found · Content-Type: application/json

{
  "error": {
    "code": "not_found",
    "message": "The requested resource was not found.",
    "details": [],
    "request_id": "6f1c2a3e-8d4b-4c5e-9f0a-1b2c3d4e5f60",
    "doc_url": "https://cascades.crscreditapi.com/docs/api/errors/not_found"
  }
}