Question
How can I authenticate API requests using one of Zendesk v2 APIs?
Answer
You must be a verified user to make API requests. To authenticate API requests, you can use basic authentication with your email address and password, your email address and an API token, or an OAuth access token.
All methods of authentication set the authorization header differently. Credentials sent in the payload or URL are not processed.
To view information on each authentication method, click each of the tabs below.
Password authentication
API token authentication
OAuth access token authentication
Password authentication
If you use basic authentication, combine your email address and password to generate the authorization header. To use basic authentication, Password Access must be enabled in the Admin Center interface at Apps and integrations > APIs > Zendesk API, as well as within the relevant authentication section (either Team Member or End User).
The email address and password combination need to be a Base-64 encoded string. For an example of how to format the authorization header, see the code block below.
Authorization: Basic {base-64-encoded email_address:password}
API token authentication
If you use an API token, combine your email address and API token to generate the authorization header. The email address and API token combination need to be a Base-64
encoded string. For an example of how to format the authorization header, see the code block below.
Authorization: Basic {base-64-encoded email_address/token:api_token}
OAuth access token authentication
If you use OAuth to authenticate, format the authorization header as seen below.
Authorization: Bearer oauth_access_token
For more information, see this article: Using OAuth authentication with your application.
Viewing your authorization header
To see exactly what your app sends, use a third-party page such as Request Bin. Compare your headers to those being generated by a webhook using an OAuth authentication. Point the webhook to your requestb.in URL and, on the Add webhook page, click Test webhook to see this in action:
Once the request hits your requestb.in, it appears like this:
The string after Authorization: Bearer
is the API key provided by RequestBin in your account settings under Programmatic Access.
If you use python to make requests, set your session headers as follows.
session = requests.Session()
session.headers = {'Content-Type': 'application/json', 'Authorization': 'Basic Basic_64_encoded_code'}
For more information, see the developer documentation: Security and authentication.
16 Comments
Hi, I'm working on a custom request form for our end-users (but still within our Zendesk subdomain). When I try to submit the form and send the data to create the request, it returns with a 403 error. The same code works on postman and the request is being created.
I'm having a hard time figuring out why im getting a 403. I tried both email/token:api_key authentication and basic email:password authentication.
https://support.zendesk.com/hc/en-us/community/posts/1260800839050-403-error-when-creating-request-via-API
@...
I think my code 5 post above will help you.
https://support.zendesk.com/hc/en-us/articles/115000510267/comments/360005066074
@Tomer did you mean the base64 encoded? I did that, my email/token:api_token is encoded. I tried manually encoding it using one of the websites and also dis btoa('email/token:api_token'); but both gave me a 403 error.
Hi @...
I am getting the same authentication error. Can you please help me on this? I also created a ticket on this.
C:\Users\yyy> curl https://<subdomain>.zendesk.com/api/v2/users.json -u yyy@<company>.com/token:xxxxxxx
{"error":"Couldn't authenticate you"}
Thanks
-Bheem
Hi Team,
Precindition: Token is created in zendesk
I as an admin share my email address and token with other team member. Can they acess the API's? or is it like i need to login to zendesk from the same system/pc from where the user is trying to access the API's?
Or they can just pass my email address and token simply without i being logged in to zendesk?
Regards,
Waseem
Waseem Khan
Simply having your email & API token is sufficient for any user to make API requests on behalf of your user. This gives them the ability to do anything your user would be able to do via the API. This includes deleting things like tickets/users/organizations/articles/sections/categories/triggers which can be very destructive. For this reason, I would encourage you to be very selective about who has access to these tokens.
Please make it clearer on this page that you have to Base-64 encode the token. Here's the command that I used on Mac to Base-64 encode my token.
HeyO Nick,
Thanks for the feedback. I will make updates to this article to make that clearer.
I just ran into and resolved an issue using Postman for API requests where the following was returned:
Per the API documentation I was using the following so everything should have been set up correctly:
Turns out, when the base64 encoded Authentication value was being decoded in Postman, it was adding an additional colon : to the decoded username string (I had to check this using a third-party decoding site).
To resolve, I had to:
At that point my requests started going through. Hope this helps anyone else that runs into this with Postman!
I have setup SSO for my end users.
I want to show some of the Zendesk content on my own web app platform without having to proxy the requests to Zendesk API through my server.
Is there any option to issue /api/v2/help_center/* requests with the JWT token I get from /access/jwt endpoint?
Also what about CORS? Of course for now I get only 401 response but I see it is not supporting cross origin requests.
Hi! I'm trying to use Azure Logic Apps to Authentic for a POC but I keep getting 401 Couldn't authenticate you.
I've encoded my username/token:aaaa via powershell this way but I must be missing something.
$text = "myname@mydomain.com/token:tokentexthere"
$encoded = [convert]::ToBase64String([text.encoding]::Unicode.GetBytes($text))
$encoded
I went through this article and tried OAuth, api, user/password but just not getting authenticated.
Any ideas would be welcome!
Hi Fraser, Vanessa
After doing that encoding are you passing the encoded value in as a Basic Authorization header as documented here: https://developer.zendesk.com/api-reference/introduction/security-and-auth/#basic-authentication
If that doesn't help sort things out for you, I recommend contacting our support team to look into logs for your specific account.
I'm sure it is something I'm doing wrong but I have been over and over that article and am not seeing what I have done wrong. I'll contact support. Also I can curl using the email/token:tokeninfo so it has to do with my encoding of the email/token:tokeninfo.
Hello, SSO authentication works to customer's side?
We don't have our customer's zendesk password.
Yes, you can use SSO for your end users. Please refer to Providing multiple sign-in options for team members and end users.
Hi All!
If you are working on macOS, I recommend that you follow the tip given by Nick Bolton. I tried to create the base64 code using the -i option of the base64 comman, but it kept adding an extra character to the end of encoded output.
Cheers!!
Dermot
Please sign in to leave a comment.