StackAdapt User Management API Guide

Auth method: Bearer token for the tenant-specific SCIM endpoint

Setup steps

1. Confirm SCIM provisioning is enabled for your StackAdapt tenant.
2. Obtain the tenant-specific SCIM base URL and bearer token from StackAdapt support or your account team.
3. Store the bearer token in your IdP or SCIM client and send it in the Authorization header for all requests.

Provision user via SCIM

• Method: POST
• URL: {tenant_scim_base_url}/Users
• Watch out for: Endpoint URL and required attribute mapping are tenant-specific and not publicly documented by StackAdapt.

Request example

POST /Users
Authorization: Bearer <token>
Content-Type: application/scim+json
{
  "userName": "user@example.com",
  "name": {"givenName": "Jane", "familyName": "Doe"},
  "active": true
}

Response example

{
  "id": "12345",
  "userName": "user@example.com",
  "active": true
}

Deactivate user via SCIM

• Method: PATCH
• URL: {tenant_scim_base_url}/Users/{id}
• Watch out for: Confirm PATCH support and expected schema with StackAdapt before production rollout.

Request example

PATCH /Users/12345
Authorization: Bearer <token>
Content-Type: application/scim+json
{
  "Operations": [{"op": "replace", "path": "active", "value": false}]
}

Response example

{
  "id": "12345",
  "active": false
}

• Rate limits: No public rate-limit policy for StackAdapt user-management or SCIM APIs was found.

• Rate-limit headers: No

• Retry-After header: No

• Rate-limit notes: Assume tenant-level throttling may exist and confirm limits with the vendor during implementation.

• Pagination method: cursor

• Default page size: 100

• Max page size: 100

• Pagination pointer: startIndex / count

• Webhooks available: No

• Webhook notes: No publicly documented webhook system found for user-management events.

• Alternative event strategy: Not documented

• SCIM available: Yes
• SCIM version: 2.0
• Plan required: Contact Sales - pricing is fully custom; no public tier gate documented
• Endpoint: Not documented

Limitations:

• SCIM endpoint URL is not publicly documented; must be obtained from StackAdapt support or account team.
• No public documentation on supported SCIM operations (e.g., Create/Update/Deactivate Users, Group sync) found without authenticated access.
• IdP connector support (Okta, Entra ID, Google Workspace, OneLogin) not confirmed in public documentation.
• SSO prerequisite status is unconfirmed from public sources.

No API scenarios can be responsibly documented at this time.

StackAdapt publishes no API reference, no endpoint schema, no auth method details, and no rate limit or pagination specifications in any publicly accessible source.

The SCIM 2.0 signal exists, but without a confirmed endpoint URL, supported operation list, or IdP connector compatibility matrix (Okta, Entra ID, Google Workspace, OneLogin are all unconfirmed), any scenario built on current public data would be speculative.

Engage StackAdapt's support team and request a SCIM configuration guide before scoping any automated provisioning workflow.

Scenario implementations are not yet verified for this app.

The core trap with StackAdapt's API surface is the gap between signal and substance: SCIM 2.0 is listed in third-party directories, which can create false confidence that integration is straightforward.

In practice, the endpoint URL is undocumented, supported operations are unconfirmed, SSO prerequisite status is unknown, and no OAuth 2.0 or API key authentication details are publicly available.

For teams building an identity graph that spans SaaS applications, StackAdapt represents an opaque node - its user lifecycle events cannot be reliably captured, correlated, or acted on without vendor-supplied documentation. Webhooks for user-management events are also absent from any public source, removing the event-driven integration path entirely.