POST /tasks/requests/{id}
Updated Oct 1, 20261 minute read
Put a request on the board
The card carries the report's words, its priority and whichever tracker issues the report already holds. From here on the two move together, so marking the card done is what tells everybody who asked for it.
Part of Tasks.
Parameters
| Name | In | Type | Required | Description |
|---|---|---|---|---|
id | path | string | Yes | A signal id. |
Request body
application/json, optional.
| Field | Type | Required | Description |
|---|---|---|---|
status | "requests" | "planned" | "in_progress" | "in_review" | "done" | No |
Responses
| Status | Description |
|---|---|
200 | The card. |
400 | The request is malformed, and the message names the field. |
401 | The bearer token is missing, revoked, or expired. |
404 | Not one of yours, or not there at all. |
409 | It already exists, or it was already settled. |
429 | Too many requests. Wait the seconds in Retry-After. Limits depend on the plan. See rate limits. |
200 body
| Field | Type | Required | Description |
|---|---|---|---|
id | string | No | |
key | string | No | |
number | integer | No |
Example response
{
"id": "k97a2fh3m1x8p4qv6r2t9w5y",
"key": "MED-12",
"number": 12
}Example request
curl -X POST https://api.median.sh/v1/tasks/requests/id \
-H "Authorization: Bearer $BEARER_AUTH"