Skip to main content
Jomioz ships five complementary capabilities that you can use independently or layer together to build robust, production-grade integrations. Whether you need programmatic control, real-time data pipelines, push notifications, visual analytics, or shared team access, each feature is designed to slot into your existing workflow with minimal friction.

REST API

The Jomioz REST API gives you full programmatic control over every object in your workspace — resources, events, integrations, team members, and API keys. All endpoints accept and return JSON, follow standard HTTP semantics, and authenticate via a Bearer token in the Authorization header. The base URL for all API requests is https://api.jomioz.com/v1. Resources follow predictable URL patterns (/resources, /resources/{id}, /resources/{id}/events) so you can navigate the API surface without consulting the reference for every call.
The API enforces rate limits of 1,000 requests per minute on Standard plans and 5,000 requests per minute on Enterprise plans. Responses include X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset headers so you can manage back-off automatically.

Real-Time Events

Every state change inside Jomioz — a resource being created, updated, or deleted; an integration syncing new data — produces an immutable event record. You can subscribe to these events as a real-time stream using Server-Sent Events (SSE), giving your application a live feed of everything happening in your workspace. Connect to the event stream at https://api.jomioz.com/v1/events/stream. The connection stays open and Jomioz pushes new events as they occur, with automatic reconnection support via the Last-Event-ID header. Filter the stream by resource type or event type to reduce noise in high-volume workspaces.
Use real-time event streaming during development to observe exactly what Jomioz emits in response to your API calls — it is far faster than polling the events log.

Webhooks

Webhooks let Jomioz push event notifications directly to your infrastructure the moment something changes, so you never need to poll. Register a publicly accessible HTTPS endpoint in the dashboard or via the API, choose which event types to subscribe to, and Jomioz will deliver a signed JSON payload to your endpoint for every matching event. Each webhook delivery includes an X-Jomioz-Signature header containing an HMAC-SHA256 signature computed from your webhook secret. Always verify this signature before processing a payload to ensure the request genuinely originates from Jomioz.
Your endpoint must respond with a 2xx status code within 10 seconds. If it does not, Jomioz retries delivery with exponential back-off for up to 72 hours. Design your handler to acknowledge quickly and process payloads asynchronously.

Dashboard

The Jomioz dashboard at dashboard.jomioz.com provides a visual interface for every operation available through the API. Use it to browse and search resources, inspect event histories, monitor integration sync status, manage team members and roles, and view usage analytics. The Analytics panel surfaces request volume, error rates, webhook delivery success rates, and event throughput over configurable time windows. You can drill into individual resources or event types to diagnose issues without writing a single query.
All dashboard actions are reflected immediately in the API and vice versa — the dashboard is a thin client over the same REST API you use programmatically.

Team Collaboration

Jomioz workspaces support multiple team members with role-based access control. Invite colleagues by email and assign them one of three roles:
  • Owner — full administrative access, including billing and workspace deletion.
  • Admin — can manage resources, events, integrations, webhooks, and team members, but cannot access billing.
  • Member — can read and write resources and events, but cannot modify workspace settings or team membership.
API keys are always tied to the workspace rather than to an individual user, so rotating a key or revoking a team member’s access does not break other members’ integrations.
Create separate API keys for each service or environment that needs access. Label them clearly in the dashboard so you can revoke a single key if it is compromised without disrupting your other integrations.

Quick Start Examples

The examples below show the two most common starting points: making your first API call and registering your first webhook.
Authenticate with your API key and fetch all resources in your workspace.
A successful response returns a paginated list of resource objects. Use the next_cursor field in the response to fetch the next page.