Configure Your Jomioz Environments, Timeouts, and Retries

Proper configuration lets you move safely between development and production, handle transient failures gracefully, and keep your workspace aligned with your team’s operational requirements. This guide covers every configuration layer available in Jomioz, from choosing the right API base URL to setting workspace-level preferences in the Dashboard.

Environments

Jomioz provides two isolated environments: sandbox and production. Use the sandbox environment while developing and testing your integration so that no real data is affected. Switch to production only when you are ready to serve real users. Each environment has its own API keys. Keys issued in one environment are not valid in the other, so your production credentials cannot accidentally be used against sandbox resources — and vice versa. To switch environments, change the base URL in your HTTP client and swap in the corresponding API key:

Sandbox — https://sandbox.api.jomioz.com/v1
Production — https://api.jomioz.com/v1

Sandbox data is not permanent. Jomioz automatically purges sandbox resources, events, and webhook logs that are older than 30 days. Do not rely on the sandbox for long-term data storage.

API Base URLs

The table below summarises the base URL for each environment. Prefix every API path with the appropriate base URL.

Environment	Base URL
Production	`https://api.jomioz.com/v1`
Sandbox	`https://sandbox.api.jomioz.com/v1`

Storing the base URL as an environment variable makes it straightforward to switch environments without changing your application code:

# Sandbox
export JOMIOZ_BASE_URL="https://sandbox.api.jomioz.com/v1"

# Production
export JOMIOZ_BASE_URL="https://api.jomioz.com/v1"

With your base URL set, every API call follows the same pattern — for example, $JOMIOZ_BASE_URL/api/resources or $JOMIOZ_BASE_URL/api/users.

Request Timeouts

Set a request timeout on every API call to prevent your application from hanging indefinitely if the network is degraded or the server takes longer than expected to respond. Jomioz recommends a 30-second timeout for standard requests. Long-running operations such as bulk imports may warrant a higher value; refer to the specific endpoint documentation for guidance.

const response = await fetch(`${process.env.JOMIOZ_BASE_URL}/api/resources`, {
  headers: {
    Authorization: `Bearer ${process.env.JOMIOZ_API_KEY}`,
  },
  signal: AbortSignal.timeout(30_000), // 30 seconds
});

Request type	Recommended timeout
Standard read/write	30 s
Bulk operations	120 s
Webhook delivery	10 s (your server)

Retry Policy

Transient errors — network blips, rate limit responses (429), and occasional server errors (500, 502, 503) — are safe to retry. Use exponential backoff with jitter so that retrying clients do not all hammer the API at the same moment. The snippet below shows a production-ready retry helper in JavaScript:

async function fetchWithRetry(url, options = {}, maxRetries = 4) {
  const RETRYABLE_STATUSES = new Set([429, 500, 502, 503, 504]);

  for (let attempt = 0; attempt <= maxRetries; attempt++) {
    const response = await fetch(url, options);

    if (response.ok) return response;

    if (!RETRYABLE_STATUSES.has(response.status) || attempt === maxRetries) {
      throw new Error(`Request failed with status ${response.status}`);
    }

    // Exponential backoff: 1 s, 2 s, 4 s, 8 s — plus up to 1 s of random jitter
    const backoffMs = Math.pow(2, attempt) * 1_000 + Math.random() * 1_000;
    await new Promise((resolve) => setTimeout(resolve, backoffMs));
  }
}

Inspect the Retry-After header on 429 responses. Jomioz sets this header to the number of seconds you should wait before retrying, which is more accurate than a fixed backoff schedule.

Workspace Preferences

Workspace-level preferences apply to all users and integrations within your Jomioz workspace. Adjust them in Dashboard → Settings → Workspace.

Default Timezone

Set the workspace timezone to control how timestamps are displayed in the Dashboard and in exported reports. The underlying API always returns timestamps in UTC — this setting affects presentation only.

Go to Dashboard → Settings → Workspace → General.
Select your timezone from the Default Timezone dropdown.
Click Save Changes.

Notification Email

The notification email is the address Jomioz uses for billing alerts, security notices, and workspace-level system alerts. Keep it pointed at an actively monitored inbox.

Go to Dashboard → Settings → Workspace → Notifications.
Enter the address in the Notification Email field.
Click Save Changes.

You can also configure per-user notification preferences independently of the workspace default. See the Notifications guide for full details.

Data Retention

Jomioz retains event logs and webhook delivery history for 90 days by default on the Standard plan and 365 days on the Enterprise plan. To adjust the retention window:

Go to Dashboard → Settings → Workspace → Data & Privacy.
Choose a retention period from the Event Log Retention dropdown.
Click Save Changes.

Reducing the retention window permanently deletes historical data beyond the new limit. This action cannot be undone.

Get Started

Core Concepts

Guides

Integrations

Support

Configure Your Jomioz Environments, Timeouts, and Retries

Environments

API Base URLs

Request Timeouts

Retry Policy

Workspace Preferences

Default Timezone

Notification Email

Data Retention

​Environments

​API Base URLs

​Request Timeouts

​Retry Policy

​Workspace Preferences

​Default Timezone

​Notification Email

​Data Retention

Environments

API Base URLs

Request Timeouts

Retry Policy

Workspace Preferences

Default Timezone

Notification Email

Data Retention