Stensul API (1.0.0)
Download Postman Collection: Download
This API uses OAuth 2.0 for authentication and adheres to the SCIM (System for Cross-domain Identity Management) protocol for user management.
This documentation is organized into the following structure:
- Authentication: Includes the OAuth request for authentication.
- Libraries: Stensul's Libraries endpoints (Not part of the SCIM specification).
- Emails: Stensul's Emails endpoints (Not part of the SCIM specification).
- Images: Stensul's Images endpoints (Not part of the SCIM specification).
- SCIM - User Provisioning: SCIM User Resource CRUD endpoints.
- SCIM - Group Provisioning: SCIM Group Resource CRUD endpoints.
- SCIM - Schemas: SCIM Schemas.
- SCIM - Resource Types: SCIM Resource Type list and User/Group type description.
- SCIM - Configuration: SCIM Service Provider Configuration endpoint.
- SCIM - Bulk Actions: SCIM Bulk Actions
Our API implements rate limiting to ensure fair usage and prevent abuse. Specifically, we limit requests to 30 per second per IP address. This helps us maintain the stability and performance of our API by preventing any single IP address from overwhelming our servers with too many requests. Rate limiting also encourages responsible use of our API and helps protect it from potential malicious attacks.
Every endpoint optionally accepts an X-ST-Origin header declaring which integration is making the call. It is used for usage metrics only — it never changes the behaviour of a request and is never returned in a response.
Accepted values: builder, figma, mcp, genstudio, unknown. When the header is absent, the origin is derived from the OAuth client that authenticated the request. An unrecognised value is ignored and the derived origin is used instead, so a malformed header never fails a call.