Use pagination when you have many workspaces to improve response times and reduce data transfer. The default page limit is 10 workspaces per page.
Authentication
All API requests must include your API key in the Authorization header. Get your API token when creating a data app - see our data app creation guide for details. Finding your API token: For detailed instructions, see the API Token guide.Headers
Bearer token for API authentication. Use your API key from the data app.
Query Parameters
Enable pagination to retrieve workspaces in batches. Pass
"true" to enable pagination.Note: Query parameters are passed as strings. Use "true" or "false" (not boolean values)."true": Enable pagination with page-based retrieval (10 items per page)"false"(default): Return all workspaces in a single response
The page number to retrieve when pagination is enabled. Must be a numeric string (e.g.,
"1", "2", "3").Note: This parameter is only used when isPagination is set to "true".- Pages start at 1 (first page)
- Each page contains up to 10 workspaces
- Returns empty array if page number exceeds available pages
Response
Array of workspace objects. Returns empty array if no workspaces exist or page number exceeds available pages.
Error object if the request failed, otherwise
null for successful requests.Examples
HTTP Status Code Summary
| Status Code | Description |
|---|---|
200 | OK - Workspaces retrieved successfully |
401 | Unauthorized - Invalid or missing API key |
500 | Internal Server Error - Server error occurred |
Possible Errors
| Error Code | HTTP Status | Description | Solution |
|---|---|---|---|
INVALID_DATA_APP_API_KEY | 401 | Invalid API key | Verify your API key is correct and has proper permissions |
INTERNAL_SERVER_ERROR | 500 | Server error | Contact support if error persists |
Pagination Details
How pagination works
How pagination works
When
isPagination is set to true:- Each page returns up to 10 workspaces
- Pages are 1-indexed (first page is
pageNumber=1) - An empty array is returned when you’ve reached the end
- Use this to implement “load more” or infinite scroll patterns
- Request page 1 → Returns 10 workspaces
- Request page 2 → Returns 10 more workspaces
- Request page 3 → Returns 5 workspaces
- Request page 4 → Returns empty array (no more data)
When to use pagination
When to use pagination
Use pagination when:
- You have more than 50 workspaces
- Building user interfaces with “load more” functionality
- Implementing infinite scroll
- Optimizing for mobile or slow connections
- You have fewer than 20 workspaces
- You need all workspace data for processing
- Implementing search or filter functionality client-side
Best practices
Best practices
- Cache results: Store workspace lists client-side to reduce API calls
- Handle empty pages: Check for empty arrays to detect the last page
- Show loading states: Display loading indicators between page requests
- Error handling: Implement retry logic for failed requests
- Rate limiting: Respect API rate limits when fetching multiple pages
Quick Start: Implement Pagination
1
Implement pagination
For large workspace lists, implement pagination to efficiently fetch results page by page:

