The product

One CRM. Every next step.

Contacts, pipeline and delivery in one workspace, with AI that prepares the work for your approval.

See how Meibo works

DEVELOPERS / API V1

Your workspace,
connected.

Bring enquiries into Meibo. Build tools around your records. Keep other systems up to date as your team works.

Authentication

Create a key in Settings → API keys. Send it as a Bearer token to https://app.meibolabs.com/api/v1. Keep keys on your server; never embed them in a public website or mobile bundle.

A key can access only its own workspace. Keys expire after 90 days and are revocable. Its creator must remain an owner or admin. Each key allows up to 120 requests per minute.

PermissionAccess
records:readList CRM records
records:writeCreate, update and delete records
enquiries:writeCreate website enquiries and follow-ups

Website enquiries

POST /enquiries creates a contact, an Enquiry-stage deal linked to that contact, and a task due tomorrow linked to the deal. All three records are saved together or none are saved.

POST /ENQUIRIES · EXAMPLEONE REQUEST · THREE RECORDS
Illustrative request with fictional data. Meibo creates the contact, an Enquiry-stage deal and a follow-up task in one transaction, then returns their IDs.

Send a unique Idempotency-Key for each real submission. Reuse that key when retrying the same submission; Meibo returns the original IDs. Reusing it with different data returns 409.

curl https://app.meibolabs.com/api/v1/enquiries \
  -H "Authorization: Bearer $MEIBO_API_KEY" \
  -H 'Content-Type: application/json' \
  -H 'Idempotency-Key: website-enquiry-0001' \
  -d '{
    "name": "Alex Morgan",
    "email": "alex@example.com",
    "subject": "A new partnership",
    "message": "We would love to discuss a campaign."
  }'
// 201 Created
{"data":{"contact_id":"…","deal_id":"…","task_id":"…"}}

Required fields: name (200 characters), email (254), subject (200), message (10,000). Optional owner is a Team record ID from this workspace. Without it, the deal and task belong to “Agency team”.

Connect BNOC’s website

  1. Create a key with only enquiries:write.
  2. Save it as MEIBO_API_KEY in the website’s server environment.
  3. Validate the form and apply spam protection on your website’s server.
  4. Forward the submission to this endpoint and show success only after a successful response.

Use a submission UUID for the idempotency header. Do not generate a new UUID for a retry. The repository includes a Next.js server route with Turnstile verification in examples/website-enquiry-route.ts.

Records

List records

GET /api/v1/records?kind=people&limit=50
Authorization: Bearer <key>

{"data":[{"id":"…","kind":"people","name":"Alex","status":"Active","version":1}],"next_cursor":null}

The limit is 1–100. The optional kind filters the object type. If next_cursor is present, pass it as the next request’s cursor. Results are ordered by ID; changing records during pagination is not a snapshot.

Create or update a record

POST /api/v1/records
Content-Type: application/json

{"kind":"companies","name":"Example Studio","status":"Prospect"}

// Update: send the complete record, including its current version.
{"id":"existing-id","kind":"companies","name":"Example Studio","status":"Active partner","version":1}

Creates return 201. Updates return 200 and increment the version. An outdated version returns 409. Linked fields — company, talent, owner, related, collaborators — must reference records in the same workspace. Owner and collaborators must reference Team records; “Agency team” is an unassigned owner.

Deal pipelines

Owners and admins configure pipelines in Settings → Pipelines. Use GET /api/v1/pipelines with records:read to retrieve pipelines and their ordered stages. Every stage has a stable ID, display name, canonical status and probability.

For a deal, send pipeline_id and stage_id alongside the usual required fields. When moving between pipelines, always send the destination stage ID. Read the returned record: an explicit new stage determines its canonical status. Names can change without changing IDs.

Legacy integrations can continue sending canonical statuses. New deals without pipeline IDs enter the default pipeline; updates without those IDs preserve their pipeline and map a changed status to its first matching stage. A pipeline with no matching stage rejects that change. Other record types cannot carry pipeline or stage IDs.

Probabilities are manually configured estimates. Won stages use 100%, lost stages 0%, and open stages 0–99%. Weighted open value excludes won and lost deals. Stage definitions remain available to every workspace member; only owners and admins can change them.

Custom fields

Owners and admins create fields in Settings → Fields. Retrieve their stable IDs with GET /api/v1/fields?kind=companies, using a key with records:read. Definitions include name, type, choices and archived status.

POST /api/v1/records
Content-Type: application/json

// Replace the UUID with a text field ID from your workspace.
{"kind":"companies","name":"Example Studio","status":"Prospect","custom":{"00000000-0000-4000-8000-000000000001":"Referral"}}

Send text, numbers, YYYY-MM-DD dates, an exact single-select choice, or true/false according to the field type. Values are available in record responses. Zero and false are valid values.

On update, omitted custom keys retain their saved values. Send null to clear an active field; an empty custom object does not clear values. Archived fields retain their values but cannot be edited. Field types cannot change, and choices in use cannot be removed.

Record webhooks identify changes; fetch the record to read its latest custom values. Public client shares do not automatically expose custom fields.

Delete a record

DELETE /api/v1/records
Content-Type: application/json

{"id":"record-id","version":2}

Returns 204. Remove incoming links before deleting a record. Request bodies are limited to 30 KB and saved record data to 25 KB.

Object types and statuses

