Momentum

Momentum API

API for Momentum AI-powered revenue orchestration platform

Documentation GitHub OpenAPI

Operations 5

POST /v1/meeting/remap POST /v1/meeting/remap #

GET /v1/signals/prompts GET /v1/signals/prompts #

POST /v1/user-provided-meeting POST /v1/user-provided-meeting #

GET /v1/{v1id} GET /v1/meetings #

GET /v2/signals GET /v2/signals #

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/momentum:momentum-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.1.0
info:
  title: Momentum API
  version: '2026-10-12'
  description: 'GENERATED FROM DOCUMENTATION by API Evangelist on 2026-10-12: 5 operation(s) read from 9 public documentation page(s) (each operation
    names its page in x-source). This is not the provider''s published contract; Momentum has published no machine-readable contract that the
    pipeline could find. Engine: local.'
  x-evidence-tiers:
    code-example: 8
    documentation: -3
    pages-with-code: 9
    pages-read: 9
  x-generated-from: documentation
  x-provenance: generated
  x-authored-by: API Evangelist
  x-generated: '2026-10-12'
  x-generator: generate-contract-from-docs.py
  x-engine: local
  x-sources:
  - https://docs.momentum.io/api-reference/users/retrieve-a-list-of-users.md
  - https://docs.momentum.io/api-reference/meetings/retrieve-a-list-of-meetings
  - https://docs.momentum.io/api-reference/meetings/retrieve-a-list-of-meetings.md
  - https://docs.momentum.io/api-reference/signals-v1/list-all-ai-signal-prompts.md
  - https://docs.momentum.io/api-reference/signals-v1/retrieve-signal-executions.md
  - https://docs.momentum.io/api-reference/signals-v2/retrieve-signal-v2-executions.md
  - https://docs.momentum.io/api-reference/signals-v2/list-all-signal-v2-definitions.md
  - https://docs.momentum.io/api-reference/meetings/remap-a-meeting-with-new-salesforce-objects
  - https://docs.momentum.io/api-reference/meetings/ingest-a-meeting-from-any-source
