PDFen.com is getting a completely new website, a simpler and modern platform. The expected go-live date is December 29, 2025. Your existing API integrations will continue to work, but there are important changes you need to be aware of.

Important Dates

• December 29, 2025: New website goes live with API v2 for existing and new users
• December 29, 2025: New website will still support API v1 for existing users
• June 1, 2026: The current API v1 will be completely shut down

What do you need to know?

• Your current code will continue to work with API v1 until June 1, 2026 - full backwards compatibility
• API v1 has been rebuilt on the new platform, there may still be some teething problems, although we have tested it thoroughly
• API v1 will be shut down on June 1, 2026 - migration to v2 is mandatory
• New users can only use API v2
• API v2 - has a simplified, modern approach

Authentication Changes

API v1: Will continue to work as you are used to (username/password)

API v2: Works with API tokens (required). More secure and easier to manage via your profile.

How to create an API token for v2 (from December 29, 2025)

1. Log in to your PDFen account
2. Go to Profile → API Tokens
3. Click "Create new token"
4. Copy the token immediately (it will only be shown once!)

Actions you need to take now!

1. Set your default template - Make sure the template that needs to be copied is set as default in the current PDFen system
2. The new website initially supports 1 template (called cover page) and will load it if set on the old website
3. Would you like to test API v1 on the new website already? You can, just send us an email and we will create an account for you. You only need to change a URL.

What to do after the new website launches

These are the steps you need to take:

1. Log in to your account on the new website (www.pdfen.com)
2. Test your existing API integration - Your v1 API code should still work, but test this to be sure
3. Create a cover page template - this will load the defaults from the legacy template on the old website into the new website
4. Prepare for v2 migration - Start reviewing the v2 API documentation and plan your migration before June 1, 2026
5. Update your code gradually - Migrate to API v2 when you are ready, but you have until June 1, 2026

New Platform Benefits

• Improved performance and reliability
• Lower credit usage
• Better security
• More conversion options
• Better error handling
• Real-time conversion status updates
• Many future features and updates

Need Help?

For questions about the migration or API changes:

• Email: This email address is being protected from spambots. You need JavaScript enabled to view it.

Last updated: December 5, 2025