Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

pro.coinbase.com/orders - request timestamp expired #453

Open
Bandit253 opened this issue Jul 30, 2021 · 1 comment
Open

pro.coinbase.com/orders - request timestamp expired #453

Bandit253 opened this issue Jul 30, 2021 · 1 comment

Comments

@Bandit253
Copy link

The endpoint was working fine for weeks many thousands of successful trades done against it. then all of a sudden, on Monday, for no apparent reason I only get this response.
POST (401) https://api-public.sandbox.pro.coinbase.com/orders - request timestamp expired

Another odd thing it has affected my non Sandbox API calls.
image

@teleprint-me
Copy link

teleprint-me commented Aug 9, 2021

The CB-ACCESS-TIMESTAMP header MUST be number of seconds since Unix Epoch in UTC. Decimal values are allowed.

Your timestamp must be within 30 seconds of the api service time or your request will be considered expired and rejected. We recommend using the time endpoint to query for the API server time if you believe there many be time skew between your server and the API servers.

Source

The code is generating a timestamp in cbpro_auth on line 16 once a request is made.

The only thing I can think of is that your request timestamp is skewed. There's ways to mitigate it, but I've never had this issue.

The docs provide a suggestion by modififying the timestamp so that the skew doesn't interfere with the request.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants