Access Token - Client ID Error

gatewaychurchgatewaychurch Posts: 4Member
I am having an issue with my access token request. It provides me an this error.

{"error":"invalid_client","error_description":"The client id supplied is invalid"}
Please assist. 

Thanks,

Michael


13 comments

  • Adrian SamuelAdrian Samuel Posts: 515Moderator, Lightspeed Staff moderator
    Hey @gatewaychurch, please explain in more detail how you got to the stage.

    Walk me through the narrative that lead you to receiving this error and I might be able to help out more

    Adrian Samuel

    API Integrations Consultant - Strategic Solutions

    Lightspeed HQ

  • gatewaychurchgatewaychurch Posts: 4Member

    I am attempting to request an authentication token. I have my url request setup with my client ID and scope. When I supply my credentials it provides me a code via the localhost page. From there I supply that token along with my clientID, client secret, the code provided my the URL, and the grant type as shown via the python example on the API docs. I run the POST request and that is the response that I receive.

  • Alex LugoAlex Lugo Posts: 138Administrator, Lightspeed Staff moderator

    Hello @gatewaychurch,


    The temporary code expires after 30 seconds of being issued. You need to do the exchange before it gets expired.

    Alex Lugo
    API Support Specialist
    Lightspeed HQ
  • gatewaychurchgatewaychurch Posts: 4Member
    edited February 18

    @Alex Lugo I am running the POST call within the 30 second window.

    Post edited by gatewaychurch on
  • gatewaychurchgatewaychurch Posts: 4Member

    @Alex Lugo and @Adrian Samuel, Can someone assist with this? Is there another method to get developer support, because this method has been pretty limited?

  • Adrian SamuelAdrian Samuel Posts: 515Moderator, Lightspeed Staff moderator

    @gatewaychurch, this is the only medium for this conversation.


    Could you try again and see if anything has changed?

    Have you checked that you did indeed copy the clientID correctly?

    If you're still getting the same error, please PM me with your details

    Adrian Samuel

    API Integrations Consultant - Strategic Solutions

    Lightspeed HQ

  • innitsolinnitsol Posts: 1Member

    Did you ever get a solution on this? I am having this same problem.

  • J_M_F_SJ_M_F_S Posts: 3Member

    Was this issue ever resolved? If so, what were the steps of resolution?

    -OR-

    What was the underling issue?

    Thanks.

  • Alex LugoAlex Lugo Posts: 138Administrator, Lightspeed Staff moderator

    Hi @innitsol,

    Are you having the same issue while exchanging the temporary token for the Access Token? If yes, could you please PM me, the API call with the payload and the error message received?

    Alex Lugo
    API Support Specialist
    Lightspeed HQ
  • VaroomVaroom Posts: 2Member

    Hi, we are having the same problems, having just registered a new client, how can we troubleshoot this?


    Cyril

  • LeahLeah Posts: 80Moderator, Lightspeed Staff moderator

    Hi @Varoom can you PM me your client ID please, I'll take a look

    API Support
    Lightspeed HQ
  • inventorysourceinventorysource Posts: 1Member
    edited September 10

    @Leah we are also running into trouble authenticating even though we received our notice that the Client ID was authorized (retail store #149972). See below:


    Can you please review?

  • LeahLeah Posts: 80Moderator, Lightspeed Staff moderator

    @inventorysource While you may have received client approval by us, it doesn't mean that your client has been authorized on the merchant's retail account. That error in postman indicates that you have not completed the OAuth process on the merchant account. Instructions for doing this are found here: https://developers.lightspeedhq.com/retail/authentication/access-token/ If you are able to trade the temporary code (provided when the merchant authorization is completed) for an access token and refresh token, and you are still having troubles, PM me your client ID and I will verify that there is no authorization issue on our end.

    API Support
    Lightspeed HQ
Sign In or Register to comment.