Axure RP User Management API Guide

Auth method: Not documented

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

Endpoint coverage is not yet verified for this app.

• 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: Axure Cloud supports outbound activity notifications to Slack and Microsoft Teams (via Teams Workflows/incoming webhook URLs) for project discussion and check-in events, but these are end-user notification integrations, not a programmable webhook system for user lifecycle events. No user-management webhook API is documented.

• Alternative event strategy: Configure SAML 2.0 SSO with Okta or Azure AD for identity-provider-driven user lifecycle management. For on-premises deployments, Active Directory or LDAP integration is available via the admin UI.

• SCIM available: No
• SCIM version: Not documented
• Plan required: Not available on any plan as of February 2026; no native SCIM provisioning is documented by Axure.
• Endpoint: Not documented

Limitations:

• No SCIM endpoint is published in official Axure documentation.
• User provisioning must be performed manually via the Axure Cloud for Business admin UI (Members page) or via SAML JIT if the IdP supports it.
• Active Directory and LDAP integrations are restricted to on-premises Axure Cloud for Business server deployments only.
• SAML SSO (Okta, Azure AD) is available on Business/Enterprise plans but does not include automated SCIM provisioning.

The only supported path for reducing manual provisioning overhead is SAML 2. 0 SSO via Okta or Azure AD, available on Business and Enterprise plans.

SAML JIT can provision a session on first login if the IdP is configured correctly, but it does not handle deprovisioning - removing a user from Okta or Azure AD does not deactivate their Axure Cloud for Business account. Admins must still manually deactivate users in the Members page.

For on-premises deployments only, Active Directory and LDAP authentication are available via the admin UI. When AD/LDAP is enabled, SAML settings are ignored - the two cannot coexist on the same server.

Teams requiring automated provisioning across their SaaS portfolio should evaluate an MCP server with ~100 deep IT/identity integrations, as Axure's native API surface does not support programmatic user lifecycle management in any form.

Onboard a new team member via SAML SSO (Okta)

1. 1. In Okta Admin Console, create a custom SAML 2.0 app integration for Axure Cloud for Business.
2. 2. Set the ACS URL to https://[domain].axure.cloud/identity/consume and Entity ID to https://[domain].axure.cloud.
3. 3. Download the X.509 certificate from Okta.
4. 4. In Axure Cloud for Business, go to Account Settings → Authentication → Configure and enter the Okta SSO URL and upload the certificate.
5. 5. On the Members page, click 'Add members', enter the user's email, and check 'Use SSO' to assign SAML authentication.
6. 6. Assign the appropriate role (e.g., Member, Admin) before saving.

Watch out for: The user must also have or create a public Axure Cloud account separately. SSO configuration must be completed before adding SSO-enabled members, or authentication will fall back to standard password login.

Onboard a new team member via Azure AD SAML

1. 1. In Azure portal, create a new non-gallery Enterprise Application.
2. 2. Configure SAML SSO: set Identifier (Entity ID) to https://[domain].axure.cloud and ACS URL to https://[domain].axure.cloud/identity/consume.
3. 3. Download the Base64 SAML signing certificate from Azure.
4. 4. Copy the Login URL from the 'Set up Axure Cloud for Business' section in Azure.
5. 5. In Axure Cloud for Business, go to Account Settings → Authentication → Configure, paste the Login URL as Sign On URL, and upload the certificate.
6. 6. Add the user on the Members page with 'Use SSO' checked.

Watch out for: Azure AD SAML integration does not include SCIM provisioning; users must still be manually added in the Axure Cloud for Business Members page. Deprovisioning in Azure AD does not automatically deactivate the Axure account.

Deactivate a departing user (on-premises)

1. 1. Sign in to Axure Cloud for Business as Super Admin or Technical Admin.
2. 2. Navigate to Organization Settings → Members.
3. 3. Locate the user in the members table.
4. 4. Click the deactivate option for that user.
5. 5. If using AD/LDAP on-premises, also disable or remove the user from the directory to prevent re-authentication.

Watch out for: Deactivating a user in Axure Cloud for Business only prevents sign-in and publishing to that server; it does not affect the user's separate public Axure Cloud account. There is no API to automate this step - it must be done manually in the admin UI.

The primary integration trap is assuming that SAML SSO covers the full user lifecycle. It does not: SAML handles authentication, not provisioning or deprovisioning. A user removed from the IdP retains their Axure Cloud for Business account and any assigned License Portal seat until an admin manually deactivates both.

A secondary trap is the two-account architecture: the admin creates the Cloud for Business account, but the user must independently hold a public Axure Cloud account to activate their RP subscription. No API surface exists to automate or verify this linkage.

Finally, Axure Cloud's outbound notifications to Slack and Microsoft Teams are end-user activity alerts, not programmable webhooks - they cannot be used to trigger user lifecycle workflows.