List catalogs

Use /catalogs/list to list existing catalogs.

List

get

List catalogs

Authorizations

rest_key

AuthorizationstringRequired

API Key Authentication

Authentication is required in order to interact with Batch's APIs.

Batch implements authentication using API Keys, that we call the "REST API Key". You can find it on your dashboard.

Please make sure that you keep this key secret. You should never use it in client apps to call APIs from there as it would easily be extractable.

How to authenticate

In order to authenticate your requests, add your REST API Key in the Authorization header and prefix it by Bearer. Example: Authorization: Bearer bcd38d9rfb38ra28.

Query parameters

fromstringOptional

A cursor for pagination across multiple pages of results. Don’t include this parameter on the first call. Use the next_from value returned in a previous response to request subsequent results.

limitinteger · min: 1 · max: 100Optional

To change the page size of results.

Default: 10Example: 20

Header parameters

X-Batch-ProjectstringRequired

The unique project key, identifying a project on the Batch platform

Example: project_0664hxvwffvbpn278gxdyhsadddqgna6

Responses

200

Successfully listed all catalogs.

application/json

get

/catalogs/list

HTTPcURLJavaScriptPython

GET /2.8/catalogs/list HTTP/1.1
Host: api.batch.com
Authorization: Bearer YOUR_SECRET_TOKEN
X-Batch-Project: text
Accept: */*

200

Successfully listed all catalogs.

{
  "catalogs": [
    {
      "name": "products",
      "fields": [
        {
          "name": "price",
          "type": "float"
        }
      ],
      "items": 42,
      "size": 4882372,
      "created": "2025-12-06T14:35:53.733Z",
      "updated": "2025-12-06T14:35:53.733Z",
      "indexing_state": "APPLIED"
    }
  ],
  "count": 5,
  "has_more": false,
  "next_from": "text"
}

Request structure

Route

The Catalog API exposes a GET endpoint that allows to list catalogs :

/catalogs/list

Headers and authentication

See Overview → Using Project APIs.

Query parameters

See API Description.

Responses

Success

If the GET to the API endpoint is successful you will receive an HTTP 200 confirmation and information about your catalogs.

{
  "catalogs": [
    {
      "name": "MOVIES",
      "items": 8807,
      "size": 7746977,
      "created": "2025-07-14T16:27:14Z",
      "updated": "2025-07-21T09:20:44Z",
      "fields": [
        {
          "name": "director",
          "type": "string"
        },
        {
          "name": "title",
          "type": "string"
        },
        {
          "name": "release_year",
          "type": "integer"
        },
        {
          "name": "cast",
          "type": "array"
        },
        {
          "name": "description",
          "type": "string"
        }
      ]
    }
  ],
  "count": 3,
  "has_more": false,
  "next_from": "676DEZREZ"
}

Pagination infos:

• next_from can be used for the next call to list to retrieve the next page

• count is only returned for the first page

Failure

If the POST data does not meet the API requirements you will receive an actionable error message. Contact us at [e-mail] if you need further support.

See the list of potential failures in the API Description.