Outly AI REST API

Create a key in Settings → API keys (workspace owners and admins). A key belongs to one workspace and is either read-only or read/write. It is shown once: store it in your server's environment variables and never put it in browser code or a public repository. If it leaks, revoke it on the same page; it stops working immediately.

Send it on every request as a Bearer token:

curl https://outlyai.originutech.in/api/v1/workspace \
  -H "Authorization: Bearer $OUTLY_API_KEY"

Base URL: https://outlyai.originutech.in/api/v1

Each key can make 120 requests a minute. Every response carries X-RateLimit-Limit and X-RateLimit-Remaining; over the limit you get 429 with a Retry-After header in seconds.

The API follows your plan exactly as the app does: creating leads past the plan's lead limit, or launching a campaign past the active-campaign limit, is refused with 402 plan_limit. Bulk creates add what fits and report the rest.

curl -X POST https://outlyai.originutech.in/api/v1/leads \
  -H "Authorization: Bearer $OUTLY_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "email": "priya@example.com",
    "first_name": "Priya",
    "last_name": "Sharma",
    "title": "Head of Growth",
    "company": "Example Labs",
    "tags": ["website-signup"]
  }'

{
  "id": "2f6c1a0e-8b1d-4f7a-9c3e-5d2b1a0f9e8d",
  "email": "priya@example.com",
  "first_name": "Priya",
  "last_name": "Sharma",
  "title": "Head of Growth",
  "company": { "id": "…", "name": "Example Labs" },
  "linkedin_url": null,
  "status": "new",
  "verification_status": "unverified",
  "tags": ["website-signup"],
  "source": "api",
  "created_at": "2026-10-21T09:30:00.000Z"
}

Campaigns are written in the app, where you build the sequence and pick the sending inbox. The API lists them, feeds them leads and controls whether they send.

Node.js (18+), adding a website signup to a campaign:

const BASE = "https://outlyai.originutech.in/api/v1";
const headers = {
  Authorization: `Bearer ${process.env.OUTLY_API_KEY}`,
  "Content-Type": "application/json",
};

// Create a lead, then add it to a campaign.
const lead = await fetch(`${BASE}/leads`, {
  method: "POST",
  headers,
  body: JSON.stringify({ email: "priya@example.com", first_name: "Priya" }),
}).then((r) => r.json());

await fetch(`${BASE}/campaigns/${process.env.OUTLY_CAMPAIGN_ID}/leads`, {
  method: "POST",
  headers,
  body: JSON.stringify({ lead_ids: [lead.id] }),
});

Python, reading every lead that replied, page by page:

import os, requests

BASE = "https://outlyai.originutech.in/api/v1"
headers = {"Authorization": f"Bearer {os.environ['OUTLY_API_KEY']}"}

page = 1
while True:
    r = requests.get(f"{BASE}/leads", headers=headers, params={"status": "replied", "page": page, "page_size": 100})
    r.raise_for_status()
    body = r.json()
    for lead in body["data"]:
        print(lead["email"], lead["status"])
    if page * body["page_size"] >= body["total"]:
        break
    page += 1

Every error has the same shape, so you can branch on code:

{
  "error": {
    "code": "plan_limit",
    "message": "This workspace is on the Free plan. ..."
  }
}

• 400 invalid_request: the body or a query parameter is wrong; the message names the field.
• 401 unauthorized: missing, invalid or revoked key.
• 402 plan_limit: the plan has no room for this.
• 403 forbidden: a read-only key tried to change something.
• 404 not_found: no such lead or campaign in this workspace.
• 409 conflict / confirmation_required: see the message.
• 422 invalid_request: the campaign can't launch yet; the message says why.
• 429 rate_limited: wait for Retry-After seconds.
• 500 server_error: our fault. Retry, and tell us if it keeps happening.

Questions, or an endpoint you need that isn't here? Email support@originutech.in and tell us what you're building.