Summary and recommendation
Scrut Automation does not publish a public REST API, developer documentation portal, or confirmed SCIM endpoint as of this research.
All findings reflect the absence of public documentation rather than confirmed negative capability.
SCIM provisioning is reported to be available on Enterprise plans, but endpoint URLs, supported operations, and attribute mappings are not publicly documented and must be obtained directly from Scrut's support or customer success team.
Any automated user lifecycle management should be treated as unverified until confirmed under an active Enterprise agreement.
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 for user-management events found in official Scrut documentation.
Alternative event strategy: SSO/SAML-based identity federation via Okta or Azure AD/Entra is the documented path for automated user lifecycle management.
SCIM API status
- SCIM available: No
- SCIM version: Not documented
- Plan required: Enterprise
- Endpoint: Not documented
Limitations:
- No publicly documented SCIM endpoint URL or SCIM API reference found in official Scrut help or developer docs.
- Context data indicates SCIM provisioning may be available on Enterprise plans via Okta or Entra ID connectors, but no official documentation confirms endpoint details, supported operations, or attribute mappings.
- Customers should contact Scrut support or their account team to obtain SCIM configuration details under an Enterprise agreement.
Common scenarios
The only documented path for automated user lifecycle management in Scrut is SSO/SAML-based identity federation via an IdP such as Okta or Azure AD/Entra ID.
SCIM provisioning, if available, appears to be configured through IdP-side connectors rather than a self-serve Scrut developer portal.
No webhook system for user-management events is publicly documented;
event-driven automation is not a confirmed option.
Teams building an identity graph that includes Scrut should treat it as an IdP-delegated node with no confirmed direct API surface, and should validate SCIM connector availability with Scrut before committing to an integration design.
Scenario implementations are not yet verified for this app.
Why building this yourself is a trap
The primary integration trap with Scrut is assuming SCIM is self-serve: context data suggests Enterprise-tier SCIM exists, but with no public endpoint, no documented attribute mappings, and no confirmed supported operations, any implementation is blocked until Scrut's team provides configuration details.
There are no rate limit headers, no pagination specs, and no public auth reference to build against. Teams relying on Scrut as a node in a broader identity graph should flag it as a manual-confirmation dependency and avoid designing automated deprovisioning flows until endpoint details are contractually confirmed.
Automate Scrut Automation 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.
