Loading

Authentication

All API requests are authenticated with an API key. Keys are tenant-scoped — one key can only access the sessions and data belonging to your workspace.

Key format

mk_live_[A-Za-z0-9]{32}

Keys start with mk_live_ followed by 32 alphanumeric characters (total 40 characters). Keys are validated at the gateway before any request reaches the backend.

Passing the key

Pass the key via the Authorization header (preferred) or the X-API-Key header. Never pass keys in query strings — they appear in server logs.

# Option 1: Authorization header (recommended)
curl https://api.relayno.com/v1/messages \
  -H "Authorization: Bearer mk_live_YOUR_API_KEY"

# Option 2: X-API-Key header
curl https://api.relayno.com/v1/messages \
  -H "X-API-Key: mk_live_YOUR_API_KEY"

Keep your key secret

Treat API keys like passwords. Store them in environment variables, never commit them to source control. If a key is exposed, rotate it immediately in the Relayno console — old keys are revoked instantly with no downtime.

Rate limits

Per IP (global)

200 requests / 15 min

Applies to all endpoints combined.

Per IP (message send)

100 requests / 15 min

Applies to POST /v1/messages/send.

Per API key

500 requests / 15 min

Across all endpoints for this key.

Webhook ingest

1 000 requests / 15 min

Per IP — webhooks have a higher limit.

Rate-limited responses include a Retry-After header (seconds). Implement exponential back-off in your client.

Error responses

# Missing key → 401
HTTP/1.1 401 Unauthorized
{"error":"missing_api_key","message":"Provide a Bearer token or X-API-Key header."}

# Invalid format → 401
HTTP/1.1 401 Unauthorized
{"error":"invalid_api_key","message":"Key format invalid. Expected mk_live_[A-Za-z0-9]{32}."}

# Revoked or unknown → 401
HTTP/1.1 401 Unauthorized
{"error":"invalid_api_key","message":"Key not recognized. Check your dashboard."}

# Rate limited → 429
HTTP/1.1 429 Too Many Requests
Retry-After: 60
{"error":"rate_limited","message":"Too many requests. Retry after 60 seconds."}

Statuserror codeDescription

401missing_api_key

No Authorization or X-API-Key header supplied.

401invalid_api_key

Key format wrong, revoked, or not recognized.

429rate_limited

Request rate exceeded. Respect Retry-After header.

413payload_too_large

Request body exceeds 512 KB limit.

405method_not_allowed

Only GET, POST, OPTIONS, HEAD allowed.

Key rotation

Create a new key in the console, update your environment variables, then revoke the old key. Both keys are valid during the switchover window. Revocation is instant — there is no propagation delay.

Relayno — the all-in-one business platform · Stock · HMS · WhatsApp · Invoices · Emails

Relayno

Pricing

Operations

Stock

Track inventory, warehouses and stock movements in real time.

Invoices

Quotes, invoices, payments and tax — all handled.

Communication

Shared team inbox, campaigns and the official WhatsApp API.

Emails

Send, automate and track transactional and marketing email.

Hospitality

HMS

Hotel management: reservations, front desk, housekeeping, channel manager and billing.

WordPress Plugins

WhatsApp for WordPress

Add a WhatsApp chat button, shared inbox and the official API to any WordPress site.

WooCommerce ↔ Relayno Stock

Soon

Sync WooCommerce products, orders and inventory with the Relayno stock app in real time.

Reservations for WordPress

Soon

Let visitors book appointments and tables right from your WordPress pages.

Social

Facebook Auto-Posting

Soon

Schedule and auto-publish your products and updates to Facebook.

Instagram Auto-Posting

Soon

Schedule and auto-publish your products and updates to Instagram.

ERP

Odoo Stock Management

Soon

Two-way sync of inventory and stock movements with your Odoo instance.

REST APIs

WhatsApp API

Send messages, receive webhooks, manage sessions.

Stock API

Soon

Inventory and stock management REST API.

HMS API

Soon

Hotel management REST API.

How to use

How to use our apps

Step-by-step guides for every Relayno product.

Company

About

Relayno started as a WhatsApp gateway for one shop. It grew into the platform that shop wished existed.

Careers

Small team, real users, short feedback loop. If you want your work in production this month, this is that kind of place.

Contact

Pick the route that matches what you need — they go to different people.

Authentication

All API requests are authenticated with an API key. Keys are tenant-scoped — one key can only access the sessions and data belonging to your workspace.

Key format

mk_live_[A-Za-z0-9]{32}

Keys start with mk_live_ followed by 32 alphanumeric characters (total 40 characters). Keys are validated at the gateway before any request reaches the backend.

Passing the key

Pass the key via the Authorization header (preferred) or the X-API-Key header. Never pass keys in query strings — they appear in server logs.

# Option 1: Authorization header (recommended)
curl https://api.relayno.com/v1/messages \
  -H "Authorization: Bearer mk_live_YOUR_API_KEY"

# Option 2: X-API-Key header
curl https://api.relayno.com/v1/messages \
  -H "X-API-Key: mk_live_YOUR_API_KEY"

Keep your key secret

Rate limits

Per IP (global)

200 requests / 15 min

Applies to all endpoints combined.

Per IP (message send)

100 requests / 15 min

Applies to POST /v1/messages/send.

Per API key

500 requests / 15 min

Across all endpoints for this key.

Webhook ingest

1 000 requests / 15 min

Per IP — webhooks have a higher limit.

Rate-limited responses include a Retry-After header (seconds). Implement exponential back-off in your client.

Error responses

# Missing key → 401
HTTP/1.1 401 Unauthorized
{"error":"missing_api_key","message":"Provide a Bearer token or X-API-Key header."}

# Invalid format → 401
HTTP/1.1 401 Unauthorized
{"error":"invalid_api_key","message":"Key format invalid. Expected mk_live_[A-Za-z0-9]{32}."}

# Revoked or unknown → 401
HTTP/1.1 401 Unauthorized
{"error":"invalid_api_key","message":"Key not recognized. Check your dashboard."}

# Rate limited → 429
HTTP/1.1 429 Too Many Requests
Retry-After: 60
{"error":"rate_limited","message":"Too many requests. Retry after 60 seconds."}

Statuserror codeDescription

401missing_api_key

No Authorization or X-API-Key header supplied.

401invalid_api_key

Key format wrong, revoked, or not recognized.

429rate_limited

Request rate exceeded. Respect Retry-After header.

413payload_too_large

Request body exceeds 512 KB limit.

405method_not_allowed

Only GET, POST, OPTIONS, HEAD allowed.

Key rotation

Create a new key in the console, update your environment variables, then revoke the old key. Both keys are valid during the switchover window. Revocation is instant — there is no propagation delay.

Relayno

The all-in-one business platform. Run every team and module from a single login.

Modules

Stock HMS WhatsApp Invoices Emails

Company

About Careers Contact Privacy Terms

Resources

Docs Blog Status Support