Users can control DefiniteMail API keys by following some simple instructions. An API key is a passcode given to track API usage of an app. It is connected to your DefiniteMail account in such a way that you don’t require a password to access your account.
Sign in into personalized DefiniteMail account and gain permission to use dashboard. This attribute permits the user to manage, track and create their personalized keys.
The web service of DefiniteMail consists of numerous endpoints. These endpoints enable the user to connect to online resources via URL. The users should add API in URL so that the API in the URL can assist the users to send requests to DefiniteMail. For example, you can add api_key URL parameter to the requests that you send to DefiniteMail. You can add api_key like this: ?api_key=your-definitemail-api-key.
Choose an App-compatible API Key
Employing a centralized API key is most appropriate workflow; linked with your account. It suggests that you can deploy your account such that a single key has enough capacity to cover the usage of every user. You can also create multiple keys if you wish to work without an account or track the billing information or usage of a particular client.
This version links personal DefiniteMail account with application’s API Keys. Resultantly, the user is liable for key usage cost that turns out as a result of key deployment. In order to avoid unforeseen cost, users can set a limit on their account. In this way, they will be able to control their spending. However, the app may not function properly after the set limit is reached.
The app may provide an option that enables users to enter API keys from their personalized DefiniteMail accounts. Nonetheless, in this way, users can manage free cost limits. In this way, you will be responsible for the cost of usage. To implement this feature, the app must inform users about the requirement of a valid API DefiniteMail key. Or else, the user may face certain errors in DefiniteMail service.
Keep API Keys Protected
In order to hide API key from the sight of the user, the client requires taking help from a proxy system. On another hand, if users ever feel that their key is being used by another user without their permission or that it has been compromised, then they should instantly inform DefiniteMail. Similarly, they can rotate API keys periodically or delete them in the app. currently; use of an API key is not limited to a specific web domain.
Users can add a sources limitation in their YAML scene file for API key; it outlines Tangram map.
"message": "Error Message"
"message": "Error Message"
"key" : "DC_SERVICE_KEY",
"list_id" : "TEMPLATE_ID",
"email_address" : "EMAIL_TO",
"cdm_key" : "CDM_KEY",
"email_name" : "NAME_TO"