MX Technologies · OpenAPI Overlay 1.0.0

API Evangelist conversational phrasing for Mx Technologies processor token API

8 actions 8 updates phrasing extends openapi/mx-technologies-processor-token-api-openapi.yml
Generated by API Evangelist Written by API Evangelist tooling for MX Technologies's API. It is a proposal applied on top of the contract, not a document MX Technologies publishes.
View Overlay File View on GitHub Overlay Specification

What the actions change

x-apievangelist-phrasing

Targets 8

$.info
$.paths['/authorization_code'].post
$.paths['/payment_processor_authorization_code'].post
$.paths['/tokens'].get
$.paths['/account/account_numbers'].get
$.paths['/account/check_balance'].post
$.paths['/payment_account'].get
$.paths['/account/transactions'].get

OpenAPI Overlay

Raw ↑
# Generated by API Evangelist (build-phrasing.py). Our phrasing, not observed demand.
overlay: 1.0.0
info:
  title: API Evangelist conversational phrasing for Mx Technologies processor token API
  version: 1.0.0
extends: openapi/mx-technologies-processor-token-api-openapi.yml
actions:
- target: $.info
  update:
    x-apievangelist-phrasing:
      method: generated
      generated: '2026-09-26'
      generator: build-phrasing.py
      label: Generated by API Evangelist
      operations: 7
- target: $.paths['/authorization_code'].post
  update:
    x-apievangelist-phrasing:
      intent: Request an authorization code for a processor
      effect: write
      questions:
      - How do I give a payment processor scoped access to a user's account data?
      - Can I limit a processor's authorization code to specific GUIDs and features?
      instructions:
      - text: Request an authorization code scoped to {scope}.
        slots:
          scope: requestBody.authorization_code
      - text: Generate a processor authorization code for my user's verified account.
      method: generated
      generated: '2026-09-26'
- target: $.paths['/payment_processor_authorization_code'].post
  update:
    x-apievangelist-phrasing:
      intent: Request a payment processor code (legacy)
      effect: write
      questions:
      - Is there an older endpoint that issues a payment processor authorization code by user, member and account?
      - What did the deprecated payment_processor_authorization_code call require?
      instructions:
      - text: Use the deprecated payment processor endpoint to request a code for {details}.
        slots:
          details: requestBody.payment_processor_authorization_code
      - text: Issue a legacy payment-processor authorization code for one user, member and account.
      method: generated
      generated: '2026-09-26'
- target: $.paths['/tokens'].get
  update:
    x-apievangelist-phrasing:
      intent: List processor tokens for a user, member or account
      effect: read
      questions:
      - Which processor tokens currently exist for a user or account?
      - Can I check what tokens were issued for one member?
      instructions:
      - text: List tokens that exist for {scope}.
        slots:
          scope: requestBody.scope
      - text: Show all processor tokens using API version {api_version}.
        slots:
          api_version: header.Accept-Version
      method: generated
      generated: '2026-09-26'
- target: $.paths['/account/account_numbers'].get
  update:
    x-apievangelist-phrasing:
      intent: Get account and routing numbers (processor)
      effect: read
      questions:
      - As a processor, how do I get the routing and account number my access token is scoped to?
      - What account details can a processor retrieve with its token?
      instructions:
      - text: Get the account and routing numbers for my processor token using API version {api_version}.
        slots:
          api_version: header.Accept-Version
      - text: Retrieve the authorized account number for this processor access token.
      method: generated
      generated: '2026-09-26'
- target: $.paths['/account/check_balance'].post
  update:
    x-apievangelist-phrasing:
      intent: Check a real-time balance (processor)
      effect: read
      questions:
      - Can a processor get a live, real-time balance from the institution instead of a cached one?
      - What does the real-time balance check return for a processor token?
      instructions:
      - text: Run a real-time balance check with API version {api_version}.
        slots:
          api_version: header.Accept-Version
      - text: Check the live balance on the account my processor token covers right now.
      method: generated
      generated: '2026-09-26'
- target: $.paths['/payment_account'].get
  update:
    x-apievangelist-phrasing:
      intent: Read the stored account balance (processor)
      effect: read
      questions:
      - As a processor, can I read the payment account's balance without a live refresh?
      - Where does a processor read the balance MX already has on file?
      instructions:
      - text: Read the payment account balance using API version {api_version}.
        slots:
          api_version: header.Accept-Version
      - text: Show the current stored balance for the processor-authorized account.
      method: generated
      generated: '2026-09-26'
- target: $.paths['/account/transactions'].get
  update:
    x-apievangelist-phrasing:
      intent: Get account owner information (processor)
      effect: read
      questions:
      - How does a processor find out who owns the authorized account?
      - Can a processor see the account holder's name and address?
      instructions:
      - text: Get account owner information with API version {api_version}.
        slots:
          api_version: header.Accept-Version
      - text: Look up the owner details for the account my processor token grants.
      method: generated
      generated: '2026-09-26'

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/mx-technologies-processor-token-api-phrasing-overlay"
All openapi overlays
curl "https://apis.io/api/v1/overlays?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

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.