JBadge 1.3 — The Workspace API

JBadge 1.3 is live, and it opens the production line to your own code. Every workspace now has its own REST API and outbound webhooks — a standalone integration surface that sits right alongside our partner integrations. Whether you build through a JBadge partner or wire it up yourself, if your HR system, event platform, or membership database already knows who needs a badge, it can now issue one directly, and hear back the moment the card is printed.

Issue without the interface

The systems that already hold your people — an HR platform onboarding a hire, a CRM registering an attendee, a member database welcoming a new sign-up — can now turn that record into a finished credential on their own. No one has to open the JBadge app and re-key what another system already knows.

Look before you spend

Every issue starts with a preview: JBadge validates the details and renders a watermarked proof before a single token is spent. Only when your system approves does the credential get issued and the print job queued.

Follow the job to the printer

Once a job is on its way, your systems can watch it the whole way: track its status through to printed, pull the proof image, see the free-reprint budget, or trigger a reprint — and check which of your paired printers are online before you send.

Get told, don’t poll

Point JBadge at one of your endpoints and we’ll call you when a job reaches the printer, or when one fails for good. Wire up a Slack ping, close the loop in your own database, or kick off whatever happens next — no polling, no waiting.

Where to start

The Workspace API and webhooks live under Settings → API & Webhooks, where you can mint a key and register an endpoint. The full reference — every request, response and event — is at /tenant-api/docs.

Thanks for building on JBadge. More soon.