Get started
Introduction
Ghost sits on top of your CRM and turns calls, email, docs and product usage into a graph of relationship, deal and product facts. The API lets your code read that graph and act on it.
Every request goes to a single base URL. The surface is versioned by path and ships labeled beta - response shapes may evolve with notice.
https://app.ghostgtm.ai/api/v1
How the surface is organised
- Capabilities and operations - one catalog endpoint lists every operation your key may run, with its JSON input schema. Read-only operations run immediately through /query; everything else is submitted to /operations and returns a durable receipt.
- Data - explicit, cursor-paginated pages of accounts, people, facts, sources, deals and the context library. No arbitrary queries.
- Definitions and values - the custom fields your workspace defines, and the values assigned to entities.
- Relations - versioned edges between accounts and ICPs, personas, use cases, products and competitors.
- Compute - quoted, credit-capped graph refreshes.
Your first request
Create a key in Dev, then introspect it. The response tells you which capability families this workspace has enabled.
curl --fail-with-body https://app.ghostgtm.ai/api/v1/me \ -H "Authorization: Bearer $GHOST_API_KEY"
Then call GET /capabilities. It is the executable catalog: every operation name, its input schema, required scopes and whether it is available and authorised for the key you hold.
Ghost-MCP and the customer plugin read the same graph. Use the API for full projected records, live CRM validation, scoped graph execution, and capabilities not exposed as MCP tools.