Emerge · OpenAPI Overlay 1.0.0

API Evangelist enhancements for the Emerge Carrier API

6 actions 6 updates update extends openapi/emerge-carrier-api-openapi.yml
Derived by API Evangelist Built from the contracts Emerge publishes. Emerge did not publish this file.
View Overlay File View on GitHub Overlay Specification

What the actions change

x-agentic-accessx-apievangelist-profilex-apievangelist-artifactsx-contract-gapsx-api-lifecyclex-environmentsx-token-acquisition

Targets 5

$.info
$.servers
$.components.securitySchemes.BearerAuth
$.paths['/options'].post
$.paths['/tenders/{shipment_id}/responses'].post

OpenAPI Overlay

Raw ↑
overlay: 1.0.0
info:
  title: API Evangelist enhancements for the Emerge Carrier API
  version: 1.0.0
extends: openapi/emerge-carrier-api-openapi.yml
x-generated: '2026-08-12'
x-method: generated
x-source: >-
  Enhancements derived from API Evangelist artifacts in this repo. The harvested specification at
  openapi/_original/emerge-carrier-api-openapi.json is never mutated.
actions:
- target: $.info
  update:
    x-apievangelist-profile: https://apievangelist.com/providers/emerge
    x-apievangelist-artifacts:
      authentication: authentication/emerge-authentication.yml
      conventions: conventions/emerge-conventions.yml
      errors: errors/emerge-problem-types.yml
      lifecycle: lifecycle/emerge-lifecycle.yml
      sandbox: sandbox/emerge-sandbox.yml
      webhooks: asyncapi/emerge-webhooks.yml
    x-contract-gaps:
    - no operationId on any operation
    - info.description states "The current version of the API is v1.0.0" while info.version is 2.0.0
      and the servers are /v2 — a documented version inconsistency
    - errors are a proprietary envelope, not RFC 9457 problem+json
- target: $.info
  update:
    x-api-lifecycle:
      version: v2
      spec_version: 2.0.0
      deprecation_support_window: 1 year
      deprecation_policy: https://carrier-api-docs.emergemarket.io/#section/Get-Started/Compatibility-Policy
      status_page: https://status.emergemarket.com/
      onboarding_request: https://emergetech.zendesk.com/hc/en-us/requests/new?ticket_form_id=11470751569179
- target: $.servers
  update:
    x-environments:
      production: https://api.emergemarket.io/v2
      sandbox: https://demo-api.emergemarket.dev/v2
- target: $.components.securitySchemes.BearerAuth
  update:
    x-token-acquisition:
      operation: POST /auth/login/client_credentials
      credentials: Integration Provider client id + client secret
      note: >-
        A client-credentials exchange at a proprietary path — not an RFC 6749 token endpoint, and no
        scopes are defined.
- target: $.paths['/options'].post
  update:
    x-agentic-access:
      action-class: acting
      consequence: physical
      note: >-
        Submits a binding rate to a shipper (creating an Option). Requires the event_id from the
        originating rate_request webhook event; carriers may echo their own quote id in
        provider_reference. Commercially consequential.
- target: $.paths['/tenders/{shipment_id}/responses'].post
  update:
    x-agentic-access:
      action-class: acting
      consequence: physical
      note: Accepts or rejects a tender — commits the carrier to hauling the load.

Work with this as data

Every overlay 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 openapi overlays

4 MCP tools reach this
  • find_overlaysBrowse and filter every overlay 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 overlay
curl "https://apis.io/api/v1/overlays/emerge-carrier-api-overlay"
All openapi overlays
curl "https://apis.io/api/v1/overlays?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.

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