GraphQL API
The CRE GraphQL API gives you programmatic, read access to your organization's CRE resources and workflow execution data.
Use the API to:
- List and inspect deployed workflows and their deployments.
- Retrieve workflow executions, including status, timing, and errors.
- Investigate failed executions using execution logs and execution events (the capability-level timeline for an execution).
- Export workflow and execution data into your own dashboards, alerting, or observability systems.
- Retrieve your account and organization details.
The API is a single GraphQL endpoint. Every request is an HTTP POST with a GraphQL query in the body — there is no REST equivalent.
Endpoint
| Environment | Endpoint |
|---|---|
| Production | https://api.cre.chain.link/graphql |
There is no separate staging endpoint documented for external use.
POST /graphql
Host: api.cre.chain.link
Content-Type: application/json
Authorization: Apikey <CRE_API_KEY>
Authentication
Every request requires a CRE API key, which in turn requires your account to have deploy access approval. See Authentication for how to create a key and send it on each request.
Make your first request
See the Quickstart to send your first request with cURL, TypeScript, or Go in a few minutes.
Explore by task
The Common Queries guide organizes example queries by what you're trying to do — list workflows, find failed executions, retrieve execution logs — rather than requiring you to explore the schema first.
Explore the schema
- Query Reference — every query, its arguments, and its return type
- Object Reference — every object type and field, including scalars
- Enum Reference — every enum and what each value means
- Input Reference — filter, sort, and pagination input types
API concepts
- Pagination — how to page through large result sets
- Errors & Rate Limits — HTTP vs. GraphQL errors, and current rate-limit behavior