Resources / DevelopersYour application asks.
Your application asks.
afka does the work.
Create tasks, retrieve results and receive signed events. The same permissions and approval gates apply whether a person or your code starts the work.
From request to result.
Use the task API to hand over a clear outcome. Track the task, retrieve its artifacts and bring the result back into your own application.
POST https://api.afka.ai/v1/tasks
{ "prompt": "Prepare an evidence-backed candidate shortlist" }
202 Accepted
{ "task_id": "task_5f2c", "status": "queued" }
GET https://api.afka.ai/v1/tasks/task_5f2c
{ "status": "done", "credits_spent": 412,
"artifacts": ["art_9d1e"] }A small surface.
A complete work loop.
| Request | What it does | Result |
|---|---|---|
| POST /v1/tasks | Submit an outcome for afka to work on. | Queued task and task ID |
| GET /v1/tasks/:id | Read the run and its current status. | Status, credits spent and artifacts |
| task.finished | Receive a completion event at your webhook. | Task and workspace references |
A key is never a shortcut around control.
Access
Inherits permissions
A key never has more access than the person who created it.
Read security overview ↗ApprovalThe same human gate
Sensitive actions still wait for the authorized person.
Explore approvals ↗RecordTrace the result
Follow the task and the actions behind the delivered artifact.
Explore the platform ↗Signed events. Safe retries.
POST https://your-app.example/afka/hooks x-afka-event: task.finished x-afka-delivery: d_8f3a1c9e x-afka-signature: sha256=<hex digest> expected = hmac_sha256(signing_secret, raw_body).hexdigest()
Verify the signature against the raw request bytes before parsing the body. Use the stable delivery ID to deduplicate retries. Keep signing secrets on the server.
Build on a governed work loop.
Start with one task. Expand when the result and approval path are right for your team.