Mixedbread

Pagination

Overview

Mixedbread API uses cursor-based pagination for endpoints that return large result sets. This approach provides consistent performance regardless of dataset size and ensures reliable pagination even when data is being modified.

Supported Endpoints

Cursor-based pagination is used for:

Pagination Parameters

Request Parameters

Include these query parameters in your requests:

ParameterTypeDescriptionDefault
beforestringCursor for pagination. Returns items before this cursor.-
afterstringCursor for pagination. Returns items after this cursor.-
limitintegerMaximum number of items to return (1-100).20

Important Notes:

  • Use either before OR after, not both
  • Cursors are opaque strings - don't parse or modify them
  • Always include limit to control result size

Response Format

All paginated responses include:

{
  "data": [...],
  "pagination": {
    "first_cursor": "eyJpZCI6InZzXzEyMyJ9",
    "last_cursor": "eyJpZCI6InZzXzQ1NiJ9", 
    "has_more": true
  }
}
FieldTypeDescription
dataarrayThe actual results for the current page
first_cursorstringCursor pointing to the first item in current page
last_cursorstringCursor pointing to the last item in current page
has_morebooleanWhether more results are available

Forward Pagination

Start with no cursor to get the first page:

GET /v1/vector-stores?limit=10

Continue with last_cursor from the previous response:

GET /v1/vector-stores?after=eyJpZCI6InZzXzQ1NiJ9&limit=10

Backward Pagination

Use first_cursor with before parameter:

GET /v1/vector-stores?before=eyJpZCI6InZzXzEyMyJ9&limit=10
Rate Limiting
Documentation on API rate limits with tier-based quotas. Learn about request limits, how to handle rate limiting responses, and strategies for optimizing your API usage.
Error Handling
Documentation on error handling with the Mixedbread API. Learn about common status codes, how to handle them, and best practices for error handling.

Last updated: July 12, 2025