Chatley AI · Authentication Profile

Chatley AI Authentication

Authentication

Chatley AI secures its APIs with http-bearer and oauth2 across 2 declared security schemes, as derived from its OpenAPI definitions.

CompanyArtificial IntelligenceVoice AgentsConversational AIAI ReceptionistTelephonySMSWhite LabelMCPLead Generation
Methods: http-bearer, oauth2 Schemes: 2 OAuth flows: API key in:

Security Schemes

bearer http
scheme: bearer
mcp-oauth oauth2

Source

Authentication Profile

Raw ↑ 
generated: '2026-11-03'
method: searched
source: https://docs.chatley.ai/api/authentication
docs: https://docs.chatley.ai/api/authentication
summary:
  types: [http-bearer, oauth2]
schemes:
- name: bearer
  type: http
  scheme: bearer
  applies_to: Chatley Developer API (https://api.chatley.ai)
  key_prefix: chatley_
  header: 'Authorization: Bearer chatley_your_key'
  description: Every Developer API request is authenticated with a Chatley API key sent as a Bearer token. There are no
    unauthenticated endpoints. Keys are created in Integrations & API Keys -> API Keys by an account owner or administrator,
    are shown once, and carry the full permissions of the owning account. A key is created for one HTTP method; both Developer
    API endpoints are POST, so a key of any other type is rejected with METHOD_NOT_ALLOWED_FOR_KEY. Keys can carry an expiry
    date (API_KEY_EXPIRED) and record when they were last used.
  rotation: Create the replacement key first, deploy it, then deactivate the old one; a deactivated key fails immediately
    with API_KEY_NOT_FOUND.
  sources: [https://docs.chatley.ai/api/authentication, openapi/_ae-authored/chatley-ai-openapi-generated.yml]
- name: mcp-oauth
  type: oauth2
  applies_to: Chatley MCP Server (https://mcp.chatley.ai/mcp)
  description: MCP clients connect with a browser sign-in; the client registers itself automatically and the user approves
    it on a screen that names the client and the Chatley account. Connections can be revoked from Integrations & API Keys.
    The protected-resource metadata names authorization server https://mcp.chatley.ai, bearer_methods_supported [header]
    and scopes_supported [openid, offline_access].
  authorization_servers: [https://mcp.chatley.ai]
  scopes_supported: [openid, offline_access]
  sources: [https://docs.chatley.ai/mcp/connecting, https://mcp.chatley.ai/.well-known/oauth-protected-resource]

Work with this as data

Every security artifact 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 security posture

4 MCP tools reach this
  • find_securityBrowse and filter every security artifact in the catalog.
  • 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 security artifact 
curl "https://apis.io/api/v1/security/chatley-ai-authentication"
All security posture 
curl "https://apis.io/api/v1/security?limit=25"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

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.

GitHub Google LinkedIn

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