Revoke Token API not Working Properly. | The place for Zendesk users to come together and share
Skip to main content
G
Gokul
March 29, 2023
Question

Revoke Token API not Working Properly.

  • March 29, 2023
  • 19 replies
  • 69 views

When revoking an Access Token using the ID of the Token, it gets revoked with no problem.

DELETE /api/v2/oauth/tokens/{oauth_token_id}

But when revoking it with current.json endpoint, the response we get is 204 but the token is not revoked. We have full write and read access with that token. But I don't know why it not get revoked.

DELETE /api/v2/oauth/tokens/current.json

Looking for your reply. Thanks.

    19 replies

    Show previous replies
    G
    GokulAuthor
    December 26, 2023

    @greg29

    Any updates on revoking token problem?

    G
    GokulAuthor
    April 25, 2024

    Hello Greg

     

    Is there any Updates on this?

     

    Thanks,
    AppuSamy

    Greg K
    Greg KEmployee
    Employee
    May 9, 2024
    Hi all! This issue should now be resolved. Please let us know if you're still experiencing any issues.
    Dinesh12
    Dinesh12
    October 8, 2024

    I revoked the latest token,  and when i try to regenerate new token, the screen that should ask user to confirm the access, does not come up. 
    It is creating issue for us, if we want to add more scope as part of the new token, it is not alllowing that. Unless all the tokens for the users are deleted , is there any api call to delele all tokens for the user

     

    C
    Christopher53Employee
    Employee
    October 10, 2024
    Hi Dinesh,
     
    When you try to get a new token, does your integration redirect the user to the authorization page with the new scope details?  If so, are you receiving an error?
    Dinesh12
    Dinesh12
    October 10, 2024

    Yes, we redirect user t authorization page, however that page does not come up, unless all the previously generated tokens are not revoked, that puzzles me whey there are multiple tokens for the same user and same client id. So i had to retrive all the existing token and revoke them one afrer another, is this expected behavior for one user ot have multiple token.

    Please let me know.

    Dinesh12
    Dinesh12
    October 10, 2024

    then I see the authorization page is coming up fine.

    Dinesh12
    Dinesh12
    March 14, 2025

    I am having issues with api call https://subdomain.zendesk.com/api/v2/oauth/tokens?client_id={client_id} only for one of client id which is only 4 digit long, it returns the empty response, however  if i make call https://{subdomain}.zendesk.com/api/v2/oauth/tokens i see the response having client id,  which i pass into first call, any reason why would it do, also since there multiple client_ids I see in the https://{subdomain}.zendesk.com/api/v2/oauth/tokens response. for others it returns correct response only the one with 4 digits is having issue

     

     

    C
    Christopher53Employee
    Employee
    May 12, 2025
    Hi Dinesh,
     
    The client might be a Global OAuth client.  If so, you'll need to filter using the global_client_id parameter instead.
    Terms & ConditionsAccessibility statement