Slash .well Known API
The .well Known API from Slash — 2 operation(s) for .well known.
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/joinslash-com:joinslash-com-well-known-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: Slash Public .well Known API
description: API description
version: 0.0.1
contact: {}
servers:
- url: https://api.slash.com
description: production
security:
- api_key: []
- partner_api_key: []
- bearer: []
- developer_application: []
tags:
- name: .well Known
paths:
/.well-known/openid-configuration:
x-reference-path: paths/.well-known/openid-configuration/route.yaml
get:
description: Get OpenID Configuration
tags:
- .well Known
security:
- {}
responses:
'200':
description: OK
content:
application/json:
schema:
$ref: '#/components/schemas/AuthorizationServerMetadata'
x-entrypoint:
virtualPath: schemas/AuthorizationServerMetadata
sourcePath: schemas/AuthorizationServerMetadata.yaml
title: AuthorizationServerMetadata
origin: ./src/publicApi
'401':
description: Unauthorized
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
'403':
description: Forbidden
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
'429':
description: TooManyRequests
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
'500':
description: Internal Error
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
summary: Get well known openid configuration
x-summary-source: derived
operationId: getWellKnownOpenidConfiguration
x-operation-id-source: derived
/.well-known/oauth-authorization-server:
x-reference-path: paths/.well-known/oauth-authorization-server/route.yaml
get:
description: Get OAuth 2.0 authorization server metadata (RFC 8414). The same document as the OpenID configuration; MCP clients look here first.
tags:
- .well Known
security:
- {}
responses:
'200':
description: OK
content:
application/json:
schema:
$ref: '#/components/schemas/AuthorizationServerMetadata'
x-entrypoint:
virtualPath: schemas/AuthorizationServerMetadata
sourcePath: schemas/AuthorizationServerMetadata.yaml
title: AuthorizationServerMetadata
origin: ./src/publicApi
'401':
description: Unauthorized
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
'403':
description: Forbidden
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
'429':
description: TooManyRequests
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
'500':
description: Internal Error
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
summary: Get well known oauth authorization server
x-summary-source: derived
operationId: getWellKnownOauthAuthorizationServer
x-operation-id-source: derived
components:
schemas:
Error:
type: object
properties:
message:
type: string
name:
type: string
identifier:
type: string
rawStatus:
type: number
meta:
type: object
additionalProperties: true
required:
- message
- name
- identifier
- rawStatus
x-entrypoint:
origin: ./src/publicApi
sourcePath: ./src/publicApi/main.yaml
title: Error
virtualPath: components/Error
title: Error
AuthorizationServerMetadata:
type: object
description: OAuth 2.0 authorization server metadata (RFC 8414), also served as the OpenID Connect discovery document.
properties:
issuer:
type: string
description: The authorization server's identifier. Authorization responses carry it as `iss` (RFC 9207).
authorization_endpoint:
type: string
token_endpoint:
type: string
userinfo_endpoint:
type: string
token_endpoint_auth_methods_supported:
type: array
description: '`client_secret_basic` for confidential clients; `none` for public clients, which authenticate with PKCE alone.'
items:
type: string
enum:
- client_secret_post
- client_secret_basic
- client_secret_jwt
- private_key_jwt
- none
response_types_supported:
type: array
items:
type: string
enum:
- code
- token
- id_token token
grant_types_supported:
type: array
items:
type: string
enum:
- authorization_code
- refresh_token
scopes_supported:
type: array
items:
$ref: '#/components/schemas/DeveloperApplicationScope'
x-entrypoint:
virtualPath: schemas/DeveloperApplicationScope
sourcePath: schemas/DeveloperApplicationScope.yaml
title: DeveloperApplicationScope
origin: ./src/publicApi
code_challenge_methods_supported:
type: array
items:
type: string
enum:
- S256
authorization_response_iss_parameter_supported:
type: boolean
client_id_metadata_document_supported:
type: boolean
description: Clients may use the HTTPS URL of their client metadata document as the client ID. Only client IDs Slash has registered are accepted.
required:
- issuer
- authorization_endpoint
- token_endpoint
- userinfo_endpoint
- response_types_supported
- scopes_supported
x-entrypoint:
virtualPath: schemas/AuthorizationServerMetadata
sourcePath: schemas/AuthorizationServerMetadata.yaml
title: AuthorizationServerMetadata
origin: ./src/publicApi
title: AuthorizationServerMetadata
DeveloperApplicationScope:
type: string
enum:
- openid
- offline_access
- profile
- email
- address
- phone
- user.identity.view
x-entrypoint:
virtualPath: schemas/DeveloperApplicationScope
sourcePath: schemas/DeveloperApplicationScope.yaml
title: DeveloperApplicationScope
origin: ./src/publicApi
title: DeveloperApplicationScope
securitySchemes:
api_key:
type: apiKey
description: "API key authentication for public API requests.\n\nKeys come in two flavors:\n\n- *Legal-entity-scoped keys* are pinned to a single legal entity.\n Minted via the dashboard under a specific entity; every request\n acts on that entity.\n- *User-scoped keys* are pinned to a user and span every legal\n entity that user has access to. Every request made with a\n user-scoped key (except `GET /legal-entity`, which lists the\n legal entities the user can access) must include an\n `x-legal-entity` header naming the legal entity the request is\n operating on. Requests without the header are rejected with\n `400`. The authenticated user must have an active permission\n role on the supplied legal entity, otherwise the request is\n rejected with `403`.\n"
name: X-API-Key
in: header
partner_api_key:
type: apiKey
description: 'Partner-program API key authentication.
Keys are minted in the partner dashboard (Developers → API Keys),
are scoped to a single partner program, and are prefixed with
`sk_partner_`. Partner keys are only accepted by routes that
declare this scheme; they are rejected by `api_key` routes and
vice versa.
'
name: X-API-Key
in: header
bearer:
type: http
scheme: bearer
developer_application:
type: http
scheme: basic