Skip to content
Start trial

For developers & integration teams

Your systems.
Connected to your business.

Bring Omnizone into the tools you already use. Read business records, connect internal workflows, and build useful integrations on a versioned REST API.

Explore the API Building with AI?
A first read · GET /v1/clients
curl "https://api.omnizone.app/v1/clients?limit=5&offset=0" \
  --header "Authorization: Bearer $OMNIZONE_API_KEY"
JSON responses · Bearer authentication · Workspace-scoped access

Set OMNIZONE_API_KEY in your server environment. This read-only example lists up to five clients.

Your app or serviceOmnizone APIYour workspace records

Connect business records

Work with clients, invoices, bills, and accounts. Use the documented endpoints to link your own back office or reporting tools.

Browse available endpoints

Build your workflow

Call the API from your server or integration service. The OpenAPI specification lists supported methods, request schemas, and responses.

View the OpenAPI specification

Keep access intentional

API keys belong to a workspace and follow their assigned role and permissions. Plan limits apply; keys can expire or be revoked.

Review plans and API access

A small first step

Connect. Check. Then build.

  1. Create a key

    Open Settings → API keys in your workspace. Choose the appropriate role and keep the secret on your server.

  2. Confirm the workspace

    Call GET /v1/me to check the workspace and plan associated with your key before reading or writing business records.

  3. Start with a read

    Fetch a small list of clients. Then consult the reference for the resources and permissions your integration needs.

Check your connection · GET /v1/me
curl "https://api.omnizone.app/v1/me" \
  --header "Authorization: Bearer $OMNIZONE_API_KEY"

Missing, expired, or revoked keys return 401. Insufficient permissions or plan access can return 403. Handle rate limits with retries and backoff.

Read the API reference

MCP & AI integrations

Give your AI tools a controlled way in.

Model Context Protocol (MCP) lets AI applications work with tools you expose. You can build an MCP bridge that calls the Omnizone REST API with a workspace key.

Native hosted MCP is not currently available. This is an integration pattern for a server you build and manage.

Discuss an integration
AI applicationYour chosen MCP clientYour MCP serverExpose approved tools · Keep keys server-sideOmnizone REST APIApply workspace permissions

Example tool: “List clients” → GET /v1/clients. Start with read-only tools and require explicit confirmation for changes.