Goal
You want people to register from a website that isn’t Confera (or from a vendor’s form), but still save the registration inside Confera.
What you need
- An API key with registrations:read and registrations:write.
- A small server endpoint that your website calls (recommended).
- A way to upload/collect a receipt URL (depends on your payment flow).
Step 1: Get config
First, fetch the “registration config”. This tells you which fields are required, which ticket types exist, which payment methods are active, and whether a pricing phase is open.
Fetch config
bash
Step 2: Build the form
Use the config response to render your form:
- Render ticket_types as a dropdown.
- Render payment_methods as a dropdown.
- Render fields (only the enabled ones) and enforce required fields.
- If public_registration_enabled is false, show a friendly “closed” message.
- If open_phase is null, registrations are enabled but pricing is closed (show “try later”).
Step 3: Submit
Submit the registration from your server. Keep the key secret.
Create registration
bash
SDK (recommended)
ts
Server endpoint (recommended)
Your website should call your endpoint, and your endpoint calls Confera. This keeps the API key secret and lets you enforce your own validation.
Next.js Route Handler: /api/registration (GET config + POST submit)
ts
Browser UI: fetch config + submit
ts
Security
- Never put the API key in browser code or a website builder.
- Use one key per vendor/integration, and rotate keys regularly.
- If the conference is not live or the plan ends, keys stop working automatically.