On this page
We've got a new API reference in the works! With a fresh look and feel, our new API content features a more logical navigation and a wider variety of code examples. Try the beta now (opens new window) and help us improve the site by providing feedback (opens new window).
Details on parameters, requests, and responses for Okta's API endpoints.
In some cases, APIs have only been documented on the new beta reference site (opens new window). This section provides a list of those, so that you can easily find them.
- Agent Pools (opens new window)
- API Service Integrations (opens new window)
- Customized Sign-in Page (opens new window)
- Customized Sign-out Page (opens new window)
- Customized Error Page (opens new window)
- Group Owners (opens new window)
The Core Okta API is the primary way that apps and services interact with Okta. You can use it to implement basic auth functions such as signing in your users and programmatically managing your Okta objects.
Okta Event and inline hooks allow you to integrate custom functionality into specific Okta process flows. event hooks send Okta events of interest to your systems as they occur, just like a webhook. inline hooks allow developers to modify in-flight Okta processes with custom logic and data from a non-Okta source. For example, you can migrate users from another data store and keep the user’s current password with a password inline hook.
Expressions allow you to reference, transform, and combine attributes before you store or parse them.
SCIM is an industry-standard protocol for automating the exchange of user identity information and is part of the Okta Lifecycle Management feature. For example, as your company onboards employees, new user accounts are created in your application so they can connect immediately. Okta supports SCIM versions 1.1 and 2.0.