Roadmunk User Management API Guide

Auth method: API Key (Bearer token in Authorization header)

Setup steps

1. Log in to Roadmunk and navigate to Account Settings.
2. Locate the API section and generate a personal API token.
3. Include the token in requests as: Authorization: Bearer

User object field mapping is not yet verified for this app.

Endpoint coverage is not yet verified for this app.

• Rate limits: No rate-limit details are published in official Roadmunk documentation.

• Rate-limit headers: No

• Retry-After header: No

• Rate-limit notes: No rate-limit details are published in official Roadmunk documentation.

• Pagination method: none

• Default page size: 0

• Max page size: 0

• Pagination pointer: Not documented

• Webhooks available: No

• Webhook notes: No webhook support is documented in official Roadmunk help or developer docs.

• Alternative event strategy: Poll the REST API for roadmap data changes; use IdP provisioning connectors (Okta, OneLogin) for user lifecycle events.

• SCIM available: No

• SCIM version: Not documented

• Plan required: Enterprise (via Okta or OneLogin connector; no native SCIM endpoint published)

• Endpoint: Not documented

• Supported operations: Create user (via Okta connector), Deactivate user (via Okta connector), Create user (via OneLogin connector), Deactivate user (via OneLogin connector)

Limitations:

• No standalone SCIM base URL is published by Roadmunk; provisioning is only available through IdP-specific app connectors (Okta, OneLogin).
• SAML SSO must be configured before provisioning can be enabled.
• Google Workspace provisioning is not supported.
• Roadmunk has been rebranded/integrated into Tempo; documentation availability may vary.

Provisioning via Okta requires configuring SAML SSO first, then enabling the provisioning connector in the Okta app settings using SCIM credentials obtained from Roadmunk/Tempo support

there is no self-serve SCIM endpoint or public base URL.

The connector supports create and deactivate operations;

group-push behavior should be confirmed with support before relying on it in an identity graph that maps group membership to application access.

OneLogin provisioning follows the same pattern: add the Roadmunk app from the catalog, configure SAML, then enable provisioning with support-issued credentials.

Both IdP paths share the same constraint - no public SCIM URL, no direct API user management, and a hard SSO prerequisite.

For roadmap data access, GET requests to /v1/roadmaps with a Bearer token return roadmap and item objects.

This is the only programmatic surface available;

it carries no user-management capability and should not be used as a substitute for IdP-driven lifecycle events in any identity graph implementation.

Provision users via Okta

1. Configure SAML SSO for Roadmunk in Okta using the official Roadmunk Okta app.
2. Enable provisioning in the Okta app settings and enter the SCIM connector credentials provided by Roadmunk support.
3. Assign users or groups in Okta; the connector will create/deactivate accounts in Roadmunk automatically.

Watch out for: The SCIM connector endpoint and credentials are not self-serve; contact Roadmunk/Tempo support to obtain them. SSO must be active first.

Provision users via OneLogin

1. Add the Roadmunk app from the OneLogin app catalog.
2. Configure SAML SSO settings, then enable provisioning in the app configuration.
3. Assign users or roles in OneLogin to trigger provisioning to Roadmunk.

Watch out for: Same constraint as Okta: no public SCIM URL; provisioning credentials must be obtained from Roadmunk/Tempo support.

Access roadmap data via REST API

1. Generate an API token from Roadmunk Account Settings.
2. Make GET requests to https://api.roadmunk.com/v1/roadmaps with Authorization: Bearer .
3. Parse returned roadmap and item objects for integration use cases.

Watch out for: This API does not expose user-management operations. It is scoped to roadmap content only.

The primary integration trap is assuming the REST API can serve double duty for both roadmap data and user lifecycle management - it cannot. Any identity graph that models Roadmunk user state must route all provisioning signals through the Okta or OneLogin connector layer, not the REST API.

A secondary trap is treating provisioning as self-serve: the SCIM connector credentials are not exposed in the UI and require a support request, introducing lead time into any automated onboarding workflow.

Additionally, Roadmunk's ongoing integration into Tempo means documentation URLs may redirect or become unavailable, making long-term API contract stability a risk worth flagging in any integration design.