Dawloom developer portal

Quickstart

One request, no setup. The base URL is https://dawloom.com and every endpoint lives under /api/v1/.

curl -F file=@report.docx \
  https://dawloom.com/api/v1/convert

curl -X POST https://dawloom.com/api/v1/convert \
  -H "Content-Type: application/json" \
  -d '{"url":"https://dawloom.com/developers/sample.docx"}'

curl -F file=@report.docx \
  -H "Accept: text/markdown" \
  https://dawloom.com/api/v1/convert

curl -H "Accept: text/markdown" \
  https://dawloom.com/services/

Sandbox

There is no separate sandbox environment, because there is nothing to protect: the API is free, read-only in effect, and stores nothing. Test against production. To try it without supplying your own file, convert the sample document we host for exactly this purpose.

curl -X POST https://dawloom.com/api/v1/convert \
  -H "Content-Type: application/json" \
  -d '{"url":"https://dawloom.com/developers/sample.docx"}'

Authentication and API keys

There are none. No key, no token, no OAuth, no sign-up. Send the request. The security array in the OpenAPI document is empty for the same reason, and the MCP manifest declares authentication: none. If you are building something that needs a key, that is a private integration, and it starts with a conversation.

Endpoints

Every operation has a stable operation id, so it maps cleanly onto an LLM function-calling tool definition. The same list is served as JSON at /api/v1/.

Errors

Every 4xx and 5xx response is JSON, never HTML, and every one has the same shape. It is modelled on RFC 9457 problem details. Send Accept: application/problem+json to get the response typed as a problem document. Branch on code, show detail to a person, and act on hint.

{
  "type": "https://dawloom.com/developers/errors/#validation_failed",
  "title": "One or more fields failed validation",
  "status": 400,
  "code": "validation_failed",
  "detail": "2 field(s) failed validation.",
  "hint": "Fix the fields listed in \"errors\" and send the request again.",
  "documentation_url": "https://dawloom.com/developers/",
  "instance": "/api/v1/contact",
  "ok": false,
  "error": "validation_failed",
  "errors": [
    { "field": "email", "code": "invalid_email", "message": "Give a valid email address so we can reply." }
  ]
}

A 404 on a page URL, not an API path, returns HTML for browsers and a short markdown document for everything else. That markdown lists the sitemap, llms.txt, and this page.

Rate limits

Limits are per client IP. Every response carries RateLimit and RateLimit-Policy, the IETF structured-field form, plus the older RateLimit-Limit, RateLimit-Remaining, and RateLimit-Reset fields. A 429 also carries Retry-After in seconds. Read them and throttle yourself rather than retrying blind.

RateLimit-Policy: "convert";q=30;w=60
RateLimit: "convert";r=29;t=60
RateLimit-Limit: 30
RateLimit-Remaining: 29
RateLimit-Reset: 60

Versioning and deprecation

The version is in the URL path. Everything current lives under /api/v1/, and every response repeats it in an X-Api-Version header.

• A breaking change never lands in an existing version. It gets a new path, /api/v2/, and both run side by side.
• Additive changes, meaning new fields, new endpoints, and new enum members, can land in v1 at any time. Parse leniently and ignore what you do not know.
• A deprecated endpoint keeps working for at least 12 months after the notice.
• Deprecated responses carry Deprecation: true, a Sunset HTTP date (RFC 8594), and a Link header with rel="deprecation".

Deprecated today: the unversioned aliases /api/convert and /api/contact. They still work and are scheduled to sunset on 31 December 2031. Move to the /api/v1/ paths.

MCP server

The same conversion is exposed as an MCP server over Streamable HTTP, so Claude, ChatGPT, and any other MCP client can call it as a tool. No key. The manifest sits at the well-known path, and the server speaks both the modern stateless revision and the older initialize handshake.

claude mcp add --transport http \
  dawloom-tools https://dawloom.com/mcp

{
  "mcpServers": {
    "dawloom-tools": {
      "type": "http",
      "url": "https://dawloom.com/mcp"
    }
  }
}

Endpoint

https://dawloom.com/mcp

Transport

Streamable HTTP

Manifest

/.well-known/mcp.json

Tools

convert_document, list_supported_formats

We also build MCP servers for other companies. That work is described on the MCP servers page.

Command line

The API is a single POST, so curl is a perfectly good client. A shell function is enough to make it feel like a tool:

dawloom() {
  curl -sS -F "file=@$1" -H "Accept: text/markdown" \
    https://dawloom.com/api/v1/convert
}

dawloom report.docx > report.md

A packaged CLI lives in the site repository under cli/. It is not on npm yet. When it is published this page will say so, with the install command.

Machine-readable files

Everything an agent needs to work with Dawloom without reading a single HTML page.

Every page on dawloom.com is also available as markdown. Send Accept: text/markdown to any page URL and you get clean markdown with the front matter, no navigation, no scripts. Each HTML page also advertises its markdown twin in a Link header.

Support

Email support@dawloom.com for anything about the API or the MCP server. For a project, use the contact form or POST /api/v1/contact. What we collect and why is written down on the privacy page.