Summary and recommendation
Hippo Video does not publish a public REST API for user management as of the research date. No developer portal, API reference, or OAuth application registration flow was found in official documentation. User lifecycle operations - invite, role change, deactivation - are only accessible through the admin dashboard UI.
For teams building an identity graph across their SaaS stack, Hippo Video represents a blind spot: there is no programmatic surface to query current users, sync role changes, or confirm offboarding completion.
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 public webhook documentation found in official sources.
Alternative event strategy: User and team management is performed via the Hippo Video web UI. SSO (SAML 2.0) with Okta or Microsoft Entra ID is available on the Enterprise plan for identity lifecycle management.
SCIM API status
- SCIM available: No
- SCIM version: Not documented
- Plan required: Enterprise
- Endpoint: Not documented
Limitations:
- No SCIM provisioning support documented in official sources.
- User provisioning must be performed manually through the Hippo Video admin UI.
- SSO via SAML 2.0 is available on Enterprise plan (Okta and Microsoft Entra ID confirmed); SCIM is not offered.
Common scenarios
No API scenarios can be documented because no public user management API exists. SSO via SAML 2.
0 (Okta, Microsoft Entra ID) is available on the Enterprise plan and represents the only supported identity integration path. Webhooks are also absent from official documentation; there is no event-driven alternative to polling or manual checks.
Any integration requiring real-time user state - for example, populating an identity graph or triggering downstream deprovisioning - cannot be built against Hippo Video's current API surface.
Scenario implementations are not yet verified for this app.
Why building this yourself is a trap
The core technical risk is invisibility: without a user management API or SCIM endpoint, there is no reliable programmatic way to verify that a departed employee's Hippo Video access has been revoked. SAML SSO on Enterprise can gate login, but session behavior post-SSO-deactivation is not documented.
Teams using an MCP server with 60+ deep IT/identity integrations to orchestrate provisioning across their stack will need to treat Hippo Video as a manual exception node - no API token, no scopes, no rate limit headers to reason about, and no pagination contract to implement against.
Automate Hippo Video 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.
