Summary and recommendation
Teampay does not publish a public REST API, developer documentation portal, or native SCIM endpoint as of this research date.
There are no documented auth methods, OAuth app registration flows, or self-serve API key issuance.
Any programmatic access would require direct engagement with Teampay's sales or support team, and no confirmation of such access being available was found in public sources.
API quick reference
| Has user API | No |
| SCIM available | No |
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 public webhook documentation found for user lifecycle events.
Alternative event strategy: Teampay uses HR system integrations (e.g., BambooHR) and IdP connectors (Okta, OneLogin) for user provisioning/deprovisioning workflows instead of native webhooks or a public API.
SCIM API status
- SCIM available: No
- SCIM version: Not documented
- Plan required: Not documented
- Endpoint: Not documented
Limitations:
- No native SCIM support documented. User provisioning is handled via HR integrations (BambooHR) and SSO IdP connectors (Okta, OneLogin).
- No public SCIM endpoint or connector-specific SCIM URL found in official documentation.
Common scenarios
Because Teampay exposes no public user-management API, standard identity graph reconciliation scenarios such as syncing user state from an IdP, querying active seat holders, or triggering deprovisioning on termination events
cannot be implemented via direct API calls.
The supported path is indirect: configure BambooHR or an Okta/OneLogin IdP connector to push lifecycle events into Teampay.
Webhook support for user lifecycle events is also undocumented, removing the event-driven automation option entirely.
Teams building identity graph pipelines should treat Teampay as an opaque downstream system that receives state changes only through its supported HR and SSO integrations.
Scenario implementations are not yet verified for this app.
Why building this yourself is a trap
The core integration trap here is assuming that SSO support implies API-level user management - it does not. Okta and OneLogin connectors handle authentication and, to some extent, provisioning, but they do not expose Teampay user objects to external orchestration layers.
There is no pagination contract, no rate limit documentation, and no user object schema to map against an identity graph. Any automation built on undocumented or vendor-negotiated API access carries high maintenance risk and zero public support surface.
Automate Teampay 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.
