SubsiMail
Why self-host Pricing Docs Changelog Support FAQ Log in Get started
Log in Get started

← Back to Support

API returns 401 even though my key looks correct

#55 Resolved
Christopher C. 283 days ago

Getting a 401 Unauthorized on every API call. I copied the key directly from the dashboard so I don't think it's a typo.

Carol Wright Staff 283 days ago

A couple of common causes: are you sending the key as a Bearer token in the Authorization header (Authorization: Bearer YOUR_KEY), or somewhere else like a query parameter? We only accept it in the header. Also worth double-checking there's no trailing whitespace or newline character if you copied it from a file rather than directly from the dashboard.

Christopher C. 283 days ago

I was passing it as a query param actually, not the header. Switched to the Authorization header and it's working now.

This ticket has been resolved. Its author or SubsiMail staff can reopen it to reply further.

Other tickets

Resolved What ports do I need open for self-hosting SubsiMail behind a firewall?
Christopher C. 3 replies
Resolved Is there a Docker install guide? First-time setup keeps failing.
Steven Y. 3 replies
Open Can I rename my workspace/organization?
Benjamin H. 0 replies
Resolved Rate limits — how many requests per minute are allowed?
Jacob W. 1 reply
Resolved Which SMTP port should I use, 587 or 465?
Amanda P. 1 reply

SubsiMail

The self-hosted alternative to Mailshake.

Documentation Setup guides Changelog Support Pricing Affiliates Terms of Service Privacy Policy Sitemap

Compare

vs. Instantly vs. Smartlead vs. lemlist vs. Apollo

Solutions

For agencies For recruiters

© 2026 SubsiMail.

We use Google Analytics to understand traffic to this site. It only runs if you accept -- see our Privacy Policy.