# Pagination

> Cursors for lists; the registry follows its own cursor.


| List | Most per call | Last page |
|---|---|---|
| `/coins`, `/accounts`, `/payouts`, `/burns`, `/rewards/assets`, a round's wallets | 200 (default 50) | `next_cursor` is `null` |
| `/registry` | 1,000 (default 200) | Always a `next_cursor`; `has_more` is false. Keep passing it to follow new coins |
| `/rewards` | 100 (default 25), newest first | `next_cursor` is `null` |

Lists take `limit` (1 to 200, default 50). When there is more, the answer has `next_cursor`: pass it back as `cursor` for the next page. On the last page `next_cursor` is `null`.

```bash
curl -H "X-API-Key: pd_YOUR_KEY" "https://payday.direct/api/v1/coins?limit=200"
curl -H "X-API-Key: pd_YOUR_KEY" "https://payday.direct/api/v1/coins?limit=200&cursor=MjAw"
```

`total` is the size of the whole filtered list.

## Exceptions

- **The registry** pages up to 1,000 a call and always returns a `next_cursor`, even when nothing is new, so a follower just keeps passing it. See [Which coins are Payday's](/developers/guides/registry).
- **`/rewards`** pages newest first up to 100 a call and returns `next_cursor` for older payouts.
- **`/payback/coins/{mint}/rounds/{n}`** pages the wallets paid in one round.