Get started with OG Manager

1. 1

   Create your account

   Sign up with email and a password of at least 10 characters, or with Google. Choose your country and billing currency (BDT or USD). Verify your email before you add billing or invite people.
2. 2

   Describe your company and your role

   Industry, timezone and goals seed your Business Brain and decide which dashboards are built for you.
3. 3

   Connect your first data source

   Meta Ads, Google Ads, GA4, Shopify, WhatsApp or a CSV. The first sync and backfill run in the background.
4. 4

   Get your first dashboard and AI insight

   After the first sync, OG Manager detects your business type and builds an executive dashboard with a first AI insight.
5. 5

   Invite your team and set up branches

   Invite members with a role and a branch scope: all branches, a region, listed branches or own records only.

1. 1

   Authorize

   You are sent to the provider. The OAuth state is single-use, expires in 10 minutes and is bound to you and your organization.
2. 2

   Select accounts

   OG Manager discovers Business Managers, ad accounts, pages, Instagram accounts and pixels. Select the ones to connect; each counts as a connected account.
3. 3

   Watch the first sync

   Progress shows on the connection card. Later syncs run on your plan's schedule, and Refresh now is available within plan limits.

Agencies can send an authorization link from Settings → Client Access so a client authorizes Meta, Google Ads or Instagram without sharing a password. Files can be imported as CSV or Excel with a validation error report.

1. 1

   Set a goal

   Type what you want to accomplish in English, Bangla or Banglish. Credits are reserved before the job starts.
2. 2

   Review the plan

   “Here is what I am going to do” lists each step with its agent, tool and risk level.
3. 3

   Approve write steps

   Medium and high-risk steps create an approval card with evidence, before and after values and an expiry.
4. 4

   Check the outcome

   After execution the gateway verifies the change on the platform and logs it. Unused credits are released.

Policies live under Settings → AI policies. Examples: maximum automatic budget change 10%, AI may spend up to ৳50,000 without approval. Each AI employee and workflow has an execution mode: recommend only, require approval, or auto-execute within policy. Critical actions are blocked by default.

curl https://api.ogmanager.com/api/v1/crm/leads?limit=25 \
  -H "Authorization: Bearer eos_live_<id>_<secret>" \
  -H "Accept: application/json"

Create keys under Platform → API & MCP. A key looks like eos_live_<id>_<secret> (or eos_test_… for the sandbox organization), is shown once, and only its SHA-256 hash is stored. Every key is scoped, for example data:read or crm:write. Full API reference.

POST /hooks/este HTTP/1.1
Content-Type: application/json
Este-Signature: t=1761112800,v1=5257a869e7ec…

{
  "id": "evt_01JB8Z3K6Q2W9Y4T0M5R7N1P8C",
  "type": "lead.created",
  "version": "2026-10-01",
  "created_at": "2026-10-22T08:00:00+06:00",
  "data": {
    "id": "0192f0c4-…",
    "display_id": "LEAD-000412",
    "name": "Nusrat Jahan",
    "source": "whatsapp",
    "branch_id": "0192e…"
  }
}

Each delivery is signed with Este-Signature: t=<ts>,v1=<hmac-sha256>. The signature is an HMAC-SHA256 of <ts>.<raw body> using your endpoint secret. Reject deliveries older than five minutes, and de-duplicate by event ID.

import crypto from "node:crypto";

// header: "t=1761112800,v1=5257a869e7ecebeda32affa62cdca3fa51cad7e77a0e56ff536d0ce8e108d8bd"
export function verifyEste(rawBody, header, secret, toleranceSec = 300) {
  const parts = Object.fromEntries(header.split(",").map((p) => p.split("=")));
  const t = Number(parts.t);
  if (!t || Math.abs(Date.now() / 1000 - t) > toleranceSec) return false;
  const expected = crypto
    .createHmac("sha256", secret)
    .update(`${t}.${rawBody}`)
    .digest("hex");
  return crypto.timingSafeEqual(Buffer.from(expected), Buffer.from(parts.v1 ?? ""));
}

• Respond with any 2xx within a few seconds; do the work on your own queue.
• Failed deliveries retry with exponential backoff for 24 hours.
• An endpoint is disabled after 50 consecutive failures. Replay any delivery from the delivery log.
• Endpoints on private IP ranges are refused.

{
  "mcpServers": {
    "este": {
      "url": "https://mcp.ogmanager.com",
      "headers": { "Authorization": "Bearer eos_live_<id>_<secret>" }
    }
  }
}

Authenticate with OAuth 2.1 or an API key. Nothing an outside AI client does bypasses billing, permissions, consent or audit.