Summary and recommendation
Stitch exposes a Connect API for managing data pipeline resources - sources, destinations, and connection configurations - but this is explicitly not a user-management API.
No publicly documented endpoints exist for listing, creating, updating, or deprovisioning users or team members programmatically.
SCIM provisioning is not available;
SSO via Okta handles authentication only and does not extend to lifecycle management.
Any identity graph that tracks Stitch access state must be populated and maintained through UI-driven actions, not API calls.
API quick reference
| Has user API | No |
| SCIM available | No |
| SCIM plan required | Enterprise |
Authentication
Auth method: Not documented
User object / data model
User object field mapping is not yet verified for this app.
Core endpoints
Endpoint coverage is not yet verified for this app.
Rate limits, pagination, and events
Rate limits: Not documented
Rate-limit headers: No
Retry-After header: No
Rate-limit notes: Not documented
Pagination method: none
Default page size: 0
Max page size: 0
Pagination pointer: Not documented
Webhooks available: No
Webhook notes: No user-management webhooks documented in official Stitch documentation.
Alternative event strategy: Not documented
SCIM API status
- SCIM available: No
- SCIM version: Not documented
- Plan required: Enterprise
- Endpoint: Not documented
Limitations:
- No native SCIM support documented in official Stitch/Talend documentation.
- SSO via Okta is supported but SCIM provisioning is not confirmed as available.
Common scenarios
Because no user-management API exists, automated provisioning and deprovisioning scenarios are not supported natively.
There are no webhooks for user lifecycle events, no SCIM endpoints, and no documented REST endpoints for team member operations.
The only supported programmatic surface is the Connect API, scoped to pipeline resource management.
Teams building identity graph coverage for Stitch must rely on periodic manual audits of the Team Members UI or out-of-band data exports
no event-driven or polling-based automation path is available through official APIs.
Scenario implementations are not yet verified for this app.
Why building this yourself is a trap
The primary integration trap is conflating SSO enablement with full lifecycle automation. Okta SSO can be configured for Stitch, which handles login authentication, but deprovisioning is not propagated - a user removed from Okta retains their Stitch account until an Admin manually removes them from the Team Members page.
There is no SCIM endpoint to target, no API token scope for user management, and no confirmed Enterprise-tier API extension that changes this. Any identity graph node representing Stitch access must be treated as manually managed state, with no reliable programmatic signal for when that state changes.
Automate Stitch workflows without one-off scripts
Stitchflow builds and maintains end-to-end IT automation across your SaaS stack, including apps without APIs. Built for exactly how your company works, with human approvals where they matter.
