Documentation

Integrate with BEZ in an afternoon

Everything an external team needs to build on the platform: one credential, one set of conventions, and a reference for every endpoint we run in production.

Quickstart

Your first authenticated call

Create a key in the developer portal, export it, and call the gateway. The same key works across intelligence, CRM, marketing and finance endpoints.

# 1. Create a key in the developer portal, then:
export BEZ_API_KEY="bez_live_…"

# 2. Call the intelligence gateway
curl https://zentechlimited.com/api/public/ai/chat \
  -H "Authorization: Bearer $BEZ_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "messages": [{ "role": "user", "content": "Hello BEZ" }] }'

One credential

A single bearer API key authenticates every product surface. Scopes decide what it can reach.

One convention

REST over HTTPS, JSON in and out, /v1 versioning, and a { data, error } envelope on every response.

Tenant isolation

Keys are bound to an organisation. Row-level security applies to every read and write.

Predictable limits

Per-minute rate limits and monthly quotas are visible on the key and returned in error bodies.

Need a sandbox tenant?

We provision seeded sandbox organisations for integration and certification testing, with support engineers who answer technical questions technically.