#nel

1 messages ยท Page 1 of 1 (latest)

versed oakBOT
karmic scaffold
#

Can you share an example request where you see this error?

#
#

eg req_123

versed oakBOT
fluid salmon
#

Sorry @karmic scaffold but any request to that account ends in 403 and there is no request id in that case...

karmic scaffold
#

Gotcha -- can you share the account id?

fluid salmon
#

The account id is : acct_1M6c7qQM849fSYpD

karmic scaffold
#

Ok thanks, looking at this.

#

Can you share an example request snippet (the code you're running) -- make sure to remove any secret keys or private info

#

Is it possible you're making the request using keys for another account you have access to, rather than the account this express account belongs to?

fluid salmon
#

If I'm using another account (listed in the connected accounts) it works fine.

#

Example with request id : Request-Id: req_paDD4gI44XzxwV

#

As an example of failure (but all requests related to the account will fail) this request fails:

http -a s_k_l_i_v_e_XXXXXXXXXXXXXX: https://api.stripe.com/v1/accounts/acct_1M6c7qQM849fSYpD
wraith merlin
#

๐Ÿ‘‹

#

Sorry for the delay! Taking a look

#

Okay so yeah looks like you are using OAuth here

#

And I can see on that account an internal error that we log that indicates the OAuth Token was consumed twice by your integration. When this happens, the account gets disconnected from the platform

#

Which is why it seems that it is "deleted"

#

However, if you want to keep using OAuth then you will want to debug your integration to ensure you aren't consuming the OAuth token multiple times.

#

@fluid salmon tagging you just to ensure you see the above info

fluid salmon
#

I'm not sure to understand how we can "consume" and what triggers this "consumption", I'm going to investigate.

#

Thank you for your answer, I may get back here with more information.

wraith merlin