ReachSocial · Authentication Profile

ReachSocial Authentication

Authentication

ReachSocial declares 4 security scheme(s) across its OpenAPI definitions.

SocialDataPublicPayments
Methods: Schemes: 4 OAuth flows: API key in:

Security Schemes

http
scheme: bearer
PAYMENT-SIGNATURE apiKey
· in: header ()
X-Job-Token apiKey
· in: header ()
X-Admin-Token apiKey
· in: header ()

Source

Authentication Profile

Raw ↑ 
generated: '2026-11-07'
method: derived
source: https://reachsocial.dev/openapi.json
schemes:
  - id: bearerAuth
    type: http
    scheme: bearer
    description: "Private ReachSocial B2B API key."
  - id: x402Payment
    type: apiKey
    in: header
    name: PAYMENT-SIGNATURE
    description: "x402 v2 payment signature after the initial 402 challenge."
  - id: jobToken
    type: apiKey
    in: header
    name: X-Job-Token
    description: "Opaque token returned once for an anonymous asynchronous job."
  - id: adminToken
    type: apiKey
    in: header
    name: X-Admin-Token
    description: "Protected owner-operations token; never used by public agents."

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.
All 92 tools →

Call it yourself

curl for this page
This security artifact 
curl "https://apis.io/api/v1/security/reachsocial-dev-authentication"
All security posture 
curl "https://apis.io/api/v1/security?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.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.