This is an organizational tip that can help us help you better. It is a very easy method to set up and use. It will allow us to isolate individual calls in our logs that are being made that may be problematic, or ones that you may wish to know more about.
If you have an agent profile that is set up for the purpose of making API calls to your Zendesk account then you can create secondary user email identities for separating out which development projects are using which addresses to make their API calls, even though they may be using the same API token.
For any individual projects that use an API token then you can add a +address to that primary email address so that we can isolate calls more easily.
- Your Primary Admin user profile identity: email@example.com
- You add a secondary identity: firstname.lastname@example.org
- You add a tertiary (and one and on) identity: email@example.com
Things to consider:
- You will want to verify that the Primary email address for that user profile is able to receive email and has been verified.
- Also, you will want to make sure that your email provider accepts +address emails. This can be verified just by emailing firstname.lastname@example.org (example) from any email client and verifying that email appeared in the inbox for email@example.com. The acceptance of +address emails is not a strict requirement of using this method, but it is a useful backup in the event that the primary address loses its verification for any reason, which may cause us to email a secondary email identity (if that secondary address is verified).
Now, when you make calls from a certain user identity we are able to more easily scope down the log searches on our side to that identity, which can allow you to notify specific developers more quickly if a problem emerges.
Note: If you are using a password and basic auth then the address of the identity will appear in the API Dashboard. However, for most development projects it is advisable to use an API token. If your token is not named then the API Dashboard will reveal the first 8 characters of the token. Adding additional tokens does not increase your account's API rate limits.
This method does not work with Oauth tokens.