Guides
Bring your own website, CRM or event app
Patterns for syncing EventOS with the systems you already run.
Your website sells, EventOS fulfils
Keep your own marketing site and send buyers to the hosted event page or the embed for payment. Subscribe to order.completed and attendee.created to update your CRM the moment a ticket is issued.
Your CRM is the source of truth for invitations
Issue complimentary tickets from the CRM with POST /events/{id}/registrations, using the CRM contact id as the Idempotency-Key so retries never double-issue. Store the returned attendee id to match check-ins later.
Nightly reconciliation
import requests, os
BASE = "https://eventos.rewardland.sg/api/v1"
H = {"Authorization": f"Bearer {os.environ['EOS_KEY']}"}
page = 1
while True:
r = requests.get(f"{BASE}/events/{EVENT_ID}/attendees", headers=H, params={"updated_since": since, "page": page, "limit": 200}).json()
for a in r["data"]:
upsert_contact(a)
if not r["has_more"]:
break
page = r["next_page"]Your own scanner
Scan the attendee's QR code with any camera library and POST the decoded string to /check-ins. The response tells you whether to admit, including re-entry and the reason for a refusal. Entry is recorded once per attendee no matter how many devices scan.
Zapier and Make
Both connect without code: use a Webhooks trigger with your EventOS endpoint for events, and an HTTP action with your API key for lookups and registrations. The Integrations page in Settings has step-by-step notes.