Skip to main content
Norbelys is built API-first and AI-first. That’s not a developer footnote — it shapes how the whole product works. Every single thing you can do by clicking in the app is also available through one API, which means you (or your developer, or an AI agent) can automate any of it.
Four ways to run Norbelys — the dashboard, Norbe, your own code, and AI agents via MCP — all act through one API on the same workspace.

The app, Norbe, your code, and AI agents all go through one API to your workspace.

​
What “API-first” means for you

  • Nothing is hidden behind the buttons. Importing people, building a segment, creating and launching a campaign, sending a message, reading analytics, checking deliverability — all of it is one predictable API. The dashboard is just one way to reach it.
  • Consistency. Because everyone goes through the same door, your automations behave exactly like the app does — same limits, same safety rails, same results.
  • You’re never locked in. Your data is yours; you can read and export all of it programmatically.
You don’t need to touch the API to get value from Norbelys — the app does everything. The API is there for when you want to automate something repetitive or connect Norbelys to your own systems.

​
What people automate

A few common examples:
  • Sync leads in automatically from your website, CRM, or another tool as they arrive.
  • Trigger outreach from your own events — someone signs up, books a call, or hits a milestone, and a campaign enrolls them.
  • Pull results into your own dashboards — reply rates, bounces, and deliverability next to your other business metrics.
  • Keep suppression in sync with systems of record so you never email the wrong person.
  • Run one-off bulk jobs like importing and verifying a large list.

​
Getting an API key

An API key is a secret token that lets your code act on your workspace. It’s tied to a single workspace (organization) and can only touch that workspace’s data.
1

Open Settings

In the dashboard, go to Settings → API keys.
2

Create a key

Create a new key, give it a recognizable name (like “Zapier” or “Website sync”), and copy the value right away — it’s shown only once.
3

Hand it to your tool or developer

Paste it wherever you’re connecting from. The key is sent as a bearer token on each request.
Treat an API key like a password. It carries full write access to your workspace, so:
  • Never paste it into public places, chats, or source code.
  • Store it in a password manager or your tool’s secret settings.
  • If a key might be exposed, rotate it (delete it and make a new one) in Settings → API keys.

​
For developers

If you or your team want to build against Norbelys, the technical reference lives in the developer guides:

Authentication

Create a key and make your first authenticated request.

Quickstart

Add a person and send your first message in minutes.

Command line (CLI)

Drive your whole workspace from the terminal — curl … | sh, then norbelys login.

API conventions

How the API is shaped — the same five predictable patterns everywhere.

API reference

Every endpoint, field, and response.

​
Prefer to let AI do it?

You don’t have to write code to automate Norbelys. Norbe, the built-in assistant, can do most of this for you in plain language — and you can point your own AI tools at Norbelys through its connector so they can operate your workspace directly.

Norbe, your AI operator

Ask in plain language; Norbe plans, drafts, and acts (with your approval).

Connect AI agents

Give Claude, Cursor, or your own agent access to your Norbelys workspace.