API
How the API works in Galaxy
- 1.
Endpoints — query your model.
Read records, search across objects, traverse relationships, and fetch lineage through clean REST endpoints that return JSON shaped like your modeled objects.
- 2.
Reference — try before you ship.
The reference lists every endpoint with its parameters, example requests in cURL and JavaScript, and the exact response body, so you can see the shape of the data first.
- 3.
Keys — scoped access.
Create API keys scoped to what a given integration needs. Keys inherit your role and permission rules, so the API can never return data a user couldn't see.
- 4.
Built for production.
Consistent pagination, predictable errors, and stable schemas mean the API behaves the same in your scripts as it does in the app.