Pagination

List endpoints return a bounded set of rows in a single { data } array. There is no cursor to follow and no meta envelope today — a list call gives you the most recent rows, up to the endpoint's cap, in one response.

The envelope

A single-object response wraps the payload in { data }. A list response is the same envelope with an array payload:

{
  "data": [
    { "id": "task_8f21", "type": "field_verification", "state": "approved" },
    { "id": "task_8f22", "type": "field_verification", "state": "matched" }
  ]
}

There is no meta object and no next_cursor — the list endpoints don't emit them.

What each list returns

• GET /v1/tasks — your org's tasks, newest first, capped at 50. It takes no query parameters, so you always get the most recent page.
• GET /v1/workers — the public worker projection for a zone. Pass limit to set how many rows come back (default 20, capped at 50), and zone_ref to filter by zone.

curl https://api.hannu.africa/v1/workers?zone_ref=lagos_yaba&limit=20 \
  -H "Authorization: Bearer $HANNU_KEY"

Cursor pagination is not yet available