Endpoint https://api.letsdeel.com/rest/v2/contracts/:id returning 502 and 504

Bug Reports
1

For about a day and a half we have been receiving 502 and 504 errors when requesting endpoint https://api.letsdeel.com/rest/v2/contracts/:id.

<html>
<head><title>504 Gateway Time-out</title></head>
<body>
<center><h1>504 Gateway Time-out</h1></center>
<hr><center>nginx</center>
</body>
</html>

<html>
<head><title>502 Bad Gateway</title></head>
<body>
<center><h1>502 Bad Gateway</h1></center>
<hr><center>nginx</center>
</body>
</html>

Here are two contract IDs: 3g4zv52 and 3yv6z6y.

2

Hi David,

Thanks for reaching out.

I’m looking into it, sorry for the inconvenience.

1 Like
3

Hi @guilherme_deel! Any updates here? Tks!

4

Hi @davidaraujo,

Sorry but still investigating. I was able to successfully call rest/v2/contracts/:id today with the contract ids you provided but still investigating why you can’t on your side.

5

@guilherme_deel,

Today 9:10:38 AM GMT, I got the error for both contract IDs.

6

Hi @davidaraujo,

Sorry for the delay. We released a potential fix for the issue you’re experiencing, can you please check if you are able to get the contracts?

2 Likes
7

Hi @guilherme_deel,

We’ve seen a sharp increase in failures with our Deel integration today. Upon further investigation, we are seeing that there has been a change to the required scopes for accessing the /rest/v2/people endpoint. This has affected at least ~50 (potentially more) clients connected through our platform.

This would be a breaking change for all of our customers. Can you confirm that this change was made on your end, and if so then please roll back the breaking change?

Thanks,
Shoabe

8

Hello @shoabe.shariff we fixed the issue with scopes for /rest/v2/people it should work as before, may I ask you to try it again? And sorry for the inconvenience