Send data in. Nothing to read out yet.

• Connections to platforms (LinkedIn, TikTok, email senders, analytics and more) use each platform's official sign-in and official APIs, set up from inside the app by the business owner. Nothing is scraped.
• Send your own data in with an API key. On the Connections page, under For developers, the business owner connects Public API and is shown one key, once. Post metrics, revenue figures, leads or customers as JSON to the endpoint it shows, with the key in an x-api-key header. What you send is stored against that one business.
• Zapier, Make and Public Webhooks give the business a webhook address and a secret, shown once, for the same kind of data. Send the secret in an x-webhook-secret header.
• An MCP server for AI assistants at https://growthdept.app/mcp (Streamable HTTP, one POST endpoint, bearer token). It reads the business's activity, approvals, hosted pages, website health and Google positions, can launch a campaign or ask a question (both metered as Growth Credits), add places, and record the owner's yes or no when the owner asked. It never publishes. The key is minted under For developers, AI assistants, and the plain-words steps are on Use with Claude or ChatGPT. OAuth sign-in is next; today the key is a fixed bearer header.
• Hosted landing pages built by GrowthDept are served under /p/<slug> with a per-business sitemap.
• Billing is Stripe-hosted Checkout and the Stripe Customer Portal.

No SDK and no outbound webhooks. The only way to read GrowthDept data back out is through the MCP server above, which is built for AI assistants rather than for your own code. There is no written reference for the ingest fields yet, so ask us if you need them. We haven't built the rest, and we won't list it here until it works.

If you need programmatic access for a client, email support@novastacks.co.uk with what you're trying to do. Our Security Policy describes how data is handled.