Skip to main content
PDF4me APIIntegrationsKnowledge BaseExtensionsAPI Tester

Fix 401 Not Authorized

A 401 Unauthorized response from PDF4me means your request could not be authenticated. The API did not accept the credentials you sent.

What You Might See​

HTTP Status
401
Error Message
Not Authorized

What to Do​

  1. Get a fresh API key from the PDF4me Dashboard
  2. Copy the key carefully – avoid any extra spaces or line breaks
  3. Update your connection – In Power Automate, Zapier, Make, or n8n, re-enter the API key in the connection settings
  4. For direct API calls – Check that the Authorization header is set correctly and contains the full key
  5. Regenerate if needed – If you suspect the key was exposed, create a new one and replace it everywhere

Common Causes​

Invalid or missing API key

The API key is wrong or not present. This can happen when the key was mistyped, revoked, regenerated in the dashboard, or never set in your integration.

Extra spaces or hidden characters

When pasting your API key, you may have included a leading or trailing space, a newline, or hidden characters. These make the key invalid even if it looks correct.

Wrong authentication method

REST API uses the Authorization header. Power Automate, Zapier, Make, and n8n use the connection's API key field. Ensure you're using the correct method for your integration.

Get API KeyBack to TroubleshootingGetting Started