KindAllowed statuses
teamAvailable · Busy · Away
talentRepresented · In discussion · Paused
companiesActive partner · Prospect · Past partner
peopleActive · New contact · Archived
dealsEnquiry · Pitching · Negotiation · Won · Lost
campaignsBriefing · In production · In review · Delivered · Paid
tasksTo do · In progress · Done
notesNote
emailsDraft

Signed webhooks

Add a public HTTPS endpoint in Settings → Webhooks. Save the signing secret when it appears. Meibo emits record.created, record.updated, and record.deleted events after the database transaction commits.

{
  "id": "event-uuid",
  "type": "record.updated",
  "workspace_id": "workspace-uuid",
  "created_at": "2026-10-04T12:00:00.000Z",
  "data": { "id": "record-id", "kind": "deals", "version": 2 }
}

The payload identifies the change; use a read API key to retrieve current record data. Deleted records are no longer available. Delivery is at least once and order is not guaranteed. Deduplicate on the event ID.

Verify X-Meibo-Signature using HMAC SHA-256 over timestamp + "." + rawBody. Reject timestamps more than five minutes from your server clock.

import { createHmac, timingSafeEqual } from 'node:crypto';

// rawBody must be the unmodified request text.
const header = request.headers.get('x-meibo-signature') ?? '';
const match = /^t=(\d+),v1=([a-f0-9]{64})$/.exec(header);
if (!match || Math.abs(Date.now() / 1000 - Number(match[1])) > 300) {
  return new Response('Invalid signature', { status: 401 });
}
const expected = createHmac('sha256', process.env.MEIBO_WEBHOOK_SECRET)
  .update(match[1] + '.' + rawBody).digest();
const supplied = Buffer.from(match[2], 'hex');
if (!timingSafeEqual(expected, supplied)) {
  return new Response('Invalid signature', { status: 401 });
}
const event = JSON.parse(rawBody);
// Persist event.id in your database with a UNIQUE constraint.
// Process each event once, even when Meibo retries delivery.
// Return 2xx only after durable acceptance.

Return a 2xx response within five seconds. Redirects are not followed. Destinations must resolve to public IPv4 addresses on HTTPS port 443. Record saves trigger delivery after the response. A scheduled worker also processes due events every five minutes, up to ten per run, with exponential backoff and a maximum of eight attempts. Check failures in Settings → Webhooks; “Send due deliveries” processes events that are ready to retry.

The default schedule is intended for the first clients. Increase worker throughput before using Meibo for a high-volume event stream.

Errors and retries

StatusWhat to do
400Check the request body and field values.
401Check the API key, expiry and revocation status.
403Check scopes and the key creator’s current permissions.
409Refresh the record version, remove blocked links, or check idempotency data.
413Reduce the request size.
415Send Content-Type: application/json.
429Wait for the Retry-After header before retrying.
503Retry later; the service or database is unavailable.
{"error":{"message":"This API key does not have the required permission.","status":403}}

Connect an AI assistant with MCP

Let an external assistant search your CRM and prepare changes for review. You approve the proposal in Meibo before records change. The assistant cannot approve its own work.

Connect with OAuth

In a client that supports remote MCP with OAuth, add https://app.meibolabs.com/api/mcp as the server URL. Meibo publishes authentication discovery. Sign in, check the app’s callback address and selected workspace, then approve read access and, optionally, reviewed proposals. Your Meibo password is never shared with the client.

Access tokens last 15 minutes. Refresh tokens rotate; connections can be revoked in Settings → API keys. The grant expires after 90 days. Client product availability and connection screens vary; complete a real-client read and reviewed-proposal check before using a connection for agency work.

API-key and desktop alternatives

  1. Open Settings & branding → API keys. Create a dedicated key with mcp:read. Add mcp:prepare if you want reviewed proposals.
  2. For clients supporting Bearer headers, use https://app.meibolabs.com/api/mcp with Authorization: Bearer YOUR_KEY.
  3. For desktop clients supporting local MCP servers, download meibo-mcp.mjs, install Node.js 22 or later, and configure the command below with the absolute path to the downloaded file. Store the key in your client’s secret configuration.
{
  "mcpServers": {
    "meibo": {
      "command": "node",
      "args": [
        "/absolute/path/meibo-mcp.mjs"
      ],
      "env": {
        "MEIBO_API_KEY": "YOUR_DEDICATED_MCP_KEY"
      }
    }
  }
}

Ask: “Find the company I mention, read its current record, and prepare a follow-up task for my review.” Open the returned review link, select the matching workspace, and approve or dismiss the proposal in Ask Meibo.

Available tools: start research, search records or talent, read records, inspect CRM fields, prepare record creation or updates, and check review status. Research expires after one hour. Repeated preparation with the same request ID returns the same review. A changed source record blocks approval until the plan is refreshed.

The server supports OAuth authorization-code grants with S256 PKCE, public-client registration, resource-bound tokens and Streamable HTTP (MCP 2025-11-25, with 2025-06-18 and 2025-03-26 compatibility). Automated protocol tests do not replace acceptance testing in your actual ChatGPT or Claude client. Mailboxes, record merges, sending messages, invoices and payments are outside this connector.

Only workspace owners and admins can create these keys. They expire after 90 days and can be revoked here at any time. Revocation stops future connector access; dismiss any already-prepared proposals separately.

Back to Meibo