Orderby and Limit Issue with GET Connections Endpoint in Public API

Summary

The user is experiencing issues with the GET connections endpoint in Airbyte’s public API related to orderby for sorting connector sets and exceeding the documented limit of 100 connectors.


Question

[Public API Airbyte] Hello,
We use Airbyte’s public API and in particular the GET connections endpoint. We want to retrieve all our connectors (around 150 at the moment) and when we tested the limit and offset parameters to create smaller sets of connectors (sets of 25), we found that the same connector was present in both sets and that other connectors were not present. Is there an orderby to sort the connector set (not seen in the doc)?
On further testing, we set a limit of 200 and the API accepted our request, whereas the max is set at 100 according to the documentation: is the documentation out of date, or is there a certain tolerance that will disappear in a future version? Thanks for your answers!



This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. Click here if you want
to access the original thread.

Join the conversation on Slack

["public-api", "get-connections-endpoint", "orderby", "limit", "connector-set"]