Summary and recommendation
People.ai does not publish a public developer portal, REST API reference, or SCIM endpoint for user management. SSO via SAML is confirmed for both Okta and Microsoft Entra, but neither integration includes automated provisioning - the Okta OIN listing covers SAML only, and Entra SCIM status is unconfirmed in any public documentation.
All user lifecycle operations - create, update, deactivate - appear to require manual admin action or direct vendor engagement. Any internal API that may exist is undocumented and should not be relied upon in a production identity graph pipeline.
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 publicly documented webhook system for user-management events found in official sources.
Alternative event strategy: Contact People.ai enterprise sales for any available data-export or event-notification integrations.
SCIM API status
- SCIM available: No
- SCIM version: Not documented
- Plan required: Enterprise
- Endpoint: Not documented
Limitations:
- No SCIM provisioning documented publicly.
- Okta OIN listing does not include SCIM provisioning, only SSO (SAML).
- Microsoft Entra integration status for SCIM is unconfirmed in public documentation.
- Enterprise plan required per vendor context; actual availability must be confirmed directly with People.ai.
Common scenarios
No documented API scenarios are available for People. ai user management.
There are no published endpoints, no documented auth method, no rate limit specifications, and no webhook system for user-management events.
The absence of a SCIM API means that identity graph tooling - including an MCP server with 60+ deep IT/identity integrations - cannot automate provisioning or deprovisioning for People. ai without a vendor-supplied integration or middleware built against undocumented internals.
If event-driven user lifecycle management is a requirement, the only documented path is to contact People.ai enterprise sales to inquire about available data-export or event-notification integrations.
Scenario implementations are not yet verified for this app.
Why building this yourself is a trap
The primary integration trap with People.ai is assuming that confirmed SAML SSO implies provisioning support - it does not. SAML handles authentication; without SCIM, user accounts must still be created and deactivated manually, and there is no documented mechanism to sync group membership, role assignments, or deactivation events from your identity provider.
This gap breaks any identity graph that depends on real-time lifecycle signals.
A second trap is relying on any undocumented internal API discovered through network inspection. People.ai has not published API versioning, deprecation policies, or change notifications, making any such endpoint a liability in a production provisioning pipeline. Treat People.ai as a manual-only integration until the vendor explicitly documents SCIM support or provides a supported API contract.
Automate People.ai 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.
