For Agents
Run GraphQL queries and mutations against DG1's digital experience platform to manage products, pages, contacts, bookings, and orders through a single endpoint.
Get started with DG1 GraphQL API in minutes using your preferred integration method.
# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
"jentic": {
"url": "https://api.jentic.com/mcp",
"auth": "oauth"
}
}
# Then ask your agent:
"list products in the dg1 catalogue"
# → Jentic returns the GET /events tool with parameter schema, agent executes.What an agent can do with DG1 GraphQL API API.
Query product catalogue, pricing, and inventory through GraphQL selection sets
Create and update website pages, blocks, and content blocks within DG1 sites
Manage contact records, segments, and consent state for marketing flows
Create, reschedule, and cancel bookings against DG1-managed services
GET STARTED
Use for: I need to query the product catalogue for in-stock items, Create a new contact record in DG1, Update the pricing on a product variant, Retrieve all bookings for a specific service this week
Not supported: Does not handle payment processing, email delivery, or hosting infrastructure — use for DG1 storefront, booking, and contact data operations only.
The DG1 GraphQL API is the single-endpoint backend for DG1's all-in-one digital experience platform, covering product catalogues, content pages, contact records, bookings, orders, and marketing assets. Every read and mutation goes through one POST /graphql endpoint and is selected by GraphQL query or mutation name, so agents and apps fetch only the fields they need. It is the system of record for any storefront, booking flow, or CRM workflow built on DG1.
Submit and track orders, invoices, and payment status for storefront purchases
Authenticate and refresh user sessions through GraphQL auth mutations
Patterns agents use DG1 GraphQL API API for, with concrete tasks.
★ Headless Storefront Backend
Power a custom storefront or mobile app with DG1 as the catalogue and order backend. The GraphQL endpoint lets the front-end fetch products, variants, prices, and inventory in a single request, then submit orders and payment intents through mutations. Adopting GraphQL means clients pull only the fields they render, keeping mobile payloads small.
Query the catalogue for products tagged summer-2026 with price and inventory, render them, and submit an order mutation when the user checks out
Booking and Service Management
Manage service bookings — appointments, classes, rentals — through DG1 GraphQL mutations. The API exposes booking creation, rescheduling, cancellation, and availability querying, making it suitable for service businesses that need a programmable scheduling layer.
Query availability for service id svc-42 next Tuesday, create a booking for the requested time slot, and email the confirmation
Contact and CRM Synchronisation
Synchronise customer records between DG1 and an external CRM or marketing tool. Agents can read contact lists, push new sign-ups in, and update consent state on the way out — all through GraphQL queries and mutations on the contact resource. Useful for unifying storefront identity with downstream marketing systems.
Fetch all contacts created in the last 24 hours, push them to the marketing platform, and update their dg1Synced flag via mutation
AI Agent Commerce Operator
An AI shopping or operations agent can use DG1 as its commerce backend through Jentic. The agent searches for the operation matching the user's intent (browse products, place an order, cancel a booking), Jentic returns the GraphQL document and variable schema, and the agent executes — without learning the schema in advance.
When a user asks to cancel their booking, find the booking by reference, execute the cancelBooking mutation, and confirm the refund status
1 endpoints — the dg1 graphql api is the single-endpoint backend for dg1's all-in-one digital experience platform, covering product catalogues, content pages, contact records, bookings, orders, and marketing assets.
METHOD
PATH
DESCRIPTION
/graphql
Single GraphQL endpoint for all queries and mutations
/graphql
Single GraphQL endpoint for all queries and mutations
Three things that make agents converge on Jentic-routed access.
Credential isolation
DG1 Bearer tokens are stored in the Jentic vault and never appear in agent prompts. Jentic injects the Authorization header at execution time only.
Intent-based discovery
Agents express intent in natural language ("cancel a booking", "list products in stock") and Jentic returns the matching DG1 GraphQL operation with its variable schema.
Time to first call
Direct DG1 integration: 1-3 days for GraphQL client setup and schema exploration. Through Jentic: under 1 hour — search, load, execute.
Alternatives and complements available in the Jentic catalogue.
Shopify Admin API
Larger headless commerce platform with its own GraphQL Admin API and broader app ecosystem
Choose Shopify when the agent needs an established marketplace, payment, and shipping app ecosystem rather than DG1's all-in-one footprint
Stripe API
Payment processing for orders submitted through DG1
Use alongside DG1 when payments need to be captured outside of DG1's built-in checkout flow
SendGrid Mail API
Transactional email for booking confirmations and order receipts
Use when DG1 contacts need richer transactional email delivery than the platform's native messaging
Specific to using DG1 GraphQL API API through Jentic.
What authentication does the DG1 GraphQL API use?
DG1 uses HTTP Bearer authentication. Every POST to /graphql must include an Authorization header carrying a DG1-issued token. Through Jentic the token lives in the encrypted vault and is injected at execution time only.
Can I manage products and bookings in a single request?
Yes. Because the API is GraphQL on a single /graphql endpoint, a query can select fields from products and bookings together in one round trip, and a mutation can update both within one request body.
What are the rate limits for the DG1 GraphQL API?
DG1 does not publish a public rate limit. Fair-use throttling applies and large queries can be split using GraphQL pagination cursors to avoid timeouts.
How do I cancel a booking through Jentic?
Run a Jentic search for "cancel a booking". Jentic returns the DG1 cancelBooking GraphQL mutation along with its input schema (booking ID, reason). Load the schema, populate variables, and execute — no need to read the GraphQL SDL.
Does the API support partial field selection?
Yes. GraphQL requires the client to specify which fields to return, so an agent fetching only product name and price avoids transferring the full product object. This is the main efficiency advantage over a REST equivalent.
How do I install the Jentic SDK to call DG1?
Run pip install jentic, set JENTIC_AGENT_API_KEY to your ak_* key, then use Jentic with SearchRequest, LoadRequest, and ExecutionRequest. Sign up at https://app.jentic.com/sign-up.