Summary and recommendation
No public user management API has been confirmed for Manhattan Associates products.
The Manhattan Active Platform exposes REST APIs for supply chain operations (inventory, orders, shipments), but no endpoints for user creation, role assignment, or deprovisioning appear in the public developer documentation at developer.manh.com.
Native SCIM 2.0 support is unconfirmed, and no official IdP connector (Okta, Entra ID, Google Workspace, OneLogin) is listed by the vendor.
Any identity graph integration mapping users, roles, and entitlements across systems
would require a custom connector built through Manhattan's professional services or a third-party middleware layer, with no guaranteed API surface to target.
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 lifecycle events was found in official Manhattan Associates documentation.
Alternative event strategy: User provisioning and deprovisioning likely handled through direct ERP/WMS admin console or via professional services engagement.
SCIM API status
- SCIM available: No
- SCIM version: Not documented
- Plan required: Enterprise
- Endpoint: Not documented
Limitations:
- No native SCIM 2.0 support confirmed in official documentation.
- No IdP connector (Okta, Entra ID, Google Workspace, OneLogin) officially listed by Manhattan Associates.
- User provisioning appears to require manual admin configuration or custom integration via professional services.
Common scenarios
Given the absence of publicly documented user/identity endpoints, standard automated provisioning scenarios (JIT provisioning on hire, role sync on transfer, access revocation on termination) cannot be implemented against a known API contract.
SSO configuration, if supported, is handled at the enterprise contract level and is not self-serve.
If a REST-based user management API exists within the platform, it is accessible only after direct vendor engagement under an enterprise agreement
meaning integration scope, auth method, rate limits, and pagination behavior are all undisclosed and must be confirmed with Manhattan Associates directly before any build begins.
Scenario implementations are not yet verified for this app.
Why building this yourself is a trap
The core technical risk is building against an undocumented or privately disclosed API surface. Without confirmed endpoints, auth method, required scopes, or rate limit headers, any integration is fragile by design. There are no documented webhooks for user lifecycle events, so event-driven deprovisioning is not a viable pattern without custom polling logic or middleware.
Retry behavior, pagination, and error contracts are all unknown. Teams that proceed without a formal API disclosure from the vendor should treat every assumption as unvalidated and scope a discovery phase - including a direct technical review with Manhattan Associates - before committing to an identity graph integration or automated provisioning pipeline.
Automate Manhattan Associates 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.
