Summary and recommendation
Nooks does not publish a public REST API or a developer documentation portal.
No base URL, authentication method, required scopes, rate-limit headers, or pagination details are publicly documented.
SCIM 2.0 support is indicated via third-party reference data for Custom enterprise plans, but no official Nooks help article confirms the endpoint URL, supported SCIM operations, or IdP-specific connector configuration for Okta, Entra ID, Google Workspace, or OneLogin.
All integration specifics must be obtained directly from Nooks enterprise sales or support.
API quick reference
| Has user API | No |
| SCIM available | Yes |
| SCIM plan required | Custom |
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 publicly accessible Nooks help or developer resources.
Alternative event strategy: Not documented
SCIM API status
- SCIM available: Yes
- SCIM version: 2.0
- Plan required: Custom
- Endpoint: Not documented
Limitations:
- SCIM support is indicated as available on a Custom enterprise plan only; no public documentation details the endpoint URL, supported operations, or IdP-specific connector configuration.
- No official SCIM setup guide was found in the publicly accessible Nooks help center.
- IdP connector support (Okta, Entra, Google Workspace, OneLogin) is not confirmed in public documentation.
Common scenarios
Because no public user API exists and SCIM endpoint details are undocumented, automated provisioning scenarios cannot be reliably scripted without vendor-supplied configuration.
An identity graph that maps Nooks seat holders to upstream IdP identities is therefore difficult to maintain programmatically
any graph node representing a Nooks user must be treated as unverified until SCIM connectivity is confirmed and tested in a live environment.
Teams building joiner-mover-leaver automation should treat Nooks as a late-binding integration: confirm SCIM endpoint and supported operations with Nooks support before committing to an orchestration design.
No webhook events are documented, so event-driven deprovisioning triggers are not available through any confirmed public mechanism.
Scenario implementations are not yet verified for this app.
Why building this yourself is a trap
The core risk is assuming SCIM availability equals SCIM readiness. Third-party data confirms SCIM 2.0 is offered on Custom plans, but the absence of a public setup guide means IdP connector configuration, attribute mapping, and supported SCIM operations (Create, Update, Deactivate, Delete) are all unverified.
Shipping an identity graph integration against undocumented endpoints creates a brittle dependency: any undocumented field mapping or unsupported operation will surface only after contract signature and provisioning setup begins.
Pricing is fully custom and API or SCIM access is likely gated behind a negotiated contract term, so integration scope should be locked in writing before implementation starts.
Automate Nooks 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.
