Summary and recommendation
Champify does not publish a public API reference, developer documentation, or SCIM endpoint as of the research date.
No user-management endpoints - create, read, update, deactivate - have been confirmed in any official or third-party source.
Auth method, base URL, rate limits, pagination behavior, and supported scopes are all undocumented publicly.
Any assumption about API-driven provisioning should be treated as unverified until confirmed directly with Champify.
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 webhook documentation found in any official or developer source.
Alternative event strategy: Not documented
SCIM API status
- SCIM available: No
- SCIM version: Not documented
- Plan required: N/A
- Endpoint: Not documented
Common scenarios
Because no public user API exists, there are no confirmed programmatic scenarios for provisioning or deprovisioning Champify users.
CRM integrations (Salesforce, HubSpot) appear to be the primary data ingestion path, but these operate on lead and contact data - not on identity or access management.
For teams building an identity graph that maps user access across the SaaS stack, Champify represents a gap: there is no API surface to query for active users, roles, or last-login signals, which means the identity graph cannot be kept current for this app without manual reconciliation.
Scenario implementations are not yet verified for this app.
Why building this yourself is a trap
The core risk is assuming that Champify's CRM connectivity implies broader API capability - it does not. Salesforce and HubSpot integrations move pipeline data, not user identity data. There are no confirmed webhooks, no OAuth flow, and no SCIM version documented.
Any engineering effort scoped against a hypothetical Champify user API should be blocked until the vendor confirms a supported endpoint in writing; building against undocumented behavior in a closed system creates brittle dependencies with no upgrade path.
Automate Champify 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.
