Developer docs

Integrate Dinabite

Public reference for tracking, forms, bookings, and the workspace API — no login required to read. Copy-paste snippets below; replace placeholders with values from your Dinabite workspace.

Building with an AI assistant? Share this page URL. To get your tracking key and API tokens, sign in and open Settings → API or Tracking.

Start here

Pick the path that matches what you're building:

  • Marketing site on WordPress, Webflow, etc. — add the tracking embed, then optionally send server events from your backend.
  • Custom app or automation — create an API key and use /api/v1 for contacts, deals, and form submissions.
  • Lead capture without building a form UI — link to a hosted Dinabite form or embed the booking page.
  • Talk to this workspace from Claude — connect the Dinabite assistant so Claude can draft posts, review Needs you, and work in your inbox with your approval.

Use Dinabite from Claude

Dinabite has a remote MCP server, so Claude (and Cursor, ChatGPT, or any MCP client) can work in your workspace: look up contacts and analytics, write and schedule posts, run campaigns and outreach, reply to comments and reviews, and book meetings.

Server URL: https://mcp.dinabite.ai

Connect

  • Claude (claude.ai, desktop, mobile): add the Dinabite connector, or add a custom connector with the server URL above. Sign in with your Dinabite account, pick a workspace (agencies can connect all client workspaces), and choose an access level.
  • Claude Code, Cursor and other clients: create a connection key in Settings → API and paste the command shown there. Keys have read and write access to one workspace.

Sign-in uses OAuth 2.1 with PKCE. Clients can register dynamically or use a client ID metadata document. Access tokens last an hour and refresh for up to 30 days.

Access levels

  • Full access (the default): everything below, plus boosting posts, pausing ads, creating and sending invoices, workspace settings, brand, agents and automations, adding team members, creating client workspaces (agency-wide connections), and approving what your Dinabite agents have queued in Needs you (approve_action, reject_action).
  • Read and write: the day-to-day work. Create, edit and approve posts, contacts, deals, segments, forms, blog posts and campaigns, reply to messages, and act for you. It can schedule and publish posts, send email campaigns, reply to comments, reviews and inbox messages, start outreach sequences, publish blog posts, and book, move or cancel meetings without a further review step in Dinabite. Your assistant may still ask you before each action, depending on its settings. No settings, ad spend or invoices.
  • Read only: look up contacts, deals, analytics, posts, inbox, campaigns, outreach, ads, invoices and bookings, and use AI research and writing (documents, marketing plan). It can't post, send, or change anything.

Connections never get billing. A sign-in connection is also limited to what your own role in the workspace allows.

What it can do

  • Social: draft, schedule, edit and cancel posts; next best posting slot; top posts; reply to comments and reviews. Posts an assistant creates wait in Needs approval unless an admin turns on "Posts from AI assistants skip approval" in Settings → Connections → API. Admins, and anyone who can publish without approval, can approve any held post with approve_social_post.
  • Content and SEO: blog posts (including unpublish and delete), content collections and their items, newsletter site pages, SEO meta and opportunities, lead magnets, forms, documents.
  • Images and video: generate and edit images; generate, trim and transcribe video.
  • CRM: search, create, update and delete contacts and deals; set up pipelines and stages; segments; proposals; draft emails to contacts.
  • Email campaigns: create campaign drafts and schedule sends.
  • Outreach: find LinkedIn prospects, build prospect lists, plan, edit and start cold email and LinkedIn sequences.
  • Inbox: summarise, read threads, and draft replies; close, assign and tag conversations; saved replies.
  • Bookings: find free slots, book, reschedule and cancel meetings, one-time booking links; create, edit and delete meeting types; weekly hours and days off.
  • Insight: workspace analytics, marketing plan, brand kit, Autopilot activity.
  • Approvals and Autopilot: read and change per-channel trust (draft, approve or auto), whether assistant posts skip approval, social and inbox autopilot, and any agent's instructions, schedule and trust. Full auto still unlocks only after the approval warm-up.
  • Automations: build, publish and test automations, including if/else branches on a contact field, and see who has been through them.
  • Payments: invoices and quotes (edit drafts, void, duplicate, convert, credit notes), products and recurring invoices.
  • Team, files and reports: list, change the role of and remove team members; organise, share and delete library files; scheduled report emails.

Try asking

  • "Plan next week's Instagram and LinkedIn posts from our marketing plan and schedule them."
  • "Which posts did best last month, and why?"
  • "Find 50 marketing agency owners in the UK on LinkedIn and set up an outreach sequence. Don't start it yet."
  • "Summarise my inbox and draft replies to anything waiting on me."
  • "Find a 30-minute slot next week and book a call with jane@example.com."

