Instasent · Schema
Authorization server metadata
RFC 8414 metadata. Served identically at `/.well-known/oauth-authorization-server` and `/.well-known/openid-configuration`.
CompanyMessagingSMSRCSWhatsAppArtificial IntelligenceMarketing
Properties
| Name | Type | Description |
|---|---|---|
| issuer | string | Issuer identifier, derived from the request host. |
| authorization_endpoint | string | Where to send the user's browser to start the flow. It is on this API host, the same origin as `issuer`, and redirects to the dashboard's consent screen, which is where the user actually authenticates |
| token_endpoint | string | Where to exchange the code and rotate refresh tokens. |
| registration_endpoint | string | Dynamic Client Registration endpoint. |
| scopes_supported | array | Every product permission that can appear in a grant. |
| response_types_supported | array | Only the authorization code response type is supported. |
| grant_types_supported | array | |
| code_challenge_methods_supported | array | PKCE is mandatory and only `S256` is accepted. |
| token_endpoint_auth_methods_supported | array | Clients are public; there is no client secret. |
JSON Schema
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"$id": "https://artifacts.apis.io/instasent/json-schema/instasent-oauth-authorization-server-metadata-schema.json",
"title": "Authorization server metadata",
"description": "RFC 8414 metadata. Served identically at\n`/.well-known/oauth-authorization-server` and\n`/.well-known/openid-configuration`.\n",
"x-generated": "2026-11-10",
"x-method": "derived",
"x-generator": "derive-json-schema.py",
"x-source": "openapi/instasent-oauth-api-openapi.yml#/components/schemas/OAuthAuthorizationServerMetadata",
"type": "object",
"properties": {
"issuer": {
"type": "string",
"format": "uri",
"description": "Issuer identifier, derived from the request host."
},
"authorization_endpoint": {
"type": "string",
"format": "uri",
"description": "Where to send the user's browser to start the flow. It is on this API\nhost, the same origin as `issuer`, and redirects to the dashboard's\nconsent screen, which is where the user actually authenticates.\n"
},
"token_endpoint": {
"type": "string",
"format": "uri",
"description": "Where to exchange the code and rotate refresh tokens."
},
"registration_endpoint": {
"type": "string",
"format": "uri",
"description": "Dynamic Client Registration endpoint."
},
"scopes_supported": {
"type": "array",
"description": "Every product permission that can appear in a grant.",
"items": {
"type": "string"
}
},
"response_types_supported": {
"type": "array",
"description": "Only the authorization code response type is supported.",
"items": {
"type": "string",
"enum": [
"code"
]
}
},
"grant_types_supported": {
"type": "array",
"items": {
"type": "string",
"enum": [
"authorization_code",
"refresh_token"
]
}
},
"code_challenge_methods_supported": {
"type": "array",
"description": "PKCE is mandatory and only `S256` is accepted.",
"items": {
"type": "string",
"enum": [
"S256"
]
}
},
"token_endpoint_auth_methods_supported": {
"type": "array",
"description": "Clients are public; there is no client secret.",
"items": {
"type": "string",
"enum": [
"none"
]
}
}
},
"required": [
"issuer",
"authorization_endpoint",
"token_endpoint",
"registration_endpoint",
"scopes_supported",
"response_types_supported",
"grant_types_supported",
"code_challenge_methods_supported",
"token_endpoint_auth_methods_supported"
]
}
Work with this as data
Every JSON Schema 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 schemas
4 MCP tools reach this
find_json_schemasBrowse and filter every JSON Schema 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.
Call it yourself
curl for this page
This JSON Schema
curl "https://apis.io/api/v1/json-schemas/instasent-oauth-authorization-server-metadata"
All schemas
curl "https://apis.io/api/v1/json-schemas?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.
A second provider on the same verified email joins the account you already have.