Important Update: API Key (Soft) Requirement Starting August
Since launching adfapi.dev, our mission has been simple: provide a fast, reliable way to convert documents into the Atlassian Document Format (ADF) — with zero setup and no friction. We’ve been thrilled by the response and the wide adoption of the API across tools, workflows, and platforms.
To keep the service sustainable and continue improving it, we’re making a small change that takes effect starting August 1st.
What’s Changing?
Starting in August, any API requests without an API key will result in converted documents that include a short line of text:
“Converted by adfapi.dev”
This message is lightweight, unobtrusive, and helps spread the word about the service while allowing us to keep a free tier open for everyone.
Want to Remove the Message?
You can! Just:
- Create an account at adfapi.dev
- Generate an API key
- Include the API key in your request headers
Once authenticated, your converted documents will no longer contain the attribution line.
Why the Change?
Running a free, anonymous service comes with costs — not just in infrastructure, but in abuse protection and long-term support. This new policy lets us continue offering a free tier while giving more control to those who need a clean output.
If you’re using adfapi.dev in production or for client-facing workflows, creating an account and using an API key is the best way to ensure a consistent, unbranded experience.
🙌 Thanks for Your Support
We’re excited about the future of adfapi.dev and have more features planned — including richer formatting options, bulk conversion, and integrations. Your support makes it all possible.
If you have any questions or feedback, don’t hesitate to reach out via our chat feature (bottom right) or email us at info@adfapi.dev.
— The adfapi.dev Team