Empower OAuth 2.0 API

The authorization API for Empower's API suite, listed as "production" in the public Empower developer portal catalog. It generates bearer access tokens used to authorize calls to the other Empower APIs. Public release notes on the catalog page document /auth and /token endpoints, an optional x-api-key header on both, and an invalid_grant 400 response when a requested OAuth scope is not configured on the client profile. Empower documents OAuth 2.0 and OpenID Connect with the client_credentials grant for B2B partner integration, and is moving to asymmetric private-key JWT client authentication (PKI) in line with Financial-grade API (FAPI) practice. Reference documentation is behind login and the authorization service endpoint is communicated privately to approved partners. The baseURL below is the probe-observed U.S. API gateway host; the authorization service host itself is never published.

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API
curl "https://apis.io/api/v1/apis/empower-oauth-2-0-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.

API entry from apis.yml

apis.yml Raw ↑
aid: great-west-lifeco:empower-oauth-2-0-api
name: Empower OAuth 2.0 API
description: The authorization API for Empower's API suite, listed as "production" in the public Empower
  developer portal catalog. It generates bearer access tokens used to authorize calls to the other Empower
  APIs. Public release notes on the catalog page document /auth and /token endpoints, an optional x-api-key
  header on both, and an invalid_grant 400 response when a requested OAuth scope is not configured on
  the client profile. Empower documents OAuth 2.0 and OpenID Connect with the client_credentials grant
  for B2B partner integration, and is moving to asymmetric private-key JWT client authentication (PKI)
  in line with Financial-grade API (FAPI) practice. Reference documentation is behind login and the authorization
  service endpoint is communicated privately to approved partners. The baseURL below is the probe-observed
  U.S. API gateway host; the authorization service host itself is never published.
humanURL: https://developer.empower.com/api-catalog/oauth2-api
baseURL: https://api.empower.com
tags:
- Authentication
- Authorization
- Security
- OpenID Connect
- Login Gated
tags_raw:
- OAuth
- Authorization
- Security
- OpenID Connect
- Login Gated
properties:
- type: Documentation
  url: https://developer.empower.com/api-catalog/oauth2-api
- type: Authentication
  url: https://developer.empower.com/docs/additional-security-protocols-publicprivate-key-infrastructure-pki
- type: ChangeLog
  url: changelog/great-west-lifeco-changelog.yml
  name: Empower OAuth 2.0 API release notes (v2.3.0, v1.3.1)
- type: OAuthScopes
  url: scopes/great-west-lifeco-scopes.yml