Developer quickstart

Get your first successful API response in minutes.

Everything you need is here: access, auth, quickstart request, and API conventions.

What to call: GET /api/v1/workflows.json
How to auth: Bearer token in Authorization header
Where quickstart is: below in the next section
Where to get access: portal token setup in auth section

Start Quickstart

Copy and run

curl -s https://robo-meister.com/api/v1/workflows.json \
  -H "Authorization: Bearer $TOKEN"

If you need a token first, jump to Authentication.

Quickstart

Create token → call endpoint → post first event.

Step 1

Get API access

Open the portal, create or select your org, then generate a Personal Access Token.

Authorization: Bearer <TOKEN>

Token setup details

Step 2

Make first authenticated call

curl -s https://robo-meister.com/api/v1/workflows.json \
  -H "Authorization: Bearer $TOKEN"

This confirms auth and endpoint reachability.

Step 3

Send first event

curl -X POST https://robo-meister.com/api/v1/events.json \
  -H "Authorization: Bearer $TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"event_type":"task_completed"}'

Authentication

Use Bearer tokens for scripts and OAuth 2.0 for user-consent app flows.

Personal Access Token

Generated in the portal for an organization
Scope by module permissions
Rotate/revoke at any time

Authorization: Bearer <TOKEN>

OAuth 2.0

Authorization Code and Client Credentials
Tenant-aware consent screens
Refresh tokens for long-lived sessions

POST /oauth/token
client_id=...&client_secret=...
grant_type=client_credentials

REST API Basics

Base URL, common endpoints, pagination, and error format.

Base URL

https://robo-meister.com/api/v1

Examples

GET /workflows.json
GET /workflows.csv
POST /events.json

Querying + errors

GET /clients.json?status=active&page=2&limit=50
GET /products.json?category=hardware&sort=-createdAt

{
  "status": "error",
  "error": {"code": "invalid_scope", "message": "Token lacks finance:read"}
}

Webhooks & Events

POST /webhooks.json
{
  "url": "https://example.com/webhooks/robo",
  "events": ["invoice.created", "shipment.updated"],
  "secret": "<HMAC_SECRET>"
}

Signature + topics

X-Robo-Signature: t=1733826000,v1=hex(HMAC_SHA256(body, secret))

events_channel:user:<id>:task_completed
events_channel:organization:<id>:inventory_update

Package Distribution

Ship apps, workflows, drivers, and integrations as .rappkg archives.

Structure

my-first-app.rappkg
├── meta.json
├── app.json
├── workflows/
├── drivers/
└── integrations/

POST /packages/install.json
{ "package_url": "https://.../my-first-app.rappkg" }

Minimal meta.json

{
  "name": "my-first-app",
  "version": "1.0.0",
  "type": "app",
  "entry": "app.json"
}

Context Engine

Use hierarchical context keys and queue patterns once your first integration is running.

Key patterns

Context:User:<user_id>:Project:<project_id>:client
Data:Queue:<queue_id>:In:<type>:payload
Data:Queue:<queue_id>:Result:status

Processing flow

PUSH Data:Queue:plan-42:In:orders
SUB  Data:Queue:plan-42:Result:status

Advanced architecture and module docs

Reference these after onboarding: specialized module guides, integration hub, assistant docs, JSON samples, and deeper Context Engine material.

Context Engine Deep Dive