|Markdown Exporter & Importer for Confluence
No, an active Markdown Importer license is required to create and use API tokens. The license must be active at the time of token creation.
You can create up to 50 tokens per Confluence instance. This limit helps maintain security and manageability.
Existing tokens remain valid until their expiration date. However, you cannot create new tokens without an active license. This means you can continue using the API with existing tokens even if the license expires after token creation.
No, tokens cannot be extended once created. You must create a new token before the old one expires. We recommend setting up a token rotation schedule to ensure continuous API access.
Yes, tokens are associated with the user who created them and inherit their Confluence permissions. This means the API can only create/update pages in spaces where the user has write access.
Yes, you can revoke tokens at any time from the API Token Management page. Once revoked, the token becomes invalid immediately and cannot be used for API requests.
The API is subject to Atlassian's platform rate limits. We recommend implementing exponential backoff and rate limiting in your application to avoid hitting these limits.
Standard CommonMark syntax is supported. The content is automatically transformed to Confluence ADF (Atlas Document Format). Supported features include:
Markdown image syntax is supported, but images must be publicly accessible URLs. The API will reference these URLs in the created Confluence page. Local images are not currently supported via the API - they must be uploaded separately.
Currently, the API supports page content only. Attachments must be uploaded separately using Confluence's REST API. You can create the page via our API, then add attachments using Confluence's attachment endpoints.
Currently, the API supports title and content updates only. To update page properties, labels, or other metadata, use the Confluence REST API after creating the page with our API.
overwrite: true: You'll get an "already exists" error (400)overwrite: true: The page will be updated with the new content, incrementing the version numberNo, the API currently supports Confluence pages only. Blog post creation may be added in future versions.
Special characters should be properly escaped in the JSON payload. Use standard JSON escaping:
{
"content": "# Title with \"quotes\"\n\nContent with \\backslash"
}
Yes, you can create pages in any space where the token owner has write permissions. Just specify different spaceId values in your requests.
The API is subject to Confluence page size limits (approximately 1MB). For larger documents, consider splitting them into multiple pages.
Tokens are stored encrypted using Forge KVS (Key-Value Store) secrets, which provides bank-level encryption. Tokens are hashed and cannot be retrieved after creation.
Currently, tokens inherit the creating user's permissions across all spaces. Space-specific tokens may be added in future versions. As a workaround, create a dedicated user account with limited space access.
Yes, all API requests are logged for security and debugging purposes, including:
Token values are never logged.
Technically yes, but it's not recommended. Create separate tokens for each application or environment to:
Yes, all API endpoints use HTTPS. Never send tokens over unencrypted HTTP connections.
Yes! The API is perfect for CI/CD integration. Check out our GitHub Actions and GitLab CI/CD examples.
Yes, you can set up webhooks to trigger API calls when documentation is updated in your repository.
Absolutely! That's one of the primary use cases. You can automatically deploy documentation from your repository to Confluence whenever you push changes.
You can make multiple API calls sequentially or in parallel (with rate limiting). See our batch import examples.
Yes, you can write scripts to read from your current system and import to Confluence via the API. The API supports bulk operations through multiple sequential calls.
Common causes:
See Troubleshooting: Unauthorized for solutions.
Tokens expire based on the period selected at creation (1 day to 30 days). Create a new token before the old one expires.
The easiest way is to use the Markdown Importer app itself:
See API Reference: Finding IDs for more details.
Ensure the user who created the token has write permissions in that space. Check permissions in Confluence space settings.
Yes, the REST API is included with all active Markdown Importer for Confluence licenses at no additional cost.
Yes, trial users can create and use API tokens during the trial period. Tokens created during the trial remain valid until their expiration date.
We're constantly improving the API based on user feedback. Submit feature requests through our support portal.
We consider all feature requests. Common requests are prioritized for future releases.
Check our release notes for recently added features and upcoming improvements.
If your question isn't answered here:
Check Documentation:
Contact Support:
Community:
Last Updated: 2025-10-07