Work Market Authentication
The WorkMarket Employer API uses an API token/secret pair exchanged for a short-lived access token. Credentials are generated in the WorkMarket web app; the client POSTs them to the authorization endpoint and then sends the returned access token as a Bearer credential in the Authorization header on subsequent requests. The published Swagger 2.0 spec declares no securityDefinitions; the scheme below is taken from the live API reference (which models it as an apiKey-style Authorization header) and the authorization operation in the spec.
Work Market secures its APIs with accessToken across 1 declared security scheme, as derived from its OpenAPI definitions.
Security Schemes
Source
Authentication Profile
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.
Call it yourself
curl for this page
curl "https://apis.io/api/v1/security/work-market-authentication"
curl "https://apis.io/api/v1/security?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.