API & Developers: From Clicks to Code

Admins automate Kemicard with Flow. Developers go further with invocable Apex actions, the REST API, and webhooks. Either way, the pass lifecycle — issue, update, revoke, query — is fully programmable from inside and outside Salesforce.

API Reference Documentation

Flow first

Invocable Actions for Every Pass Operation

Kemicard exposes its core operations as invocable actions available to Flows and automation across Sales Cloud, Service Cloud, Nonprofit Cloud, and Marketing Cloud journeys. If your admin can build a Flow, they can run the pass lifecycle.

Generate Pass — create a pass for a record against a chosen template.
Send Message — push a notification to one pass or a whole segment.
Switch Template — change a pass design in real time (tier upgrades, seasonal cards, error states).
Expire / Revoke — end-of-life a pass from the same automation that issued it.

Browse the actions

// Apex: issue a pass from a trigger-safe context
KemicardAPI.GeneratePassRequest req =
    new KemicardAPI.GeneratePassRequest();
req.recordId  = contact.Id;
req.template  = 'Gold_Member';
req.sendEmail = true;

KemicardAPI.GeneratePassResult res =
    KemicardAPI.generatePass(req);

System.debug(res.passUrl); // signed add-to-wallet link

REST API

Issue, Update, and Revoke Passes Over HTTPS

Authenticate with a bearer token and drive passes from any system — HubSpot workflows, a POS, a booking engine, or your own app.

`POST /passes`

Create a pass from a record ID and template. Returns a signed add-to-wallet URL that resolves per device.

`PATCH /passes/:id`

Update fields, switch templates, or trigger a push notification for an installed pass.

`DELETE /passes/:id`

Revoke a pass. The wallet copy is invalidated and the action logs with a timestamp.

`GET /passes/:id`

Query pass status: installed, removed, last updated, last scanned.

Webhooks

Subscribe to pass.installed, pass.scanned, pass.updated, and pass.removed — JSON payloads POSTed to any listener you register.

Sandbox-first

Full API available in sandbox orgs, so CI and UAT flows run before production.

Architecture

How the Pipeline Works

Your org calls the Kemicard backend through a named credential. Pass events stream through a Pub/Sub pipeline to Apple's APNs and the Google Wallet API — so updates land on phones in seconds, at bulk scale.

1. Salesforce org

Records, templates, Flows, and the Kemicard managed package — your system of record.

2. Named credential

Secure, admin-controlled authentication from your org to the Kemicard backend.

3. Event pipeline

Real-time pass event processing handles generation, updates, and push fan-out.

4. Wallets

Signed .pkpass bundles to Apple Wallet via APNs; JWT-signed objects to Google Wallet via the Wallet API.

Build on Kemicard

Get the full API reference, or talk to us about a custom integration.

API Reference Talk to Us