Tasks
GET /v1/tasks
Section titled “GET /v1/tasks”| Parameter | In | Type | Required | Description |
|---|---|---|---|---|
status | query | string | No | pending | completed | cancelled |
type | query | string | No | GODKEND_SAGSSTART | GODKEND_INKASSO | GODKEND_FOGEDRET | GODKEND_CIVILSAG | BESVAR | BESVAR_INDSIGELSE | WORKFLOW_BESLUTNING |
caseId | query | string | No | Only tasks about this case |
invoiceId | query | string | No | Only tasks about this invoice |
lang | query | string | No | da | en — language of title, description and field labels (default en) |
limit | query | integer | No | Page size, 1-200 (default 50) |
cursor | query | string | No | Opaque cursor from meta.nextCursor |
Request exampleNo request body
curl https://api.rieckflow.com/v1/tasks \ -H "Authorization: Bearer $RIECK_API_KEY"const svar = await rieck.request("GET", "/v1/tasks");{ "data": [ {} ], "meta": { "nextCursor": null }}200 What we are waiting for you to answer. The four
GODKEND_* types ARE the approval queue: a claim that waits for your yes before the case is started or the invoice goes to collection (approval: true). Each task carries its own form.fields — that is what POST …/complete is validated against. Newest first.application/jsonPossible errors 5
| HTTP | Code | Meaning |
|---|---|---|
| 400 | invalid_cursor | The cursor is malformed, expired or belongs to another list shape. |
| 401 | invalid_api_key | The API key is missing, invalid, expired or revoked. |
| 403 | api_not_included | The organisation’s plan does not include API access. |
| 403 | insufficient_scope | The key does not have the required scope. |
| 429 | rate_limited | The organisation’s rate budget is exhausted. |
GET /v1/tasks/{taskId}
Section titled “GET /v1/tasks/{taskId}”| Parameter | In | Type | Required | Description |
|---|---|---|---|---|
taskId | path | string | Yes | |
lang | query | string | No | da | en (default en) |
Request exampleNo request body
curl https://api.rieckflow.com/v1/tasks/9b2f1c1e-… \ -H "Authorization: Bearer $RIECK_API_KEY"const svar = await rieck.request("GET", "/v1/tasks/9b2f1c1e-…");{ "data": {}}200 One task in any status — answered ones included, so you can read your own answer back after a timeout instead of guessing whether the call landed.application/json
Possible errors 4
| HTTP | Code | Meaning |
|---|---|---|
| 401 | invalid_api_key | The API key is missing, invalid, expired or revoked. |
| 403 | api_not_included | The organisation’s plan does not include API access. |
| 403 | insufficient_scope | The key does not have the required scope. |
| 429 | rate_limited | The organisation’s rate budget is exhausted. |
POST /v1/tasks/{taskId}/complete
Section titled “POST /v1/tasks/{taskId}/complete”Body is { "answer": { "<field id>": <value> } } against the task’s own form.fields, validated fail-closed: an unknown field is rejected, a required field must be present. Single-use — a second call gets 409 task_not_pending. The row records that the answer came from a machine (and task.completed carries via: "api"), so a key’s decision can always be told apart from a person’s.
| Parameter | In | Type | Required | Description |
|---|---|---|---|---|
taskId | path | string | Yes |
Request exampleNo request body
curl -X POST https://api.rieckflow.com/v1/tasks/9b2f1c1e-…/complete \ -H "Authorization: Bearer $RIECK_API_KEY" \ -H "Idempotency-Key: order-2041"const svar = await rieck.request("POST", "/v1/tasks/9b2f1c1e-…/complete");{ "data": {}}200 The updated task plus
meta: outcome (approved / declined / answered), executed (did your answer set something in motion — a no never does), blocked when we may not carry it out yet, and caseId. ⚠️ executed: false with blocked still means your answer IS registered; do not call again.application/jsonPossible errors 7
| HTTP | Code | Meaning |
|---|---|---|
| 400 | invalid_idempotency_key | Idempotency-Key is missing or malformed. |
| 401 | invalid_api_key | The API key is missing, invalid, expired or revoked. |
| 403 | api_not_included | The organisation’s plan does not include API access. |
| 403 | insufficient_scope | The key does not have the required scope. |
| 409 | idempotency_conflict | The same key was used with a different request. |
| 409 | idempotency_in_progress | The same operation is currently being processed. Retry later. |
| 429 | rate_limited | The organisation’s rate budget is exhausted. |