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.
openapi: 3.2.0
info:
title: Mercoa Organization API
description: 'The Mercoa REST API powers embedded accounts payable and accounts receivable
workflows inside vertical SaaS platforms. This spec is a curated subset of
the canonical Mercoa OpenAPI document
(https://github.com/mercoa-finance/openapi). All requests authenticate with
a Bearer token (API key or JWT) in the Authorization header.'
version: '1.0'
contact:
name: Mercoa
url: https://docs.mercoa.com/
servers:
- url: https://api.mercoa.com
description: Production
security:
- bearerAuth: []
tags:
- name: Organization
paths:
/organization:
get:
tags:
- Organization
summary: Get organization
responses:
'200':
description: Organization
operationId: getOrganization
x-operation-id-source: derived
post:
tags:
- Organization
summary: Update organization
responses:
'200':
description: Updated
operationId: postOrganization
x-operation-id-source: derived
components:
securitySchemes:
bearerAuth:
type: http
scheme: bearer
bearerFormat: token
description: 'Mercoa API key or JWT. Send as "Authorization: Bearer {token}". API keys
are issued from the Mercoa Dashboard and are backend-only. JWTs scope
access to an entity or entity group.
'
x-provenance:
method: harvested
publisher: Mercoa
source: https://docs.mercoa.com/openapi/api-reference-2.yaml
note: split by refine-openapis from the provider's own published document, verified by fetch (openapi/_original/*.fetch.json);
stamped by stamp-openapi-provenance.py (roadmap#793)