rConfig API clients by language
The recipes are organised by the integration they build. These pages are organised by language. Each shows the same five things, so you can start a client in the language your team already uses: sending the token, testing the connection, reading one item, following every page of a list, and handling errors.
| Page | Good for |
|---|---|
| Python | Integrations with real logic: sync jobs, reports, pipeline stages, webhook receivers |
| curl and jq | Trying endpoints by hand, quick shell scripts, CI steps |
Whatever the language, the rules are the same. They are set out in how the API behaves: the token goes in the apitoken header, v2 lists are paged and capped at 100 per page, and some calls only start work.