Summary and recommendation
Corpay's public developer surface (developer.corpay.com, docs.corpay.com) is scoped entirely to financial operations - payments, FX rates, and cross-border transfer execution.
No user-management, provisioning, or identity lifecycle endpoints are publicly documented.
There is no confirmed SCIM endpoint, no documented IdP connector support for Okta, Entra ID, Google Workspace, or OneLogin, and no webhook events tied to user lifecycle.
Building an identity graph against Corpay via public API is not currently feasible without a direct partner or enterprise agreement.
API quick reference
| Has user API | No |
| SCIM available | No |
| SCIM plan required | N/A |
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 events for user lifecycle management found in official Corpay developer documentation.
Alternative event strategy: Not documented
SCIM API status
- SCIM available: No
- SCIM version: Not documented
- Plan required: N/A
- Endpoint: Not documented
Limitations:
- No SCIM endpoint documented in official Corpay developer or help center documentation.
- No IdP connector (Okta, Entra, Google Workspace, OneLogin) support confirmed in official sources.
Common scenarios
No automatable user-provisioning or deprovisioning scenarios can be constructed from public Corpay API documentation.
The API does not expose user object fields, authentication scopes for identity operations, rate limit headers, or pagination contracts relevant to account management.
Any scenario requiring programmatic user creation, role assignment, or access revocation would need to be scoped directly with Corpay's developer or enterprise sales team, as capabilities may exist behind undisclosed partner agreements.
Scenario implementations are not yet verified for this app.
Why building this yourself is a trap
The core integration trap here is assuming that because Corpay has a developer portal and API documentation, user provisioning is available programmatically - it is not, based on all public sources. Corpay's API is a financial operations API, not an identity or directory API.
Teams attempting to wire Corpay into an identity graph or automated joiner-mover-leaver workflow via API will find no supported path in public docs. Any integration built on assumptions rather than confirmed partner-tier documentation risks silent failures in access control for a platform with direct payment authority.
Automate Corpay 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.
