🔐Authentication
Learn about the authentication schemes of the Mailzeet API.
Last updated
Learn about the authentication schemes of the Mailzeet API.
Last updated
Mailzeet API endpoints are secured with API keys, which you can create from the dashboard. You must include your API key in all API requests to the server as a header field.
To interact with the Mailzeet API, you must follow each of your requests with an Authorization header including your API key.
API keys must remain secret and should not be used publicly. For better safety, always use the secret keys on the backend server as environment variables if possible. If you suspect your secret key has been compromised and you want to reset it, you can do so from the dashboard.
You can manage your API key from the dashboard, on the Settings page on the Access key tab.
Each API request should include the API key or token, sent within the Authorization header of the HTTP call using the Bearer method. For instance, a valid Authorization header looks like this: Bearer faeawrafaf:01J2RJJBC6190R7GXK147HXNN5.
Typically, our SDKs offer shortcuts to simplify setting the API key and interacting with the API.
In the example below, we use an API key for the POST method to send an email.
Do not set VERIFY_PEER to FALSE. Ensure your server verifies the SSL connection to Moneroo.
