Markdown Anything

All API requests must include a valid Bearer token in the Authorization header. Tokens are scoped to a workspace — every conversion and credit charge is attributed to the workspace that owns the token.

Creating a Token

Open API Token Settings

Navigate to Settings > API Tokens in your workspace dashboard.

Generate a New Token

Click Create Token and give it a descriptive name (e.g. production-pipeline or n8n-integration).

Copy the Token

Your token is displayed once after creation. Copy it immediately — you will not be able to view it again.

Store your token securely. Treat it like a password. Do not commit tokens to version control or expose them in client-side code.

Token Format

All tokens are prefixed with mda_ for easy identification:

mda_1a2b3c4d5e6f7g8h9i0j...

Using the Token

Include the token in the Authorization header as a Bearer token:

curl -X POST https://markdownanything.com/api/v1/convert \
  -H "Authorization: Bearer mda_your_token_here" \
  -F "[email protected]"

API access is available on all paid plans. Free accounts include 25 credits per month.

Workspace Scoping

Tokens are bound to the workspace that created them. This means:

Credits are deducted from the workspace balance, not the individual user.
Conversions are visible to all workspace members.
Rate limits are applied per workspace, not per token.

If you need separate rate limits or credit pools, create separate workspaces.

Revoking a Token

You can revoke any token from Settings > API Tokens. Revoked tokens immediately stop working — any in-flight requests using that token will fail with a 401 response.

Error Response

Requests without a valid token receive a 401 Unauthenticated response:

{
    "message": "Unauthenticated."
}

See Errors for all error codes.

Authentication