What problem does it solve? Developers integrating with Okta Identity Governance (OIG) face a separately-versioned API with OAuth-only authentication, no official Python SDK, and feature-flag-gated endpoints that return misleading 403/404 errors, causing wasted debugging time and failed integration designs. ## Core Features & Use Cases - API Surface Reference: Documents the /governance/api/v1 and /v2 endpoints covering campaigns, access requests, entitlements, bundles, grants, collections, risk rules, delegates, and security access reviews. - Authentication Guidance: Explains OAuth 2.0-only access with okta.governance.* scopes, admin role requirements for service apps, and the absence of SSWS token support. - Tooling Alternatives: Clarifies that no official Python SDK exists for governance endpoints and points to raw HTTP with httpx/requests, Okta Workflows connectors, or the Okta Terraform Provider (v6.1.0+) as practical options. - Use Case: When building a service-to-service integration that lists OIG campaigns from Python, use this Skill to learn that you must perform a client-credentials JWT exchange against /oauth2/v1/token and call the governance endpoints directly with a bearer token rather than searching for a nonexistent SDK. ## Quick Start Ask how to call the Okta Identity Governance campaigns API from Python and what authentication and scopes are required.
