Skip to main content
Okta logo

Overview

Add Okta to any ModuleX agent or workflow. Manage users and user-type metadata in an Okta tenant via the Okta Management REST API (https://<subdomain>.okta.com/api/v1).
Categories: Developer Tools & Infrastructure · Identity & Access Management · Productivity & Collaboration · Auth: Okta API Token · Actions: 4

Authentication

Okta API Token

Authenticate with an Okta SSWS API token plus the tenant subdomain. The token is sent as Authorization: SSWS &lt;token> and the subdomain is used to build the request host (https://&lt;subdomain>.okta.com).
1

Step 1

Sign in to your Okta admin console.
2

Step 2

Open Security -> API -> Tokens, then click Create Token.
3

Step 3

Copy the generated SSWS token (it is shown only once).
4

Step 4

Your subdomain is the leading part of your admin URL, e.g. for acme.okta.com the subdomain is acme.

Required Credentials

Available Actions

Parameters

string
required
The first name of the user.
string
required
The last name of the user.
string
required
The email address of the user.
string
required
The login (typically the email) for the user.
string
Optional mobile phone number for the user.
string
Optional ID of a non-default user type. Use list_type_id_options to enumerate available IDs.
boolean
Whether to execute the activation lifecycle on creation. Defaults to true. (Default: true)

Response

Parameters

string
required
The unique identifier of the user (Okta user ID, login, or email).

Response

Response

Parameters

string
required
The unique identifier of the user to update.
string
New first name for the user.
string
New last name for the user.
string
New email address for the user.
string
New login for the user.
string
New mobile phone number for the user.
string
Optional new user type ID. Use list_type_id_options to discover valid IDs.

Response

Limits & Quotas

  • Okta enforces per-org rate limits that vary by endpoint and plan; common defaults are 600 requests/minute for the Users endpoints on developer orgs and higher on production tiers. See https://developer.okta.com/docs/reference/rl-global-mgmt/.
  • Each response includes X-Rate-Limit-Limit, X-Rate-Limit-Remaining, and X-Rate-Limit-Reset headers; agents that hit 429 should back off until the reset epoch.
  • update_user issues one GET plus one PUT per call (the existing profile is merged client-side so partial updates do not blank out fields).
  • Error model: non-2xx responses and timeouts are caught and returned as success=False + error rather than raising.

Jira

Microsoft Entra ID

Algolia