Niche OAuth API
The oauth API from Niche — 4 operation(s) for oauth.
The oauth API from Niche — 4 operation(s) for oauth.
Every API here is available over the APIs.io API and to AI agents over MCP.
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
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.curl "https://apis.io/api/v1/apis/nicheangle-com:nicheangle-com-oauth-api"
curl "https://apis.io/api/v1/apis?limit=25"
Calls without X-API-Key need no key. Calls with it need a paid plan — get a 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. By signing up you are subscribing to the APIs.io and API Evangelist newsletters — you can unsubscribe from any issue. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.
openapi: 3.2.0
info:
title: Signal OAuth API
version: 0.1.0
tags:
- name: OAuth
paths:
/oauth/register:
post:
tags:
- OAuth
summary: Register Client
description: RFC 7591 Dynamic Client Registration. Open endpoint.
operationId: register_client_oauth_register_post
requestBody:
content:
application/json:
schema:
$ref: '#/components/schemas/ClientRegistrationRequest'
required: true
responses:
'200':
description: Successful Response
content:
application/json:
schema: {}
'422':
description: Validation Error
content:
application/json:
schema:
$ref: '#/components/schemas/HTTPValidationError'
/oauth/authorize:
get:
tags:
- OAuth
summary: Authorize
description: 'OAuth 2.1 authorize endpoint. Validates the request, then
redirects to the web-side consent page where the user is auth''d
via Supabase + sees the ''Authorize this app?'' prompt.'
operationId: authorize_oauth_authorize_get
responses:
'200':
description: Successful Response
content:
application/json:
schema: {}
/oauth/authorize/complete:
post:
tags:
- OAuth
summary: Authorize Complete
description: 'Internal endpoint — called by the web consent page after the
user''s decision lands. Mints the auth code on approval, returns the
redirect URL the web side sends the user to.
Auth: requires a valid Supabase JWT in the Authorization header.
The JWT''s `sub` claim becomes the authorized user — body cannot
override (confused-deputy guard).'
operationId: authorize_complete_oauth_authorize_complete_post
requestBody:
content:
application/json:
schema:
$ref: '#/components/schemas/AuthorizeCompleteRequest'
required: true
responses:
'200':
description: Successful Response
content:
application/json:
schema: {}
'422':
description: Validation Error
content:
application/json:
schema:
$ref: '#/components/schemas/HTTPValidationError'
/oauth/token:
post:
tags:
- OAuth
summary: Token
description: 'Exchange an auth code + PKCE code_verifier for an access token.
The minted token is a niche_sk_ opaque bearer stored in api_keys
with oauth_client_id populated.'
operationId: token_oauth_token_post
responses:
'200':
description: Successful Response
content:
application/json:
schema: {}
components:
schemas:
ValidationError:
properties:
loc:
items:
anyOf:
- type: string
- type: integer
type: array
title: Location
msg:
type: string
title: Message
type:
type: string
title: Error Type
input:
title: Input
ctx:
type: object
title: Context
type: object
required:
- loc
- msg
- type
title: ValidationError
HTTPValidationError:
properties:
detail:
items:
$ref: '#/components/schemas/ValidationError'
type: array
title: Detail
type: object
title: HTTPValidationError
ClientRegistrationRequest:
properties:
client_name:
type: string
maxLength: 200
minLength: 1
title: Client Name
redirect_uris:
items:
type: string
type: array
title: Redirect Uris
grant_types:
items:
type: string
type: array
title: Grant Types
response_types:
items:
type: string
type: array
title: Response Types
token_endpoint_auth_method:
type: string
title: Token Endpoint Auth Method
default: client_secret_basic
scope:
anyOf:
- type: string
- type: 'null'
title: Scope
client_uri:
anyOf:
- type: string
- type: 'null'
title: Client Uri
logo_uri:
anyOf:
- type: string
- type: 'null'
title: Logo Uri
tos_uri:
anyOf:
- type: string
- type: 'null'
title: Tos Uri
policy_uri:
anyOf:
- type: string
- type: 'null'
title: Policy Uri
software_id:
anyOf:
- type: string
- type: 'null'
title: Software Id
software_version:
anyOf:
- type: string
- type: 'null'
title: Software Version
type: object
required:
- client_name
title: ClientRegistrationRequest
description: 'Subset of RFC 7591 client metadata we accept. Unknown fields are
ignored (per the spec).'
AuthorizeCompleteRequest:
properties:
client_id:
type: string
title: Client Id
redirect_uri:
type: string
title: Redirect Uri
scope:
type: string
title: Scope
default: niche:mcp
state:
type: string
title: State
default: ''
code_challenge:
type: string
title: Code Challenge
code_challenge_method:
type: string
title: Code Challenge Method
default: S256
approved:
type: boolean
title: Approved
type: object
required:
- client_id
- redirect_uri
- code_challenge
- approved
title: AuthorizeCompleteRequest
description: 'Payload posted by the web consent page after the user clicks
Authorize / Deny. The authenticated Supabase user (resolved
server-side from the Authorization: Bearer header) is the one we
issue the code for — the body''s user_id field is IGNORED if it
disagrees with the JWT, to prevent confused-deputy attacks.'