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.
Call it yourself
curl for this page
This API
curl "https://apis.io/api/v1/apis/chime-authentication-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.
OpenAPI Specification
openapi: 3.2.0
info:
title: Chime Partner Authentication API
description: 'The Chime Partner API provides programmatic access to Chime user account information, transactions, account balances, statements, and payment initiation. Authentication is handled via OAuth 2.0 with support for Authorization Code Flow and PKCE (Proof Key for Code Exchange).
'
version: 1.0.0
contact:
url: https://developer.chime.com/
x-api-status: production
servers:
- url: https://api.chimebank.com/chime/v1
description: Chime Partner API Production Server
security:
- BearerAuth: []
tags:
- name: Authentication
description: Legacy partner authentication
paths:
/users/auth_token:
post:
operationId: signIn
summary: Sign in and obtain auth token (Legacy)
description: 'Legacy authentication endpoint. Returns an auth_token for use with legacy API calls. Not recommended for new integrations; use OAuth 2.0 instead.
'
tags:
- Authentication
security: []
requestBody:
required: true
content:
application/json:
schema:
$ref: '#/components/schemas/LegacySignInRequest'
responses:
'200':
description: Authentication successful
content:
application/json:
schema:
$ref: '#/components/schemas/LegacyAuthResponse'
'401':
description: Invalid credentials
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
delete:
operationId: signOut
summary: Invalidate auth token (Legacy)
description: 'Legacy endpoint to invalidate an existing auth_token (logout). Not recommended for new integrations; use OAuth 2.0 instead.
'
tags:
- Authentication
parameters:
- name: client_id
in: query
required: true
description: Your application's client identifier
schema:
type: string
- name: secret
in: query
required: true
description: Your application's client secret
schema:
type: string
- name: auth_token
in: query
required: true
description: The auth token to invalidate
schema:
type: string
responses:
'200':
description: Token invalidated successfully
'401':
description: Invalid credentials
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
components:
schemas:
LegacySignInRequest:
type: object
required:
- client_id
- secret
- username
- password
properties:
client_id:
type: string
description: Your application's client identifier
secret:
type: string
description: Your application's client secret
username:
type: string
description: User's email or username
password:
type: string
format: password
description: User's password
LegacyAuthResponse:
type: object
description: Legacy authentication response
properties:
auth_token:
type: string
description: Authentication token for legacy API calls
user_id:
type: string
description: Authenticated user's ID
Error:
type: object
description: Standard API error response
properties:
error:
type: string
description: Error code
message:
type: string
description: Human-readable error message
status:
type: integer
description: HTTP status code
securitySchemes:
BearerAuth:
type: http
scheme: bearer
bearerFormat: JWT
description: OAuth 2.0 Bearer token