Frequently asked questions
Frequently asked questions about the Jobcelis platform.
Understanding Jobcelis
What problem does Jobcelis solve?
Every time you build an app that needs to notify other services — send order updates, process payments, notify Slack — you end up writing the same retry logic, failure handling, and delivery logs. Jobcelis centralizes all that infrastructure: you send an event, configure where it goes, and we take care of the rest.
What is Jobcelis?
Jobcelis is an events and webhooks platform: data (events) is sent from the application via POST, and Jobcelis delivers them to the configured URLs (webhooks), with filters and automatic retries. It also supports scheduling tasks (jobs) to run daily, weekly, monthly, or with a cron expression.
How is Jobcelis different from Zapier or n8n?
Zapier and n8n are no-code/low-code tools with a visual interface for connecting apps. Jobcelis is a developer-first API: you send events with code (POST JSON), configure webhooks programmatically, and have full control over filters, transformations, and retries. It's more like Stripe's webhook infrastructure, but for any app.
Can I use Jobcelis in production?
Yes. Jobcelis is built with Elixir/OTP, designed for concurrent and fault-tolerant systems. It includes automatic retries, circuit breaker, dead letter queue, encryption at rest, MFA, and audit log. It's the same infrastructure used internally by platforms like WhatsApp and Discord.
What happens if Jobcelis is down?
Pending deliveries are queued and processed when the service recovers. Events are never lost. You can monitor the status in real time on the Status page (/status).
Getting Started
Where do I get my API Token?
After authentication, navigate to the Dashboard. In the API Token section the token (or its prefix) is displayed. If you just signed up, the full token was shown once when the project was created; it should be saved. The token can be regenerated from the Dashboard; the previous one will stop working.
How do I send an event from my code?
Send a POST request to /api/v1/events (or /api/v1/send) with header Authorization: Bearer YOUR_TOKEN or X-Api-Key: YOUR_TOKEN and Content-Type: application/json. The body can be any JSON; optionally include a "topic" field to classify the event. The documentation at /docs has curl examples.
What is a webhook and what is it for?
A webhook is a configured URL endpoint. When an event arrives that meets the conditions (topic, filters), Jobcelis sends a POST to that URL with the data. This way the receiving server or system gets the information in real time without polling the API. Multiple webhooks can be configured and filtered by topic or payload fields.
What happens if a delivery fails?
Jobcelis automatically retries with increasing intervals. The status of each delivery is visible in the Dashboard, where failed deliveries can be manually retried. Deliveries that exhaust all retries are moved to the Dead Letter Queue, where they can be reviewed and resent.
Features
How do I set up a job to run every day at a certain time?
In the Dashboard, Jobs → Create. Select type "Daily" and configure the hour and minute. As an action, select "Emit event" (with topic and payload) or "POST to URL". For more complex schedules (every 15 min, Mondays only, etc.) select type Cron and define the cron expression; in the Documentation, "Configuring jobs and cron" section, you will find the field table and examples.
What is the Dead Letter Queue?
It is where deliveries go after exhausting all automatic retries. From the Dashboard you can see the error, fix the webhook URL if needed, and retry the delivery manually. You can also mark a dead letter as resolved.
How do I replay events?
Past events can be replayed to webhooks using the Replay API. Filter by date range, topic or specific webhook. Allows reprocessing historical events after code changes or system migrations.
How do I verify a webhook signature?
Each delivery includes a signature header that you can verify with your API token. This lets you confirm the POST comes from Jobcelis and was not tampered with. The documentation at /docs has verification examples in all SDKs.
What are pipelines?
Pipelines let you chain transformations on your events before delivering them. You can filter by conditions, transform the payload, and route to different webhooks with rules. They are useful for complex flows where an event needs different processing based on its content.
What is the sandbox?
The sandbox provides temporary test endpoints to validate webhooks during development without requiring a public server. Create a sandbox endpoint, configure it as the webhook URL, and view all incoming requests.
Technical and security
What is the difference between API Key and JWT?
The API Key (project token) is used for all platform operations: sending events, configuring webhooks, managing jobs, etc. The JWT is used only for user authentication (login/signup) and for managing projects and teams. In practice, most integrations only need the API Key.
Can I use Jobcelis with my favorite framework?
Yes. Jobcelis is a REST API, so it works with any language and framework: React, Next.js, Django, Laravel, Rails, Spring Boot, Express, FastAPI, etc. We also have official SDKs for 12 languages that simplify integration.
Is there rate limiting on the API?
Yes, authentication routes have rate limiting to prevent abuse. Platform routes (events, webhooks, jobs) have generous per-project limits. For custom limits, contact support.
Is it free?
Yes. Jobcelis is completely free: unlimited events, unlimited webhooks, 12 SDKs + CLI, replay, pipelines, sandbox, and more. No credit card, no trial period.
Where can I find more help?
In the Documentation (/docs) you will find concepts, getting started guides, full API reference, and integration guides. For direct support, write to us from the Contact page (/contact) or open an issue on GitHub.