ZEONEXT DEVELOPER API

Put governed profit intelligence inside the systems your team already uses.

Read portfolio intelligence, submit analysis, ask the Profit Agent, and subscribe to signed webhooks through tenant-scoped API keys with usage controls.

API v1

Stable endpoints. Explicit scopes. Signed events.

Developer API access is an add-on to an active Zeonext product. Keys are shown once, stored hashed, individually revocable, and constrained to explicit machine capabilities.

AUTH

Tenant-scoped API keys

Authorization: Bearer zx_live_••••••

Available scopes include analysis:submit, analysis:read, portfolio:read, agent:ask, and governed integration access where enabled.

USAGE

Governed capacity

Default launch entitlement: 100,000 API requests per rolling 30-day usage window. Usage and remaining capacity are visible to workspace admins.

WEBHOOKS

Signed deliveries

HTTPS-only endpoints receive event, timestamp, delivery ID, and an HMAC signature for verification and replay-safe processing.

QUICKSTART

Request → response

Read the portfolio

curl https://zeonext.com/api/v1/portfolio \
  -H "Authorization: Bearer $ZEONEXT_API_KEY"

200 response

{
  "opportunities": [...],
  "accounts": [...],
  "summary": {
    "open": 14,
    "realized": 6
  }
}

Submit an analysis

POST /api/v1/analysis
Content-Type: application/json
Authorization: Bearer zx_live_••••••

{
  "product": "complete",
  "accountName": "Example Account",
  "documents": [...]
}

202 response

{
  "job": {
    "id": "…",
    "status": "queued"
  }
}

Webhook payload

{
  "event": "opportunity.updated",
  "at": "2026-10-02T20:10:00Z",
  "deliveryId": "…",
  "payload": {
    "opportunityId": "…",
    "stage": "approved"
  }
}

JavaScript

const res = await fetch(
  "https://zeonext.com/api/v1/portfolio",
  { headers: {
    Authorization: `Bearer ${process.env.ZEONEXT_API_KEY}`
  }}
);
const data = await res.json();

Python

requests.get(
  "https://zeonext.com/api/v1/portfolio",
  headers={"Authorization": f"Bearer {key}"}
)
CUSTOMER DEVELOPER CENTER

Manage API access from the same governed account.

Signed-in customers can see entitlement state, request usage, revocable API keys, and webhook endpoints here.

Key policy

Separate test and live environments, expiration, IP controls and rotation.

Delivery history

Signed delivery attempts, HTTP outcomes, retries and endpoint health.
No webhook deliveries yet.

API request inspector

Request IDs, endpoint, status and latency. Request bodies are never stored here.
No API requests yet.
ERRORS & VERSIONING

Predictable failure modes.

401 AUTH_REQUIRED — missing or invalid credential. 403 CAPABILITY_REQUIRED — key lacks the required scope. 402 entitlement required — Developer API add-on is not active. 429 — rate limit exceeded. 5xx — retry with backoff using idempotency keys on supported writes.

Current version: v1. Backward-incompatible changes will ship under a new major API version. Changelog entries document additive fields, new events, deprecations, and sunset dates.