Data and disconnecting

Results from your workspace go to the assistant you connected, and are handled under that provider's terms. We store tokens hashed, never in plain text. To disconnect, revoke the assistant under Connected assistants, or delete its key under API keys, in Settings → API. See our Privacy Policy for details. Questions: contact us.

Website tracking (embed)

Paste this in your site <head>, or add it as a Custom HTML tag in Google Tag Manager (All Pages trigger). Get your real key from Settings → Tracking after sign-in.

<script async src="https://your-domain.com/tracking.js?id=YOUR_TRACKING_KEY"></script>

In Settings → Tracking, add every site origin you use (e.g. https://www.example.com). Without that, cross-site requests are blocked.

The script automatically captures pageviews and submits on HTML forms on your site.

Optional JavaScript API

// After the script loads:
dinabite.grantConsent(); // if you require consent in Tracking settings
dinabite.identify({ email: "guest@example.com", firstName: "Jane" });
dinabite.track("cta_clicked", { label: "Start trial" });

// Ids for events your server sends about this visitor (null without analytics consent):
const ids = dinabite.ids(); // { visitorKey, sessionKey }

// Skip a form: <form data-dinabite-ignore>...</form>

Live chat

Enable live chat in Settings → Tracking. The tracking snippet loads the chat widget automatically. Visitor threads appear in Messages with AI replies when messaging autopilot is on.

Website tracking (server)

Send events from your backend with the same workspace API key used for CRM endpoints.

{
  "events": [
    {
      "type": "form_submit",
      "properties": {
        "email": "guest@example.com",
        "name": "Jane Doe"
      },
      "external": {
        "pageUrl": "https://example.com/contact",
        "formName": "Contact",
        "fields": [
          "email",
          "name"
        ]
      }
    }
  ]
}
curl -X POST "https://your-domain.com/api/v1/tracking/events" \
  -H "Authorization: Bearer din_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d @payload.json

Event types: pageview, form_submit, booking_scheduled, identify, company, custom. Submissions with an email create or update contacts automatically. identify can carry a company: { domain, name, traits }, found or created by domain with the contact added to it; a company event saves a company without a contact.

Custom events can carry the browser's visitorKey and sessionKey (from dinabite.ids()), or an email to file them under an existing contact, plus occurredAt (up to 7 days ago). identify traits named like your contact custom fields are saved to them. The response lists the contacts touched: { accepted, contacts: [{ email, contactId }] }. Keys need analytics:manage (and crm:write for contact events) from 1 February 2027.

For headless blog posts and resources, preferred custom event names are content_view, content_unlock, and content_download. Create matching event name goals under Analytics → Goals (match value exactly, e.g. content_download). Unlock via the Content API also records these server-side when tracking is enabled.

Content API (blog + resources)

Publish posts and downloadable resources in the Content app, then fetch them from your own site (Astro, Next.js, etc.) with a workspace API key that includes content:read (and content:write for gated unlocks). Dinabite does not host a public blog theme — JSON only.

List published entries

curl -H "Authorization: Bearer din_YOUR_KEY" \
  "https://your-domain.com/api/v1/content?type=POST&locale=en&limit=20"

Get one entry

curl -H "Authorization: Bearer din_YOUR_KEY" \
  "https://your-domain.com/api/v1/content/my-post-slug?locale=en"

Resources include gated, optional formSlug, and downloadPath when ungated. Gated downloads:

  1. Visitor submits the gate form (hosted or headless). Public submit responses include submissionId; V1 POST /forms/:id/submissions returns the full row with id.
  2. Call unlock with that id (requires content:write):
curl -X POST "https://your-domain.com/api/v1/content/toolkit-slug/unlock" \
  -H "Authorization: Bearer din_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{"formSubmissionId":"clx...","locale":"en"}'

Response: short-lived downloadUrl. Query track=0 on GET to skip automatic content_view.

Collections (custom types)

Workspace-defined collections (team, FAQs, toolkits, etc.) sit alongside posts and resources. Field keys in schema map to data on each item. Prefer stable snake/camel keys like title, body, file, form.

curl -H "Authorization: Bearer din_YOUR_KEY" \
  "https://your-domain.com/api/v1/collections"

curl -H "Authorization: Bearer din_YOUR_KEY" \
  "https://your-domain.com/api/v1/collections/team/items?locale=en"

curl -H "Authorization: Bearer din_YOUR_KEY" \
  "https://your-domain.com/api/v1/collections/team/items/jane-doe?locale=en"

REST API

Base URL: https://your-domain.com/api/v1

Create a key in Settings → API (requires a Dinabite account). Send it on every request:

curl -H "Authorization: Bearer din_YOUR_KEY" \
  "https://your-domain.com/api/v1/contacts?limit=10"

Common endpoints

  • GET /contacts · POST /contacts
  • GET /companies · POST /companies
  • GET /deals · POST /deals · GET /deals/pipelines
  • GET /forms · GET/POST /forms/:id/submissions
  • GET /content · GET /content/:slug · POST /content/:slug/unlock
  • GET /collections · GET /collections/:slug/items · GET /collections/:slug/items/:itemSlug
  • GET /analytics/overview?days=7
  • POST /tracking/events
curl -X POST "https://your-domain.com/api/v1/contacts" \
  -H "Authorization: Bearer din_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{"email":"guest@example.com","firstName":"Jane","lastName":"Doe"}'

Rate limit: ~120 requests/minute per workspace. Errors return JSON { "error": "..." }. Scoped keys can limit access — create them in Settings → Connections → API.

Outbound webhooks

Receive real-time JSON when contacts, deals, form submissions, inbox messages, and other workspace events occur. Configure endpoints in Settings → API (Webhooks section). Each delivery is signed with HMAC-SHA256:

X-Dinabite-Signature: sha256=<hex>
X-Dinabite-Event: contact.created
X-Dinabite-Delivery-Id: <uuid>

Verify by computing HMAC-SHA256 of the raw body with your webhook signing secret. Use this with Zapier, Make, or n8n to trigger automations when Dinabite data changes.

Wake an agent

Agents can start on the same events as webhooks: a new contact, a form submission, a booking, or a custom event from your app such as signed_up. There is nothing extra to call. Send the data you already send, then pick the trigger when you set the agent up in Agents → New agent or in chat.

For example, a founder email to every new signup: send an identify and a custom event when someone signs up, and give the agent the trigger “When your app sends signed_up”.

curl -X POST "https://your-domain.com/api/v1/tracking/events" \
  -H "Authorization: Bearer din_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{"events":[
    {"type":"identify","email":"jane@acme.com","traits":{"firstName":"Jane"}},
    {"type":"custom","name":"signed_up","email":"jane@acme.com","properties":{"plan":"Pro"}}
  ]}'

