Summary and recommendation
Criteria does not publish a public REST API, developer documentation portal, or self-serve API key mechanism as of this research date.
There is no confirmed OAuth 2.0 flow, token-based auth, or publicly documented endpoint for user management operations.
All integration surface area observed in official sources is limited to pre-built ATS/HRIS connectors (Greenhouse, Lever, Workday), which are managed by Criteria's team - not by the consuming developer.
Any attempt to build programmatic user lifecycle management against Criteria would require direct engagement with their enterprise sales or support team to determine whether a private API exists and under what contractual terms it is accessible.
For teams building an identity graph across their SaaS portfolio, Criteria represents a blind spot: without a user API or SCIM endpoint, there is no reliable machine-readable source of truth for who has access, what role they hold, or when that access was last active.
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 found in official Criteria Corp documentation.
Alternative event strategy: Criteria Corp offers pre-built ATS/HRIS integrations (e.g., Greenhouse, Lever, Workday) for candidate and assessment data flow. Contact Criteria Corp sales/support for integration options.
SCIM API status
- SCIM available: No
- SCIM version: Not documented
- Plan required: Enterprise
- Endpoint: Not documented
Limitations:
- No public SCIM documentation found in official help center or developer docs.
- Context data indicates no native SCIM support; Enterprise plan noted as a requirement if/when available.
- No IdP connector support (Okta, Entra, Google Workspace, OneLogin) confirmed in official sources.
Common scenarios
No API scenarios can be documented from available data.
Criteria does not expose endpoints for user creation, deactivation, role assignment, or license enumeration through any publicly documented mechanism.
The pre-built connector ecosystem (ATS/HRIS) handles candidate and assessment data flow, but this is distinct from identity or access management.
If Criteria surfaces a private API under enterprise agreements, scenarios for provisioning and deprovisioning could be constructed - but that would require vendor-supplied documentation not available in current sources.
Scenario implementations are not yet verified for this app.
Why building this yourself is a trap
The core risk is assuming that because Criteria offers ATS integrations, user access management is also automated - it is not. Those connectors move assessment and candidate data, not identity lifecycle events. There is no SCIM endpoint, no webhook system for access events, and no public API to poll for user state.
This means Criteria cannot be enrolled in a standard IGA or SCIM-based provisioning workflow without a custom arrangement negotiated directly with the vendor. Teams that skip this verification step may discover orphaned accounts only during an access review, at which point manual remediation is the only path.
The absence of rate limit headers, pagination contracts, and auth documentation further signals that no self-serve API path is intended for this use case.
Automate Criteria 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.
