How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

MethodFi Merchants API

Merchant directory

MethodFi Merchants API is one of 44 APIs that MethodFi publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Merchants. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 3 operations across 3 paths, and defines 11 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against 3 base URLs: https://production.methodfi.com, https://sandbox.methodfi.com, https://dev.methodfi.com.

3 operations 3 paths 11 schemas 3 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://production.methodfi.com
Authentication
HTTP Bearer, HTTP Bearer, HTTP Bearer
Resource Areas
1

Authentication & Security 3

MethodFi Merchants API declares 3 security schemes for authenticating requests. It accepts HTTP bearer tokens (OpalToken). It accepts HTTP bearer tokens (SecretKey). It accepts HTTP bearer tokens (bearerAuth).

  • OpalToken — Opal token authentication for Opal session endpoints. Use an Opal token (otkn...) as the Bearer token. Created via POST /opal/token using a secret key.
  • SecretKey — Secret key authentication. Use your team's secret key (sk...) as the Bearer token. All authenticated API endpoints require this scheme unless otherwise noted.
  • bearerAuth — Provide your Method API key as a Bearer token in the Authorization header. Optionally send a Method-Version header (e.g. 2026-03-30).

Paths & Operations 3

Across 3 paths, the API surfaces 3 operations — 3 GET. Each is listed below with its method, path, parameters, and response codes.

Merchants 3

Merchant directory

GET
/merchants
List all merchants
listMerchants 3 params → 200400401403429500
GET
/merchants/{mchId}
Retrieve a merchant
retrieveMerchant 2 params → 200400401403404429500
GET
/merchants/{mch_id}
Retrieve a merchant
getMerchant 1 param → 200

Schemas 11

The contract defines 11 schemas that model the data the API accepts and returns. The most detailed are Merchant (8 properties), MerchantResponse_2 (6 properties), MerchantProviderIds (5 properties), ErrorObject (4 properties). Each schema is shown below with its type and property counts.

SuccessEnvelope
object
Standard envelope for successful responses that return a single payload.
3 properties 3 required
MerchantProviderIds
object
5 properties
ErrorEnvelope
object
3 properties 3 required
ListEnvelope
object
Standard envelope for successful responses that return a list payload.
3 properties 3 required
Merchant
object
8 properties 8 required
MerchantResponse
MerchantType
string
ErrorObject
object
4 properties 3 required
MerchantListResponse
MerchantResponse_2
object
6 properties
MerchantListResponse_2
object
1 property

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

methodfi-merchants-api-openapi.yml Raw ↑

Other APIs MethodFi publishes across the network.

MethodFi Account Attributes API
MethodFi Account Balances API
MethodFi Account Card Brands API
MethodFi Account Consent API
MethodFi Account Payment Instruments API
MethodFi Account Payoffs API
MethodFi Account Products API
MethodFi Account Sensitive API
MethodFi Account Subscriptions API
MethodFi Account Transactions API
MethodFi Account Updates API
MethodFi Account Verification Sessions API
Where this information came from

This is an independent, third-party profile of MethodFi Merchants API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.