Runs are queued, so your request returns straight away. Each agent handles up to 40 events a day, and anything it drafts for someone else waits for approval unless you let that channel act on its own.

OpenAPI

Machine-readable spec for all /api/v1 routes (CRM, social, inbox, email, scheduling, files, workspace):

https://your-domain.com/api/v1/openapi.json

Import into Postman, Swagger UI, or your AI coding tool. Requires a valid API key for live requests; the spec itself is public.

Hosted forms

Publish a form in Dinabite, then link or iframe the hosted page. Submissions appear under Forms with a Dinabite badge.

https://your-domain.com/forms/your-workspace-slug/your-form-slug

Replace your-workspace-slug and your-form-slug with the values from the form builder (copy link / embed). On a verified custom domain you can also use /forms/your-form-slug.

Custom form UI (headless)

Build your own UI and talk to the public form API. Requests must come from the same workspace host (or proxy through your server).

// 1. Load field definitions
const schema = await fetch("https://your-domain.com/api/forms/contact").then((r) => r.json());

// 2. Submit (same origin or your server proxy)
await fetch("https://your-domain.com/api/forms/contact/submit", {
  method: "POST",
  headers: { "Content-Type": "application/json" },
  body: JSON.stringify({
    email: "guest@example.com",
    name: "Jane Doe",
    pageVisitorKey: localStorage.getItem("dinabite_trk_vid"), // optional, links to visitor
  }),
});

For server-side submission with an API key, use POST /api/v1/forms/:id/submissions — the form must have internal submissions enabled.

Booking pages

Link to your public scheduling page (copy the exact URL from Scheduling in the app):

https://your-domain.com/book/your-workspace/your-host-slug

Replace your-workspace and your-host-slug with values from Scheduling → copy link. Bookings create contacts when tracking is enabled. Pass pageVisitorKey in the book request body to link the booking to a tracked visitor.

Before you ship

  • ✓Tracking enabled; after install, review sites under Tracking and block any you do not want
  • ✓API key stored in your server secrets — never in client-side code
  • ✓Form slug / booking URL tested on the same domain users will visit
  • ✓Submit a test with a real email — confirm the contact appears in Contacts
  • ✓External site forms show under Forms with an External badge after the embed captures a submit
Developer docs | Dinabite