Alkemics Token API
The Token API from Alkemics — 1 operation(s) for token.
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/alkemics:alkemics-token-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: authentication Token API
version: '2.1'
servers:
- url: https://apis.supplierxm.salsify.com/auth
security:
- {}
tags:
- name: Token
paths:
/v2/token:
post:
summary: Create Token
description: 'The token can be obtained from the authentication server with your secret credentials. It expires after 2 hours.
When your API receives an HTTP 401 error you will need to re-authenticate using your credentials.
Those credentials were given to you when you registered on the platform. They are strictly confidential and must remain secret.'
operationId: token-v2
requestBody:
content:
application/json:
schema:
type: object
properties:
client_id:
type: string
description: your client_id
client_secret:
type: string
description: your client-secret
grant_type:
type: string
description: the type of credentials used to retrieve the token, should be "client_credentials"
default: client_credentials
responses:
'200':
description: '200'
content:
application/json:
examples:
Result:
value: "{\n \"access_token\": \"GENERATED_TOKEN\",\n \"type\": \"JWT\"\n}"
schema:
type: object
properties:
access_token:
type: string
example: GENERATED_TOKEN
type:
type: string
example: JWT
'400':
description: '400'
content:
application/json:
examples:
Result:
value: '{}'
schema:
type: object
properties: {}
deprecated: false
security: []
x-readme:
code-samples:
- language: text
code: "{\n \"client_secret\": \"azertyuiopqsdfghjk\",\n \"client_id\": \"123456789012345678901234567890\",\n \"grant_type\": \"client_credentials\"\n}"
samples-languages:
- text
tags:
- Token
x-readme-fauxas: true
x-provenance:
method: searched
source: https://docs.supplierxm.salsify.com/reference
harvested: '2026-10-14'
tool: harvest-readme-openapi.py
note: Assembled verbatim from the OpenAPI definition ReadMe embeds in each operation page of the provider's developer portal; paths and components merged by API title, nothing authored.
assembled_from:
- https://docs.supplierxm.salsify.com/reference/list-organizations.md
- https://docs.supplierxm.salsify.com/reference/token-v2.md
merge:
pages: 2
deduped: 0
conflicts_kept_first: 0