servers:
- url: https://api.momentum.io
paths:
  /v1/meeting/remap:
    post:
      operationId: post_v1_meeting_remap
      tags:
      - Meeting
      summary: POST /v1/meeting/remap
      x-source: https://docs.momentum.io/api-reference/meetings/remap-a-meeting-with-new-salesforce-objects
      responses:
        '201':
          description: Success (shape read from the example response on the page)
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/PostV1MeetingRemapResponse'
      x-evidence:
        kind: code-example
        language: curl
        snippet: "curl curl --request POST  --url https://api.momentum.io/v1/meeting/remap  --header 'Content-Type: application/json'  --header\
          \ 'X-API-Key: <api-key>'  --data '\n{\n \"source\": {\n \"id\": \"<string>\"\n },\n \"salesforceRecords\": {\n \"opportunityId\": \"\
          <string>\",\n \"accountId\": \"<string>\",\n \"leadId\": \"<string>\"\n },\n \"meetingDetails\": {\n \"momentumMeetingId\": 123,\n \"\
          title\": \"<string>\",\n \"startTime\": \"2023-11-07T05"
  /v1/signals/prompts:
    get:
      operationId: get_v1_signals_prompts
      tags:
      - Signals
      summary: GET /v1/signals/prompts
      x-source: https://docs.momentum.io/api-reference/signals-v1/list-all-ai-signal-prompts.md
      responses:
        '200':
          description: Success (shape read from the example response on the page)
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/GetV1SignalsPromptsResponse'
      x-evidence:
        kind: code-example
        language: curl
        snippet: "curl --request GET  --url 'https://api.momentum.io/v1/signals/prompts'  --header 'X-API-Key: YOUR_API_KEY'\n        - lang:\
          \ javascript\n          label: JavaScript\n          source: |\n            const response = await fetch(\n              \"https://api.momentum.io/v1/signals/prompts\"\
          ,\n              {\n                headers: { \"X-API-Key\": \"YOUR_API_KEY\" },\n              }\n            );\n           "
  /v1/user-provided-meeting:
    post:
      operationId: post_v1_user_provided_meeting
      tags:
      - User Provided Meeting
      summary: POST /v1/user-provided-meeting
      x-source: https://docs.momentum.io/api-reference/meetings/ingest-a-meeting-from-any-source
      responses:
        '201':
          description: Success (status as documented)
      x-evidence:
        kind: code-example
        language: curl
        snippet: "curl curl --request POST  --url https://receiver.momentum.io/v1/user-provided-meeting  --header 'Content-Type: application/json'\
          \  --header 'X-API-Key: <api-key>'  --data ' \n { \n \"meeting\": { \n \"title\": \"<string>\", \n \"startTime\": \"2023-11-07T05:31:56Z\"\
          , \n \"endTime\": \"2023-11-07T05:31:56Z\", \n \"host\": { \n \"name\": \"<string>\", \n \"email\": \"jsmith@example.com\" \n }, \n\
          \ \"id\": \"<string>\", \n \"callUrl\": \"<stri"
  /v1/{v1id}:
    get:
      operationId: get_v1_v1id
      tags:
      - Api
      summary: GET /v1/meetings
      x-source: https://docs.momentum.io/api-reference/meetings/retrieve-a-list-of-meetings
      parameters:
      - name: v1id
        in: path
        required: true
        schema:
          type: string
      - name: from
        in: query
        required: false
        schema:
          type: string
      - name: includeDownloadUrl
        in: query
        required: false
        schema:
          type: string
      - name: pageNumber
        in: query
        required: false
        schema:
          type: string
      - name: pageSize
        in: query
        required: false
        schema:
          type: string
      - name: sourceTypes
        in: query
        required: false
        schema:
          type: string
      - name: to
        in: query
        required: false
        schema:
          type: string
      responses:
        '200':
          description: Success (shape read from the example response on the page)
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/GetV1V1IdResponse'
      x-evidence:
        kind: code-example
        language: curl
        snippet: "curl cURL curl --request GET  --url 'https://api.momentum.io/v1/meetings?from=2025-01-01T00:00:00Z&to=2025-01-31T23:59:59Z&pageNumber=1&pageSize=10&includeDownloadUrl=true&sourceTypes=MOMENTUM,GONG'\
          \  --header 'X-API-Key: YOUR_API_KEY' const response = await fetch(\n \"https://api.momentum.io/v1/meetings?from=2025-01-01T00:00:00Z&to=2025-01-31T23:59:59Z&pageNumber=1&pageSize=10&includeDownloadUrl=tru"
        collapsed_from: 2 example path(s) differing only at v1Id
  /v2/signals:
    get:
      operationId: get_v2_signals
      tags:
      - Signals
      summary: GET /v2/signals
      x-source: https://docs.momentum.io/api-reference/signals-v2/list-all-signal-v2-definitions.md
      responses:
        '200':
          description: Success (shape read from the example response on the page)
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/GetV2SignalsResponse'
      x-evidence:
        kind: code-example
        language: curl
        snippet: "curl --request GET  --url 'https://api.momentum.io/v2/signals'  --header 'X-API-Key: YOUR_API_KEY'\n        - lang: javascript\n\
          \          label: JavaScript\n          source: |\n            const response = await fetch(\n              \"https://api.momentum.io/v2/signals\"\
          ,\n              {\n                headers: { \"X-API-Key\": \"YOUR_API_KEY\" },\n              }\n            );\n            const\
          \ data = aw"
components:
  schemas:
    PostV1MeetingRemapResponse:
      type: object
      properties:
        accepted:
          type: boolean
        requestId:
          type: string
    GetV1SignalsPromptsResponse:
      type: object
      properties:
        headers:
          type: object
          properties:
            X-API-Key:
              type: string
    GetV1V1IdResponse:
      type: object
      properties:
        X-API-Key:
          type: string
    GetV2SignalsResponse:
      type: object
      properties:
        headers:
          type: object
          properties:
            X-API-Key:
              type: string
  securitySchemes:
    apiKey:
      type: apiKey
      in: header
      name: X-API-Key
security:
- apiKey: []
tags:
- name: Api
- name: Meeting
- name: Signals
- name: User Provided Meeting