Overview
Pre-built tooling
✅ Authorization
✅ Authorization
✅ Read & write data
✅ Read & write data
| Tools | Status |
|---|---|
| Pre-built integrations | 🚫 (time to contribute: <48h) |
| API unification | ✅ |
| 2-way sync | ✅ |
| Webhooks from Nango on data modifications | ✅ |
| Real-time webhooks from 3rd-party API | 🚫 (time to contribute: <48h) |
| Proxy requests | ✅ |
✅ Observability & data quality
✅ Observability & data quality
| Tools | Status |
|---|---|
| HTTP request logging | ✅ |
| End-to-end type safety | ✅ |
| Data runtime validation | ✅ |
| OpenTelemetry export | ✅ |
| Slack alerts on errors | ✅ |
| Integration status API | ✅ |
✅ Customization
✅ Customization
| Tools | Status |
|---|---|
| Create or customize use-cases | ✅ |
| Pre-configured pagination | ✅ |
| Pre-configured rate-limit handling | ✅ |
| Per-customer configurations | ✅ |
Access requirements
| Pre-Requisites | Status | Comment |
|---|---|---|
| Paid dev account | ✅ Not required | Free developer account available at developer.okta.com. |
| Paid test account | ✅ Not required | Developer accounts can be used for testing. |
| Partnership | ✅ Not required | |
| App review | ✅ Not required | |
| Security audit | ✅ Not required |
Setup guide
No setup guide yet.Contribute improvements to the setup guide by editing this page
Useful links
- Okta API Services app setup guide
- Okta private_key_jwt client authentication
- Okta Management API OAuth 2.0 scopes reference
- Okta API reference
- API rate limiting
Contribute useful links by editing this page
API gotchas
- This provider uses Okta’s Org Authorization Server (
/oauth2/v1/token) withprivate_key_jwtclient authentication to call Okta’s Management API. - The Okta application must be created as API Services (Applications > Create App Integration > API Services). Standard OIDC apps only support
authorization_codeand will returnunauthorized_clienterrors. - Authentication uses
private_key_jwt: you generate an RSA key pair, upload the public key to the Okta app, and provide the private key to Nango. No client secret is used. - Scopes must be granted to your application under Applications >
your app> Okta API Scopes. See the full list in the Okta Management API scopes reference. - Client credentials do not use refresh tokens — Nango re-authenticates automatically when the access token expires (default: 1 hour).
Contribute API gotchas by editing this page
Going further
Connect to Okta (Client Credentials)
Guide to connect to Okta (Client Credentials) using Connect UI