# Utility catalog (/docs/api-reference/utility/get-catalog)

`GET /v1/utility/catalog`

Returns every biller with its offers, page by page, for partner inventory.

Returns `{ items, nextCursor }`, ordered by biller ID, with the search filters except `q`. Continue
with `nextCursor` as `cursor`, the same filters and the same `currency` until it is null; a page
can hold fewer billers than `limit`, even none, while `nextCursor` is not null. A cursor reused with
other filters or another currency gives 400 / 10001. The walk is not a frozen snapshot: update your copy by
biller `id`, and remove a biller only when a complete walk did not return it. On 429, wait for
`Retry-After` and request the same page again.

## Parameters

| Name | In | Required | Type | Description |
|---|---|---|---|---|
| `countryCode` | query | no | `string` | Optional ISO 3166-1 alpha-2 country filter, in either case; every country when omitted. A blank value is rejected. |
| `category` | query | no | `string` | Keep the billers of this category, for example `electricity`. |
| `serviceType` | query | no | `string` | Keep `prepaid` or `postpaid` billers. |
| `currency` | query | no | `string` | Price currency, three letters in either case; the API key's currency when omitted. An unsupported code gives 400 / 10001 at `currency`, reason `NOT_SUPPORTED`. |
| `cursor` | query | no | `string` | The `nextCursor` of the previous page; omit it for the first page. Reuse it only with the same filters and currency. |
| `limit` | query | no | `integer` | Page size, 1 to 100; default 100. |

## Responses

### 200

OK

- `text/plain`: `UtilityCatalogPage`
- `application/json`: `UtilityCatalogPage`
- `text/json`: `UtilityCatalogPage`

### 400

Invalid partner request or model validation failure.

- `application/json`: `ErrorResponse`

### 429

Too many requests from this IP address. Wait for Retry-After seconds, then send the same request again; an order keeps its Idempotency-Key and body.

- `application/json`: `ErrorResponse`

The full schemas are in the OpenAPI specification at /openapi.json.