Summary
User is facing issues with triggering connection sync using various API endpoints, receiving 403 Forbidden and 502 Bad Gateway errors.
Question
Hello, I need help. I’m trying to trigger a connection sync through API and so far I’ve tried:
POST /api/v1/connections/{connectionId}/sync
andPOST /api/v1/jobs
(with the body of{"connectionId": "e735894a-e773-4938-969f-45f53957b75b", "jobType": "sync"}
), both returns403 Forbidden
POST /api/public/v1/connections/sync
(with the body of{"connectionId": "e735894a-e773-4938-969f-45f53957b75b", "jobType": "sync"}
), the response took too long and returned with502 Bad Gateway
:
<body>
<h1>An error occurred.</h1>
<p>Sorry, the page you are looking for is currently unavailable.<br/>
Please try again later.</p>
<p>If you are the system administrator of this resource then you should check
the error log for details.</p>
<p><em>Faithfully yours, nginx.</em></p>
</body>
</html>```
I've tried to ask the AI multiple times with no concrete answers. So may I ask what's the correct API for triggering a connection sync?
<br>
---
This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. [Click here](https://airbytehq.slack.com/archives/C021JANJ6TY/p1733914748605639) if you want
to access the original thread.
[Join the conversation on Slack](https://slack.airbyte.com)
<sub>
['api', 'connection-sync', '403-forbidden', '502-bad-gateway']
</sub>