API and webhooks: connect your ERP, website, Zapier or Make with Remotjob
Each organization creates its own API keys with per-resource permissions, reads and loads data from its other systems, and receives signed notifications when something happens: an order, an issued invoice, a payment, a lead or stock below the minimum. Nobody has to copy data by hand.
Your systems should not depend on someone copying and pasting
When your ERP, website or spreadsheets live apart from Remotjob, someone ends up moving customers, orders and invoices from one to the other, and nobody learns in time that something changed. With the API and webhooks, your systems read and load what they need, and Remotjob tells them the moment it happens.
From key to notification, in six steps
Everything is managed from a single screen, without writing a line of code until you want to.
1
Create an API key
You give it a name and tick, resource by resource, what it can read and what it can create. If you wish, you limit the IP addresses it can be used from and set an expiry date and a per-minute call cap.
2
Save it: it is shown only once
The secret appears a single time, with a copy button; Remotjob keeps only a fingerprint and cannot show it to you again. If it is lost, you rotate the key and the old one stops working.
3
Connect your system
Your ERP, website or automation calls the API with the key: it reads customers, products, issued invoices and inventory, and creates customers, draft orders and leads. The OpenAPI documentation includes ready-to-copy examples.
4
Choose the notifications you want
You enter an https address and the events you care about: order created, invoice issued, payment received, lead created or stock below the minimum. You can send a test event before relying on it.
5
Every notification arrives signed
Remotjob signs each delivery so your system can confirm it comes from the platform and was not altered. If your system does not respond, it retries with increasing waits and keeps a record of every delivery.
6
Review, resend and control
You see calls and deliveries with their detail, resend by hand the one that failed and, if an address fails many times in a row, the subscription pauses itself and emails you.
What it includes
Keys per organization, with per-resource permissions
Each key can read or create only what you assign: customers, products, orders, issued invoices, leads or inventory. They are created, edited, rotated and revoked from the screen.
Allowed IPs, expiry and per-minute cap
A key can be used only from the IP addresses you list, expire on a date and have its own per-minute call cap, so a mistake in an external system does not overload yours.
Reading and loading business data
You read customers, products, issued invoices and inventory; you create customers, orders and leads. Orders come in as drafts: someone on your team confirms them in the Store.
Signed webhooks
Notifications for order created and confirmed, invoice issued and paid, payment received, lead created and stock below the minimum, with a verifiable signature and no personal data in the notification: it carries identifiers and amounts; you query the detail through the API.
Retries and delivery log
If your system fails, Remotjob retries with increasing waits and records every attempt with what it sent and what your system answered. You can resend by hand.
Call log
Every API call is recorded with method, path, result and duration, without storing the content sent, so you can see what each key does.
OpenAPI documentation with examples
A downloadable OpenAPI contract and examples in curl, JavaScript and Python, plus how to verify a webhook signature, inside the screen itself.
Guide for Zapier and Make
To connect tools without coding you use Zapier’s and Make’s generic webhook and HTTP modules with your key. Remotjob does not publish its own app on Zapier.
Integrate without opening the door wider than needed
An integration is a door to your data. Here each key is limited to what it needs and every use is recorded.
Each key sees only the data of its own organization; asking for another organization’s record answers as if it did not exist.
Secrets cannot be read again: the key is shown only once and the webhook secret is visible only to someone with administration permission.
Creating and rotating keys requires being a direct member of the organization with administration permission; if that person leaves the organization, their key stops working.
Webhooks go only to public https addresses: internal or private destinations are blocked, and notifications carry no names, emails or phone numbers.
What it is and what it is not
Orders created through the API stay as drafts: they are not confirmed on their own, a person on the team confirms them.
The API delivers the invoices your organization issues; never costs, margins or third-party billing data.
Zapier and Make connect through their webhook and HTTP modules; there is no dedicated Remotjob app published on Zapier.
It is included in the membership and does not consume AI credits.
Video · 1 min 5 s
API and webhooks, explained in a short video
Link copied
Link copied
English narration with Spanish subtitles.
How it works
Learn to use it in minutes
Link copied
Link copied
Keys and webhooks: your systems, connected · 25s
Frequently asked questions
How much does the API and webhooks cost?
They are included in the Remotjob membership and do not consume AI credits.
What can I read and create with the API?
You can read customers, products, orders, issued invoices, leads and inventory, and create customers, draft orders and leads. Each key can only do what you gave it permission to do.
What if I lose a key’s secret?
The secret is shown only once and cannot be recovered. You rotate the key from the screen, get a new secret and the old key stops working.
What if my system does not receive a notification?
Remotjob retries with increasing waits and records every attempt. You can see what your system received, resend the notification by hand and, if the address fails many times in a row, the subscription pauses itself and emails you.
How do I connect with Zapier or Make?
You use each tool’s webhook or HTTP module with your key. The screen includes a step-by-step guide; no coding is needed.
Connect your systems with Remotjob
Tell us which system you want to connect and what data should travel: we will show you how it would look with your keys, your permissions and your notifications.
