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/medianfi-com:medianfi-com-accounting-tags-api"
All apis
curl "https://apis.io/api/v1/apis?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.
openapi: 3.2.0
info:
title: Median Accounting Tags API
version: 0.1.0
description: Production-grade Node.js + Express API starter template
license:
name: Proprietary
servers:
- url: /api/v1
security: []
tags:
- name: Accounting Tags
paths:
/companies/{companyId}/tags:
parameters:
- $ref: '#/components/parameters/companyId'
get:
operationId: listAccountingTags
summary: List accounting tags
description: Company-owned controlled tag vocabulary (#1166). Retired tags are omitted unless includeRetired=true. Owner, admin, cfo and member roles write; viewers read. Held behind the same customer surface gate as classes.
tags:
- Accounting Tags
security:
- bearerAuth: []
parameters:
- name: includeRetired
in: query
schema:
type: string
enum:
- 'true'
- 'false'
responses:
'200':
description: Tags
content:
application/json:
schema:
$ref: '#/components/schemas/AccountingTagsListResponse'
'401':
$ref: '#/components/responses/Unauthorized'
'403':
$ref: '#/components/responses/Forbidden'
post:
operationId: createAccountingTag
summary: Create an accounting tag
tags:
- Accounting Tags
security:
- bearerAuth: []
requestBody:
required: true
content:
application/json:
schema:
$ref: '#/components/schemas/AccountingTagNameInput'
example:
name: Paid social
responses:
'201':
description: Tag created
content:
application/json:
schema:
$ref: '#/components/schemas/AccountingTagResponse'
'401':
$ref: '#/components/responses/Unauthorized'
'403':
$ref: '#/components/responses/Forbidden'
'409':
description: A live tag with the same name (ignoring case and repeated spaces) exists
content:
application/json:
schema:
$ref: '#/components/schemas/ApiErrorResponse'
'422':
$ref: '#/components/responses/ValidationError'
/companies/{companyId}/tags/{tagId}:
parameters:
- $ref: '#/components/parameters/companyId'
- name: tagId
in: path
required: true
schema:
type: string
format: uuid
patch:
operationId: renameAccountingTag
summary: Rename an accounting tag
tags:
- Accounting Tags
security:
- bearerAuth: []
requestBody:
required: true
content:
application/json:
schema:
$ref: '#/components/schemas/AccountingTagNameInput'
responses:
'200':
description: Tag renamed; assignments keep the same tag ID
content:
application/json:
schema:
$ref: '#/components/schemas/AccountingTagResponse'
'401':
$ref: '#/components/responses/Unauthorized'
'403':
$ref: '#/components/responses/Forbidden'
'404':
$ref: '#/components/responses/NotFound'
'409':
description: A live tag with the same name exists
content:
application/json:
schema:
$ref: '#/components/schemas/ApiErrorResponse'
'422':
$ref: '#/components/responses/ValidationError'
/companies/{companyId}/tags/{tagId}/retire:
parameters:
- $ref: '#/components/parameters/companyId'
- name: tagId
in: path
required: true
schema:
type: string
format: uuid
post:
operationId: retireAccountingTag
summary: Retire an accounting tag
description: Idempotent. A retired tag keeps its existing assignments and history but cannot be newly assigned. Tags are never deleted.
tags:
- Accounting Tags
security:
- bearerAuth: []
responses:
'200':
description: Tag retired
content:
application/json:
schema:
$ref: '#/components/schemas/AccountingTagResponse'
'401':
$ref: '#/components/responses/Unauthorized'
'403':
$ref: '#/components/responses/Forbidden'
'404':
$ref: '#/components/responses/NotFound'
'422':
$ref: '#/components/responses/ValidationError'
/companies/{companyId}/transactions/{transactionId}/tags:
parameters:
- $ref: '#/components/parameters/companyId'
- name: transactionId
in: path
required: true
schema:
type: string
format: uuid
get:
operationId: getTransactionTags
summary: Get a transaction's tags and revision
tags:
- Accounting Tags
security:
- bearerAuth: []
responses:
'200':
description: Current tags
content:
application/json:
schema:
$ref: '#/components/schemas/TransactionTagAssignmentResponse'
'401':
$ref: '#/components/responses/Unauthorized'
'403':
$ref: '#/components/responses/Forbidden'
'404':
$ref: '#/components/responses/NotFound'
put:
operationId: replaceTransactionTags
summary: Replace a transaction's tags
description: Sends the full tag set with the revision the client loaded. A different set at a stale revision is 409 and changes nothing; an identical set is an idempotent no-op. Never changes amounts, accounts, dates, status or reconciliation state; reconciled transactions may be tagged. Refused (422) when the transaction or a linked posted entry is in a filing-locked period. Owner, admin, cfo and member roles write; viewers read. Held behind the same customer surface gate as classes.
tags:
- Accounting Tags
security:
- bearerAuth: []
requestBody:
required: true
content:
application/json:
schema:
$ref: '#/components/schemas/ReplaceTransactionTagsInput'
example:
tagIds:
- 6f1b2a4e-8f7c-4b8e-9d2a-1c3e5f7a9b0d
expectedRevision: 0
responses:
'200':
description: Tags replaced (or unchanged)
content:
application/json:
schema:
$ref: '#/components/schemas/TransactionTagAssignmentResponse'
example:
success: true
data:
transactionId: 0b8f2c1e-2d7a-4c3b-9e1f-5a6b7c8d9e0f
tagIds:
- 6f1b2a4e-8f7c-4b8e-9d2a-1c3e5f7a9b0d
revision: 1
'401':
$ref: '#/components/responses/Unauthorized'
'403':
$ref: '#/components/responses/Forbidden'
'404':
$ref: '#/components/responses/NotFound'
'409':
description: The tags changed since the client loaded them (TAG_REVISION_CONFLICT)
content:
application/json:
schema:
$ref: '#/components/schemas/ApiErrorResponse'
'422':
description: Validation failed, unknown or retired tag, or filing-locked period
content:
application/json:
schema:
$ref: '#/components/schemas/ApiErrorResponse'
/accountant/companies/{customerId}/tags:
parameters:
- name: customerId
in: path
required: true
schema:
type: string
format: uuid
get:
operationId: listAccountantAccountingTags
summary: List accounting tags
description: Company-owned controlled tag vocabulary (#1166). Retired tags are omitted unless includeRetired=true. Assigned accountants only.
tags:
- Accounting Tags
security:
- bearerAuth: []
parameters:
- name: includeRetired
in: query
schema:
type: string
enum:
- 'true'
- 'false'
responses:
'200':
description: Tags
content:
application/json:
schema:
$ref: '#/components/schemas/AccountingTagsListResponse'
'401':
$ref: '#/components/responses/Unauthorized'
'403':
$ref: '#/components/responses/Forbidden'
post:
operationId: createAccountantAccountingTag
summary: Create an accounting tag
tags:
- Accounting Tags
security:
- bearerAuth: []
requestBody:
required: true
content:
application/json:
schema:
$ref: '#/components/schemas/AccountingTagNameInput'
example:
name: Paid social
responses:
'201':
description: Tag created
content:
application/json:
schema:
$ref: '#/components/schemas/AccountingTagResponse'
'401':
$ref: '#/components/responses/Unauthorized'
'403':
$ref: '#/components/responses/Forbidden'
'409':
description: A live tag with the same name (ignoring case and repeated spaces) exists
content:
application/json:
schema:
$ref: '#/components/schemas/ApiErrorResponse'
'422':
$ref: '#/components/responses/ValidationError'
/accountant/companies/{customerId}/tags/{tagId}:
parameters:
- name: customerId
in: path
required: true
schema:
type: string
format: uuid
- name: tagId
in: path
required: true
schema:
type: string
format: uuid
patch:
operationId: renameAccountantAccountingTag
summary: Rename an accounting tag
tags:
- Accounting Tags
security:
- bearerAuth: []
requestBody:
required: true
content:
application/json:
schema:
$ref: '#/components/schemas/AccountingTagNameInput'
responses:
'200':
description: Tag renamed; assignments keep the same tag ID
content:
application/json:
schema:
$ref: '#/components/schemas/AccountingTagResponse'
'401':
$ref: '#/components/responses/Unauthorized'
'403':
$ref: '#/components/responses/Forbidden'
'404':
$ref: '#/components/responses/NotFound'
'409':
description: A live tag with the same name exists
content:
application/json:
schema:
$ref: '#/components/schemas/ApiErrorResponse'
'422':
$ref: '#/components/responses/ValidationError'
/accountant/companies/{customerId}/tags/{tagId}/retire:
parameters:
- name: customerId
in: path
required: true
schema:
type: string
format: uuid
- name: tagId
in: path
required: true
schema:
type: string
format: uuid
post:
operationId: retireAccountantAccountingTag
summary: Retire an accounting tag
description: Idempotent. A retired tag keeps its existing assignments and history but cannot be newly assigned. Tags are never deleted.
tags:
- Accounting Tags
security:
- bearerAuth: []
responses:
'200':
description: Tag retired
content:
application/json:
schema:
$ref: '#/components/schemas/AccountingTagResponse'
'401':
$ref: '#/components/responses/Unauthorized'
'403':
$ref: '#/components/responses/Forbidden'
'404':
$ref: '#/components/responses/NotFound'
'422':
$ref: '#/components/responses/ValidationError'
/accountant/companies/{customerId}/transactions/{transactionId}/tags:
parameters:
- name: customerId
in: path
required: true
schema:
type: string
format: uuid
- name: transactionId
in: path
required: true
schema:
type: string
format: uuid
get:
operationId: getAccountantTransactionTags
summary: Get a transaction's tags and revision
tags:
- Accounting Tags
security:
- bearerAuth: []
responses:
'200':
description: Current tags
content:
application/json:
schema:
$ref: '#/components/schemas/TransactionTagAssignmentResponse'
'401':
$ref: '#/components/responses/Unauthorized'
'403':
$ref: '#/components/responses/Forbidden'
'404':
$ref: '#/components/responses/NotFound'
put:
operationId: replaceAccountantTransactionTags
summary: Replace a transaction's tags
description: Sends the full tag set with the revision the client loaded. A different set at a stale revision is 409 and changes nothing; an identical set is an idempotent no-op. Never changes amounts, accounts, dates, status or reconciliation state; reconciled transactions may be tagged. Refused (422) when the transaction or a linked posted entry is in a filing-locked period. Assigned accountants only.
tags:
- Accounting Tags
security:
- bearerAuth: []
requestBody:
required: true
content:
application/json:
schema:
$ref: '#/components/schemas/ReplaceTransactionTagsInput'
example:
tagIds:
- 6f1b2a4e-8f7c-4b8e-9d2a-1c3e5f7a9b0d
expectedRevision: 0
responses:
'200':
description: Tags replaced (or unchanged)
content:
application/json:
schema:
$ref: '#/components/schemas/TransactionTagAssignmentResponse'
example:
success: true
data:
transactionId: 0b8f2c1e-2d7a-4c3b-9e1f-5a6b7c8d9e0f
tagIds:
- 6f1b2a4e-8f7c-4b8e-9d2a-1c3e5f7a9b0d
revision: 1
'401':
$ref: '#/components/responses/Unauthorized'
'403':
$ref: '#/components/responses/Forbidden'
'404':
$ref: '#/components/responses/NotFound'
'409':
description: The tags changed since the client loaded them (TAG_REVISION_CONFLICT)
content:
application/json:
schema:
$ref: '#/components/schemas/ApiErrorResponse'
'422':
description: Validation failed, unknown or retired tag, or filing-locked period
content:
application/json:
schema:
$ref: '#/components/schemas/ApiErrorResponse'
components:
schemas:
ApiErrorResponse:
type: object
required:
- success
- error
properties:
success:
type: boolean
enum:
- false
error:
$ref: '#/components/schemas/ProblemDetail'
ProblemDetail:
type: object
properties:
type:
type: string
title:
type: string
description: 'For application errors, a stable UPPER_SNAKE machine code (for example `NOT_FOUND`, `FORECAST_NOT_FOUND`, `VALIDATION_ERROR`). Clients branch on this, never on `detail` wording. A few transport level responses use a short human title instead.
'
status:
type: integer
detail:
type: string
description: 'Human-readable explanation; correlate a failure with `traceId`. A NOT_FOUND-family 404 names the resource type (for example "Company not found"), not its id. Some legacy messages still include an id (tracked in #2666).
'
instance:
type: string
traceId:
type: string
retryAfter:
type: integer
minimum: 0
description: Whole seconds until retry is allowed for a 429 response
errors:
type: array
items:
type: object
properties:
field:
type: string
message:
type: string
extensions:
type: object
additionalProperties: true
TransactionTagAssignmentResponse:
type: object
properties:
success:
type: boolean
data:
type: object
required:
- transactionId
- tagIds
- revision
properties:
transactionId:
type: string
format: uuid
tagIds:
type: array
items:
type: string
format: uuid
revision:
type: integer
minimum: 0
description: Accepted tag changes so far; send it back as expectedRevision
AccountingTagNameInput:
type: object
additionalProperties: false
required:
- name
properties:
name:
type: string
minLength: 1
maxLength: 80
description: Plain text; unique per company among live tags ignoring case and repeated spaces
AccountingTagsListResponse:
type: object
properties:
success:
type: boolean
data:
type: array
items:
$ref: '#/components/schemas/AccountingTag'
ReplaceTransactionTagsInput:
type: object
additionalProperties: false
required:
- tagIds
- expectedRevision
properties:
tagIds:
type: array
maxItems: 20
uniqueItems: true
items:
type: string
format: uuid
expectedRevision:
type: integer
minimum: 0
AccountingTagResponse:
type: object
properties:
success:
type: boolean
data:
$ref: '#/components/schemas/AccountingTag'
AccountingTag:
type: object
required:
- id
- name
- retired
- retiredAt
- createdAt
- updatedAt
properties:
id:
type: string
format: uuid
name:
type: string
maxLength: 80
retired:
type: boolean
retiredAt:
type:
- string
- 'null'
format: date-time
createdAt:
type: string
format: date-time
updatedAt:
type: string
format: date-time
responses:
Forbidden:
description: Insufficient permissions or not a company member
content:
application/problem+json:
schema:
$ref: '#/components/schemas/ProblemDetail'
NotFound:
description: Resource not found
content:
application/problem+json:
schema:
$ref: '#/components/schemas/ProblemDetail'
Unauthorized:
description: Authentication required
content:
application/problem+json:
schema:
$ref: '#/components/schemas/ProblemDetail'
ValidationError:
description: Request failed validation
content:
application/problem+json:
schema:
$ref: '#/components/schemas/ProblemDetail'
parameters:
companyId:
name: companyId
in: path
required: true
schema:
type: string
format: uuid
securitySchemes:
bearerAuth:
type: http
scheme: bearer
bearerFormat: JWT
serviceApiKey:
type: apiKey
in: header
name: X-API-Key
description: 'Persistent credential for the configured cloud-bookkeeping service principal. The key must carry accountant:* and is accepted only on accountant operations that explicitly list this scheme. Ordinary API keys, and service keys presented to bearer-only operations, are denied.
'
refreshSessionCookie:
type: apiKey
in: cookie
name: __Secure-median_refresh
description: 'Exact production HttpOnly refresh-session cookie. Local non-secure development uses median_refresh.
'
passkeyEnrollmentGrantCookie:
type: apiKey
in: cookie
name: __Secure-median_passkey_enrollment
description: 'Exact production HttpOnly passkey-enrollment grant cookie. Local non-secure development uses median_passkey_enrollment.
'
webAuthnCeremonyCookie:
type: apiKey
in: cookie
name: __Secure-median_webauthn
description: 'Exact production HttpOnly WebAuthn ceremony cookie. Local non-secure development uses median_webauthn.
'
x-median-quarantined-authorities:
decision: ADR-0001-model-a
runtimeStatus: unmounted
description: 'Migrations 267-272 modeled legal entities as separate company tenants. These paths are not runtime API authority while their preserved accounting math is re-keyed to legal entities inside one company workspace.
'
paths:
- /companies/{companyId}/consolidation-groups
- /companies/{companyId}/consolidation-groups/{groupId}/versions/{groupVersionId}/report-rollups
- /companies/{companyId}/consolidation-groups/{groupId}/versions/{groupVersionId}/report-rollups/{rollupId}
- /companies/{companyId}/consolidation-groups/{groupId}/versions/{groupVersionId}/translation-adjustments
- /companies/{companyId}/consolidation-groups/{groupId}/versions/{groupVersionId}/translation-adjustments/{adjustmentId}
x-median-demo-parity-customer-surface:
runtimeStatus: mounted-lifecycle-only
description: 'v2 customer-app capabilities available to JWT-authenticated members of any active or test company — the v2 app is the product, not a rollout cohort, so no allowlist applies to the markerless path. Production customer calls omit X-Median-App-Surface. Test-company calls may carry X-Median-App-Surface: qa to select the QA bundle; that marker branch alone still requires membership in CUSTOMER_APP_DEMO_PARITY_COMPANY_IDS. An API key, unknown marker, malformed company id, inactive company, missing gate dependency, or failed company lookup receives the standard hidden-resource 404 contract. The held surfaces riding these prefixes (AR/AP, Forecast, Insights) carry their own additional allowlist gate — see x-median-forecast-hold and x-median-ar-ap-hold.
'
headerContract: '#/components/parameters/demoParityCustomerAppSurface'
routePrefixes:
- /companies/{companyId}/ar
- /companies/{companyId}/ap
- /companies/{companyId}/customers
- /companies/{companyId}/vendors
- /companies/{companyId}/contracts
- /companies/{companyId}/receivables
- /companies/{companyId}/entities
- /companies/{companyId}/currencies
- /companies/{companyId}/reporting-scopes
- /companies/{companyId}/reporting-scopes/{reportingScopeId}/versions/{versionId}/rollups
- /companies/{companyId}/reporting-scopes/{reportingScopeId}/versions/{versionId}/translation-adjustments
- /companies/{companyId}/presentation-report-snapshots
- /companies/{companyId}/reporting-trial-balances
- /companies/{companyId}/reporting-scopes/{reportingScopeId}/versions/{versionId}/trial-balances
- /companies/{companyId}/reporting-scopes/{reportingScopeId}/versions/{versionId}/intercompany
- /companies/{companyId}/weekly-email
- /companies/{companyId}/forecast
- /companies/{companyId}/books
- /companies/{companyId}/sub-ledgers
x-median-forecast-hold:
runtimeStatus: mounted-only-with-server-gate
description: 'Forecast is held. Beyond the lifecycle-only customer surface above, every operation under the prefix below also requires the company to appear in the held-surface allowlist CUSTOMER_APP_DEMO_PARITY_COMPANY_IDS — the one operator-set list that opens AR/AP, Forecast and Insights (the legacy CUSTOMER_APP_FORECAST_COMPANY_IDS variable is no longer consulted). It is empty by default, so the v2 rollout alone never exposes Forecast. A company off the list receives the same hidden-resource 404 contract as one for which the surface does not exist. The auth-context featureFlags key `forecast` mirrors this verdict for the customer app shell.
'
featureFlag: forecast
routePrefixes:
- /companies/{companyId}/forecast
x-median-ar-ap-hold:
runtimeStatus: mounted-only-with-server-gate
description: 'Receivables/Payables are held behind TWO required authorities. Beyond the lifecycle-only customer surface above, every operation under the prefixes below requires the company to appear in the held-surface allowlist CUSTOMER_APP_DEMO_PARITY_COMPANY_IDS (requireDemoParityAllowlistedCompany) AND to satisfy the company_subledger_flags conversion chain (requireArApItemsEnabled — the same authority the public /pay page, aging and the accountant portal consult); failing either answers the opaque 404. The auth-context featureFlags key `arApItems` mirrors exactly that conjunction, resolved server-side, so the customer shell hides the Receivables/Payables nav and pages instead of offering menu entries these routes 404. Default is FALSE for every company while the list is empty or the conversion has not run.
'
featureFlag: arApItems
routePrefixes:
- /companies/{companyId}/ar
- /companies/{companyId}/ap
- /companies/{companyId}/customers
- /companies/{companyId}/vendors
- /companies/{companyId}/contracts
- /companies/{companyId}/receivables
x-median-demo-parity-qa-only:
runtimeStatus: mounted-only-with-server-gate
description: 'Strict test-company-only routes. Every interactive call requires X-Median-App-Surface: qa in addition to JWT authentication, the server allowlist, and persisted client_status=test. A copied header, API key, active company, missing gate dependency, or failed company lookup receives the standard hidden-resource 404 contract.
'
headerContract: '#/components/parameters/qaAppSurface'
routePrefixes:
- /companies/{companyId}/gl-accounts/{id}/monetary-classification
- /companies/{companyId}/fx-account-roles
- /companies/{companyId}/gl-periods/{periodId}/fx-revaluation
- /accountant/companies/{customerId}/gl-accounts/{id}/monetary-classification
- /accountant/companies/{customerId}/fx-account-roles
- /accountant/companies/{customerId}/gl-periods/{periodId}/fx-revaluation
- /accountant/companies/{customerId}/ar/{id}
- /accountant/companies/{customerId}/ap/{id}
x-median-onboarding-v3-surface:
runtimeStatus: promoted
promotionFlag: ONBOARDING_V3_QA_ONLY=false
description: 'Promoted. The deployment this contract describes runs ONBOARDING_V3_QA_ONLY=false, so none of the onboarding-v3 auth, pricing, or setup paths below requires X-Median-App-Surface: qa. An unmarked request is served and reaches ordinary authentication, so an unauthenticated call now answers 401 rather than the hidden-resource 404. Mounting is still conditional: with ONBOARDING_V3_ENABLED false every path below returns the hidden-resource 404 before body parsing or authentication. The header stays defined and is still honoured, because a deployment left at ONBOARDING_V3_QA_ONLY=true keeps requiring it on every path below and 404s unmarked traffic; setting that flag back to true is the rollback. On either setting the header is a pre-company bundle marker, never tenant authorization.
'
headerContract: '#/components/parameters/onboardingV3QaSurface'
routePaths:
- /auth/otp/start
- /auth/otp/verify
- /auth/passkeys/register/options
- /auth/passkeys/register/verify
- /auth/passkeys/assert/options
- /auth/passkeys/assert/verify
- /onboarding/v3/quote
- /onboarding/v3/offer/resolve
- /onboarding/v3/flow
- /onboarding/v3/setup-intent
- /onboarding/v3/subscribe
- /onboarding/v3/test-account-activation
- /onboarding/v3/checkout-session
- /onboarding/v3/checkout-session/complete
- /onboarding/v3/setup-state
- /onboarding/v3/delegate-invites
- /onboarding/v3/delegate-invites/{inviteId}
- /onboarding/v3/delegate/resolve
- /onboarding/v3/delegate
- /onboarding/v3/task-context
- /onboarding/v3/delegate/task-context
- /onboarding/v3/banks/plaid/link-token
- /onboarding/v3/banks/plaid/exchange
- /onboarding/v3/banks/commit
- /onboarding/v3/documents/google-workspace/auth-url
- /onboarding/v3/documents/google-workspace/callback
- /onboarding/v3/books/quickbooks/auth-url
- /onboarding/v3/books/quickbooks/callback
- /onboarding/v3/books/xero/auth-url
- /onboarding/v3/books/xero/callback
- /onboarding/v3/welcome-call
- /onboarding/v3/welcome-call/embed
- /onboarding/v3/books-progress
- /onboarding/v3/books/open
- /companies/{companyId}/onboarding/v3/questions
- /companies/{companyId}/onboarding/v3/questions/{questionId}/answer
- /companies/{companyId}/onboarding/v3/review-items