Summary and recommendation
Pave does not publish a public REST API or developer portal for user management as of the research date.
There is no documented SCIM provisioning endpoint, no base URL for a user-management API, and no published authentication method or required scopes for programmatic access.
Any identity graph reconciliation against Pave user records cannot be driven by a native API integration at this time.
Employee data ingestion is handled exclusively through HRIS connector integrations (Rippling, BambooHR, Workday, and others).
These are connector-based syncs initiated on the HRIS side, not API- or webhook-driven from Pave.
No webhook events, rate limit headers, or pagination contracts are documented.
API quick reference
| Has user API | No |
| SCIM available | No |
| SCIM plan required | Enterprise (Workflows package) |
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 webhook documentation found in official Pave help center or developer resources.
Alternative event strategy: Pave supports HRIS integrations (e.g., Rippling, BambooHR, Workday) for employee data sync; these are connector-based, not API/webhook-driven from the Pave side.
SCIM API status
- SCIM available: No
- SCIM version: Not documented
- Plan required: Enterprise (Workflows package)
- Endpoint: Not documented
Limitations:
- No SCIM provisioning endpoint is documented in official Pave help center.
- SSO via Okta requires the Workflows package subscription but does not include SCIM user provisioning per available documentation.
- User lifecycle management is handled through connected HRIS integrations, not a SCIM or REST API.
Common scenarios
No supported API scenarios were identified in the research data.
Pave's integration surface is limited to HRIS connectors for employee data sync and Okta SSO (Workflows package required) for authentication.
There are no documented endpoints for user create, read, update, or deactivate operations.
Engineers needing to automate user lifecycle events or pull user roster data should contact Pave sales or support directly to determine whether any private API access is available.
Scenario implementations are not yet verified for this app.
Why building this yourself is a trap
The primary integration trap with Pave is assuming that Okta SSO availability implies SCIM provisioning - it does not. SSO via Okta is gated behind the Workflows package subscription but does not include SCIM user provisioning per available documentation.
This means an identity graph built to rely on SCIM-driven lifecycle events will have a blind spot for Pave: joiners may not be provisioned automatically, and leavers may retain access until an HRIS sync or manual intervention catches the gap.
Any integration capabilities beyond native HRIS connectors require direct engagement with Pave, introducing unpredictable lead time for automation projects.
Automate Pave 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.
