GraphQL integration
Crystallize GraphQL integration for Draftbit
Crystallize Catalogue API
What is Crystallize?
The Catalogue API is Crystallize's read-only storefront endpoint. Public catalogues need no auth; protected catalogues require a static auth token.
Use Crystallize with Draftbit
- Schema discovered automatically via GraphQL introspection.
- Queries, mutations, and subscriptions usable across screens and AI agents.
- Auth headers configured once and reused for every operation.
- Works with custom Crystallize schemas and federated graphs.
Example
crystallize-query.graphql # Example query against Crystallize
query GetItems {
items(limit: 10) {
id
name
createdAt
}
}Use cases
- Show a product catalog with prices and inventory
- Add a cart, checkout, and order history
- Sync orders between the storefront and the app
Authentication
Add any required auth headers when you connect Crystallize. Headers are stored per app and applied to every operation.
Use Crystallize in a Draftbit app today
Start free, connect Crystallize in minutes, and ship with AI agents that know how to use it.
Frequently asked questions
What is the Crystallize GraphQL integration?
The Catalogue API is Crystallize's read-only storefront endpoint. Public catalogues need no auth; protected catalogues require a static auth token.
How do I connect Crystallize to a Draftbit app?
In your Draftbit app, go to Integrations and then GraphQL and choose Crystallize. Enter the endpoint URL and any auth headers. Draftbit introspects the schema and exposes its operations to your app and to the AI agents.
Do I need to write GraphQL queries by hand?
No. Once Draftbit has introspected the Crystallize schema, you can bind components to operations visually, and the AI agents can compose queries against the live schema.
What can I build with Crystallize and Draftbit?
Most teams use Crystallize as a commerce platform for their app. You might use Crystallize to show a product catalog with prices and inventory, or to add a cart, checkout, and order history.