question

jeremyinvoiceasap avatar image
jeremyinvoiceasap asked jeremyinvoiceasap commented

Access token specifies merchant read permissions, but cannot read merchant

After making a call to:

https://apisandbox.dev.clover.com/v3/access_tokens/

I receive back the following result:

{
    "id": "[token removed]",
    "permissions": {
        "elements": [
            ...
            {
                "name": "MERCHANT_R"
            },
            ...
        ]
    }
}

I then make a call to:

https://apisandbox.dev.clover.com/v2/merchant/name?access_token=[token removed]

And get back:

{
    "message": "401 Unauthorized"
}

This was working two days ago, and I'm not sure what could have changed.

3 comments
10 |2000

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Mike M avatar image Mike M commented ·

What does the response of using this API return? /v2/app/valid_token?access_token={token}

0 Likes 0 ·
jeremyinvoiceasap avatar image jeremyinvoiceasap commented ·

That API endpoint says the token is invalid.

I tried making a call to

https://apisandbox.dev.clover.com/v3/access_tokens/

again and this time it was not successful.

I then tried fetching the token from inside the app and it pulled down a new token. This token is able to make all three API calls successfully.

Thank you for your help! I must say that this issue of stale access tokens being retrieved from the testing devices is becoming painful!

0 Likes 0 ·
Mike M avatar image Mike M commented ·

I completely understand your frustration. We are always looking at ways to improve our API and are continuing to track this issue.

0 Likes 0 ·

1 Answer

hammer avatar image
hammer answered

OBE - Closing dead thread.

10 |2000

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Welcome to the
Clover Developer Community