Leadspace Authorization API

OAuth 2.0 token issuance and refresh

Documentation GitHub OpenAPI

Operations 2

Each operation below carries the questions people ask an LLM about it and the instructions they give an agent to run it. Generated by API Evangelist overlay

POST /oauth/authorize Get an access token with program credentials · Request an OAuth 2.0 access token #

Ask an LLM

“How do I get a bearer token to call the Leadspace v4 APIs?”

“What credentials do I exchange for an API access token, and how long does it last?”

Tell an agent

Request a new access token using program ID {user} and secret {pass} for audience {audience}.

Log in with program ID {user} and secret {pass} to get a fresh 24-hour bearer token scoped to {audience}.

PUT /oauth/authorize Refresh an expired access token · Refresh an OAuth 2.0 access token #

Ask an LLM

“Can I renew my bearer token with a refresh token instead of sending my secret again?”

“What do I send to swap a refresh token for a new access token?”

Tell an agent

Refresh the access token for program ID {user} using refresh token {refreshToken}.

Exchange refresh token {refreshToken} for a new bearer token for {user}.

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.

All 92 tools →

Call it yourself

curl for this page

This API

curl "https://apis.io/api/v1/apis/leadspace:leadspace-authorization-api"

All apis

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.

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.

OpenAPI Specification

openapi: 3.2.0
info:
  title: Leadspace Enrichment API v4 Authorization API
  description: The Leadspace Enrichment API enriches person (lead/contact) and company (account) records against the Leadspace Universal Graph (v4 data graph). Single Direct requests are synchronous; Bulk requests accept up to 500 records per POST and are retrieved asynchronously by polling a results endpoint or via a callback URL. This document was generated by API Evangelist from Leadspace's published technical specifications; Leadspace does not publish a machine-readable OpenAPI definition.
  version: '4.0'
  contact:
    name: Leadspace Support
    url: https://support.leadspace.com/hc/en-us
    email: support@leadspace.com
  termsOfService: https://www.leadspace.com/service-support-terms
servers:
- url: https://apigw.leadspace.com
  description: Leadspace API gateway (production)
security:
- bearerAuth: []
tags:
- name: Authorization
  description: OAuth 2.0 token issuance and refresh
paths:
  /oauth/authorize:
    post:
      operationId: createAuthorizationToken
      summary: Request an OAuth 2.0 access token
      description: Exchanges the Program ID and authentication secret supplied by Leadspace for a bearer token. Tokens expire every 24 hours.
      tags:
      - Authorization
      security: []
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/AuthorizationRequest'
      responses:
        '200':
          description: Token issued
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/AuthorizationResponse'
        '401':
          $ref: '#/components/responses/Unauthorized'
    put:
      operationId: refreshAuthorizationToken
      summary: Refresh an OAuth 2.0 access token
      description: Exchanges a refreshToken for a new bearer token.
      tags:
      - Authorization
      security: []
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/RefreshRequest'
      responses:
        '200':
          description: Token refreshed
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/AuthorizationResponse'
        '401':
          $ref: '#/components/responses/Unauthorized'
components:
  schemas:
    AuthorizationRequest:
      type: object
      required:
      - user
      - pass
      - audience
      properties:
        user:
          type: string
          description: The Program ID Leadspace provided in the credentials email
        pass:
          type: string
          description: The authentication secret Leadspace provided in the credentials email
        audience:
          type: string
          description: For API v4 services use API_GATEWAY
          examples:
          - API_GATEWAY
    RefreshRequest:
      type: object
      required:
      - user
      - refreshToken
      properties:
        user:
          type: string
        refreshToken:
          type: string
    AuthorizationResponse:
      type: object
      properties:
        token:
          type: string
          description: The generated token to use in API v4 enrichment requests
        refreshToken:
          type: string
          description: Value to use in refresh token requests
        expiration:
          type: integer
          description: Epoch seconds of the expiration moment
  responses:
    Unauthorized:
      description: Unauthorized request (wrong credentials or credentials have expired)
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer
      description: Authorization header in the form 'Bearer API_KEY'. The API key is either a perpetual token issued by Leadspace or an OAuth 2.0 token obtained from POST /oauth/authorize.
externalDocs:
  description: Leadspace Single Direct API v4 - Technical Specifications
  url: https://support.leadspace.com/hc/en-us/articles/23687993264284-Leadspace-Single-Direct-API-v4-Technical-Specifications