- Data models: consistent field names and structures across providers
- Pagination: cursor-based pagination works the same whether the provider uses offsets, pages, or cursors
- Error formats: standardized error responses, with provider-specific details when available
Documents
Files, folders, and drives. Search, upload, and download across storage providers.
IAM
Users, groups, roles, and policies across identity providers.
Permissions Check
Verify what a user can access before your agent acts.
Pagination
Every endpoint that returns multiple records pages with a cursor, whether the provider itself uses offsets, page numbers, or cursors.integer
default:"25"
Records per page. Keep the same value for every request in a sequence, since changing it partway through invalidates the cursor.
string
Cursor for the following page. Leave it off the first request, then pass the value the previous response returned.
next to fetch the following page. A null cursor means you have reached the end of the data set.
A page can arrive with fewer records than the page_size you asked for, or with none at all, and still carry a cursor. That happens when StackOne has to filter or restructure provider requests to reach data the provider’s own API won’t return in one pass, and it returns the short page rather than holding the request open. Keep paginating until next is null.
Resources
Embed Overview
The path to embedding StackOne in your product, from setup to production.
API SDKs
Official client SDKs for the StackOne API in TypeScript, Ruby, PHP, Java, and C#.