Converting RTF to Atlassian Document Format: New Endpoint Available

5 min read

Introducing RTF to ADF Conversion: Expanding Document Format Support

We’re excited to announce a powerful new addition to the ADFAPI.dev platform: RTF (Rich Text Format) to ADF conversion. This latest endpoint expands our document conversion capabilities, making it easier than ever to migrate RTF documents into Atlassian’s ecosystem.

What is RTF and Why Convert to ADF?

Rich Text Format (RTF) is a widely-used document format that preserves text formatting across different applications and platforms. Developed by Microsoft, RTF files contain formatted text, images, and other document elements that can be opened by most word processors.

Converting RTF to Atlassian Document Format (ADF) enables you to:

Migrate legacy documents to Confluence and Jira
Preserve formatting including bold, italic, headers, and lists
Integrate RTF content into Atlassian workflows
Automate document processing pipelines

Two Powerful RTF Conversion Endpoints

Our new RTF conversion feature includes two flexible endpoints to handle different use cases:

1. RTF File Upload Endpoint

Perfect for converting RTF files directly from your file system or application uploads.

Endpoint: POST /api/Rtf/file

Example using curl (without API key):

curl -X 'POST' \
  'https://api.adfapi.dev/api/Rtf/file' \
  -H 'accept: application/json' \
  -H 'Content-Type: multipart/form-data' \
  -F 'file=@document.rtf'

Example using curl (with API key):

curl -X 'POST' \
  'https://api.adfapi.dev/api/Rtf/file' \
  -H 'accept: application/json' \
  -H 'Content-Type: multipart/form-data' \
  -H 'X-API-KEY: YOUR_API_KEY_HERE' \
  -F 'file=@document.rtf'

2. RTF Text Input Endpoint

Ideal for converting RTF content directly from text strings or when working with RTF data in memory.

Endpoint: POST /api/Rtf/text

Example using curl (without API key):

curl -X 'POST' \
  'https://api.adfapi.dev/api/Rtf/text' \
  -H 'accept: application/json' \
  -H 'Content-Type: text/rtf' \
  -d '{\rtf1\ansi\deff0 {\fonttbl {\f0 Times New Roman;}} \f0\fs24 Hello \b bold\b0  world!}'

Example using curl (with API key):

curl -X 'POST' \
  'https://api.adfapi.dev/api/Rtf/text' \
  -H 'accept: application/json' \
  -H 'Content-Type: text/rtf' \
  -H 'X-API-KEY: YOUR_API_KEY_HERE' \
  -d '{\rtf1\ansi\deff0 {\fonttbl {\f0 Times New Roman;}} \f0\fs24 Hello \b bold\b0  world!}'

Using Your API Key for Clean Conversions

Important: When calling the ADFAPI.dev endpoints without an API key, a conversion message is automatically added to your converted documents. To get clean, production-ready ADF output without any additional messages, make sure to include your API key in the request headers.

Why use an API key?

Clean output: No conversion messages added to your documents
Production ready: Perfect for integration into applications and workflows
Rate limiting: Higher request limits for authenticated users
Support: Priority support for API key holders

To get your API key:

Visit ADFAPI.dev and sign up for an account
Generate your API key from the dashboard
Include the X-API-KEY header in all your requests

Getting Started with RTF Conversion

Converting your RTF documents to ADF is straightforward:

Choose your endpoint based on whether you’re working with files or text content
Send your RTF data via POST request
Receive clean ADF JSON ready for use in Confluence, Jira, or other Atlassian products

The conversion process handles common RTF formatting elements including:

Text formatting (bold, italic, underline)
Headers and paragraph styles
Lists (numbered and bulleted)
Basic tables
Line breaks and spacing

Use Cases for RTF to ADF Conversion

Our RTF conversion endpoint is perfect for:

Content Migration Projects: Moving existing RTF documents to Confluence spaces
Documentation Workflows: Converting technical documentation from RTF to ADF
Integration Applications: Building tools that bridge RTF-based systems with Atlassian products
Bulk Document Processing: Automating the conversion of large RTF document libraries
Legacy System Integration: Modernizing document workflows that still rely on RTF format

Enterprise-Ready API Features

Like all ADFAPI.dev endpoints, our RTF conversion service includes:

High Performance: Fast processing optimized for large documents
Reliable Uptime: Enterprise-grade infrastructure with 99.9% availability
Secure Processing: Your documents are processed securely and never stored
Flexible Pricing: Pay-as-you-go model that scales with your needs
Developer-Friendly: RESTful API with comprehensive documentation

Try RTF Conversion Today

Ready to start converting RTF documents to ADF? You can:

Test the API using our interactive API documentation
Try it for free on our Try It page
Get your API key and start integrating RTF conversion into your applications

What’s Next?

The RTF conversion endpoint represents our continued commitment to supporting diverse document formats and making ADF accessible across different content ecosystems. We’re constantly working to expand format support and improve conversion quality.

Have feedback or need support with RTF conversion? Contact our team – we’re here to help you succeed with your document conversion projects.

Ready to convert your RTF documents to ADF? Get started with ADFAPI.dev today and experience the power of seamless document format conversion.

Atlassian Document Format API Blog