Troubleshoot Jomioz: Fix Auth, Webhooks, and API Issues

Use this guide to quickly identify and fix the most common problems you may encounter while working with Jomioz. Each section describes the symptom, explains what causes it, and walks you through the steps to resolve it.

Authentication Errors

Authentication failures prevent your requests from reaching the API. The two most common status codes and their fixes are listed below.

Status Code	Cause	Fix
`401 Unauthorized`	Missing or invalid API key	Verify that your request includes the `Authorization` header with a valid key. The correct format is `Authorization: Bearer YOUR_API_KEY`. Check that you haven’t accidentally included extra spaces or newline characters.
`403 Forbidden`	Key exists but lacks the required permissions	Open Dashboard → Settings → API Keys, review the role assigned to the key, and confirm it includes the permissions needed for the operation you are attempting.

API keys are workspace-scoped. Make sure you are using a key that belongs to the same workspace as the resource you are trying to access.

Rate Limit Errors

When you exceed your plan’s request quota, the API returns a 429 Too Many Requests response. Every API response includes two rate-limit headers you can use to manage your request cadence:

Header	Description
`X-RateLimit-Remaining`	Number of requests remaining in the current one-minute window
`X-RateLimit-Reset`	Unix timestamp (UTC) indicating when the window resets

Recommended approach — exponential backoff: When you receive a 429, pause before retrying. Double the wait time on each successive failure to avoid hammering the API and extending your lockout period.

python

import time
import requests

def request_with_backoff(url, headers, max_retries=5):
    delay = 1  # initial delay in seconds
    for attempt in range(max_retries):
        response = requests.get(url, headers=headers)
        if response.status_code != 429:
            return response
        print(f"Rate limited. Retrying in {delay}s...")
        time.sleep(delay)
        delay *= 2  # exponential backoff
    raise Exception("Max retries exceeded")

Monitor X-RateLimit-Remaining proactively and slow down your request rate before it reaches zero rather than waiting for a 429.

Webhook Delivery Failures

If your webhook endpoint is not receiving events, work through the following checklist.

Webhook delivery checklist

Your endpoint returns HTTP 200. Jomioz considers any non-2xx response a delivery failure and will retry with exponential backoff.
Your endpoint responds within 10 seconds. Requests that time out are treated as failures. Offload heavy processing to a background job and return 200 immediately upon receipt.
Your endpoint accepts HTTP POST requests. Jomioz sends all webhook payloads as POST requests with a Content-Type: application/json body.
Review delivery logs. Open Dashboard → Integrations → Webhooks → Delivery Log to inspect every delivery attempt, including the request payload, response code, and error message if applicable.
Check for firewall or IP restrictions. If your server restricts inbound traffic, ensure it allows connections from Jomioz’s outbound IP ranges (listed in Dashboard → Integrations → Webhooks).

After repeated delivery failures Jomioz will automatically disable the webhook endpoint. Re-enable it from Dashboard → Integrations → Webhooks once the underlying issue is resolved.

Resource Not Found

A 404 Not Found response means the API could not locate the resource you requested. Work through these checks in order:

Verify the resource ID. Copy the ID directly from the Dashboard or from a previous API response to rule out typos.
Confirm the correct workspace. Resources are workspace-scoped. Ensure your API key and the resource ID both belong to the same workspace.
Check your environment. Jomioz has separate sandbox and production environments. A resource created in the sandbox is not visible in production and vice versa. Confirm you are targeting the right base URL.

bash

# Production
curl -X GET https://api.jomioz.com/v1/resources/RESOURCE_ID \
  -H "Authorization: Bearer YOUR_API_KEY"

# Sandbox
curl -X GET https://sandbox.api.jomioz.com/v1/resources/RESOURCE_ID \
  -H "Authorization: Bearer YOUR_SANDBOX_API_KEY"

Slow API Responses

Occasional latency spikes are normal, but consistently slow responses may indicate a configuration issue on your end. Try these optimizations:

Use pagination. Retrieve large collections in pages using the limit and cursor query parameters rather than requesting all records at once.
Filter fields. Use the fields query parameter to request only the properties your application needs, reducing payload size.
Avoid polling loops. Replace tight polling loops with webhooks to receive event-driven updates without generating unnecessary API traffic.
Check your network path. Run a request from a server geographically close to Jomioz’s API endpoints to rule out network latency.

If you consistently see response times above 5 seconds for standard requests, contact support and include representative curl timing output so the team can investigate.

Getting Help

If you’ve worked through the relevant section above and the issue persists, reach out to the Jomioz support team directly.

Dashboard Support Chat

Start a live chat with the support team directly from your Dashboard. Include your workspace ID and any relevant error messages to get help faster.

Email Support

Send a detailed description of your issue to support@jomioz.com. Attach request IDs, status codes, and reproduction steps where possible.

Get Started

Core Concepts

Guides

Integrations

Support

Troubleshoot Jomioz: Fix Auth, Webhooks, and API Issues

Authentication Errors

Rate Limit Errors

Webhook Delivery Failures

Resource Not Found

Slow API Responses

Getting Help

Dashboard Support Chat

Email Support

​Authentication Errors

​Rate Limit Errors

​Webhook Delivery Failures

​Resource Not Found

​Slow API Responses

​Getting Help

Dashboard Support Chat

Email Support

Authentication Errors

Rate Limit Errors

Webhook Delivery Failures

Resource Not Found

Slow API Responses

Getting Help