> ## Documentation Index > Fetch the complete documentation index at: https://docs.ergoly.ai/llms.txt > Use this file to discover all available pages before exploring further. # Hand off a task > Name exactly one of `workerId` or `slackUserId`. Handing it to the holder it already has changes nothing and answers `changed: false`. A task that is one client's work can go only to a Worker serving that client, or to a person. A closed task cannot be handed on. ## OpenAPI ````yaml /openapi.json post /api/v1/tasks/{id}/handoff openapi: 3.1.0 info: title: Ergoly platform API version: 1.0.0 description: >- Read and change one organization's own Ergoly environment. Every route is scoped to the organization the presented credential resolves to; there is no parameter that widens it. The human-readable reference is served from the same namespace at `/api/v1/docs`, behind the same credential. The namespace's front door is `GET /api/v1`, and it is deliberately absent from `paths` below. It answers without a credential — what this API is, how an organization admin mints a key, and where the reference lives — so it is the way in to this contract rather than a part of it: it has no scope, takes no parameters, and there is nothing about it for a generated client to call. Every `unauthorized` refusal carries that same URL as `error.docs`. servers: - url: https://control.ergoly.ai security: - orgApiKey: [] tags: - name: auth description: How to present a key, what it is scoped to, and what a 401 means. - name: organization description: Which organization your credential resolves to. - name: workers description: The Slack apps and bot identities in your organization. - name: eworks description: The runtime instances under a Worker — one core, one per bound Client. - name: clients description: The customers a Worker can be scoped to, and how to bind one. - name: channels description: Which Slack rooms a Worker answers in, and who it answers as. - name: tasks description: >- Tasks handed between Workers and people, scheduled jobs, their targets, and their run history. - name: jobs description: How a provisioning run is going — the other half of every 202. - name: memory description: Read and write the memory tiers an ework mounts. - name: connections description: The credentials your agents use, and the hosts they are injected on. - name: webhooks description: Inbound URLs an outside system can POST to, each of which starts a turn. - name: activity description: Your organization's audit feed. - name: usage description: Cost, turn outcomes and a per-day pulse over a window you choose. - name: errors description: The closed set of refusal codes, and what to do about each. paths: /api/v1/tasks/{id}/handoff: post: tags: - tasks summary: Hand off a task description: >- Name exactly one of `workerId` or `slackUserId`. Handing it to the holder it already has changes nothing and answers `changed: false`. A task that is one client's work can go only to a Worker serving that client, or to a person. A closed task cannot be handed on. operationId: handOffTask parameters: - name: id in: path required: true description: >- The task id. A malformed id answers 404, exactly as another organization's well-formed id does. schema: type: string description: >- The task id. A malformed id answers 404, exactly as another organization's well-formed id does. - name: Idempotency-Key in: header required: false description: >- Any unique string. A retry under the same key is answered from the first attempt's record, with `X-Idempotent-Replay: true`. The same key with a different body is a conflict. schema: type: string description: Any unique string. requestBody: required: false content: application/json: schema: type: object properties: workerId: type: string description: >- Hand it to this Worker. Exactly one of `workerId` or `slackUserId`. slackUserId: type: string description: Hand it to this person, by Slack user id. note: type: string description: A line riding the handoff — what is left, what is missing. required: [] additionalProperties: false example: workerId: 8f1c2d3e-9a4b-4c5d-8e6f-1a2b3c4d5e6f note: Needs the finance figures. responses: '200': description: Success. content: application/json: schema: type: object properties: data: $ref: '#/components/schemas/TaskChange' required: - data additionalProperties: false example: data: taskId: 5d6e7f80-91a2-4b3c-8d4e-5f60718293a4 entryId: e3f4a5b6-c7d8-4e9f-8a0b-1c2d3e4f5a6b changed: true '400': description: '`invalid_request`' content: application/json: schema: $ref: '#/components/schemas/Error' '401': description: '`unauthorized`' content: application/json: schema: $ref: '#/components/schemas/Error' '404': description: '`not_found`' content: application/json: schema: $ref: '#/components/schemas/Error' '409': description: '`conflict`' content: application/json: schema: $ref: '#/components/schemas/Error' '429': description: '`rate_limited`' content: application/json: schema: $ref: '#/components/schemas/Error' security: - orgApiKey: - tasks:write components: schemas: TaskChange: type: object properties: taskId: type: string description: The task. entryId: type: - string - 'null' description: >- The log entry the change wrote. Null when nothing changed — the task already had that holder or that state. changed: type: boolean description: False when the task was already as asked. required: - taskId - entryId - changed additionalProperties: false Error: type: object description: The one error shape. Every refusal in this namespace has it. properties: error: type: object description: The refusal. properties: code: type: string enum: - unauthorized - not_found - invalid_request - conflict - quota_exceeded - rate_limited - upstream_error - gone description: The machine-stable half. Branch on this, never on `message`. message: type: string description: Prose for a human reading a terminal. docs: type: string description: >- Where to learn how to authenticate. Present on `unauthorized` and on nothing else — it is the one refusal a caller can reach with no credential at all, so it is the one that has to say where the way in is. required: - code - message additionalProperties: false required: - error additionalProperties: false securitySchemes: orgApiKey: type: http scheme: bearer description: >- An organization-scoped API key, minted in control under Settings → API keys. Every failure to authenticate answers one identical 401: "Provide a valid organization-scoped API key or an active session." Each operation names the one scope it is filed under, `:`, where the resource is the first path segment after `/api/v1/`; a key minted today carries all 22 of them. Scopes are RECORDED — on the key and on every audit row — and are not yet enforced: no request is refused for want of one. ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.