How to create a participant and send a welcome email

Use this guide when you want to register a new participant and immediately trigger a registration confirmation email in the same request.

Prerequisites

Your API key
The event_id of the target event
A registration confirmation email must be configured for the event in the platform

Request

Bash

curl -X POST "https://your-event-domain.com/api/v2/account/set" \
  -H "Authorization: Bearer your_api_key_here" \
  -F "event_id=7" \
  -F "first_name=John" \
  -F "last_name=Doe" \
  -F "email=john.doe@example.com" \
  -F "status=REGISTERED" \
  -F "send_email=true"

Response

JSON

{
  "code": 200,
  "errors": null,
  "data": {
    "id": 12347,
    "email": "john.doe@example.com",
    "status": "created",
    "external_id": null,
    "errors": []
  },
  "response_id": "1700000000.12347"
}

The email is dispatched as part of the same request. There is no separate field in the response confirming the email was sent — a successful 200 response with no errors indicates the operation completed fully.

Critical: never hardcode `send_email=true`

send_email=true triggers an email on every request it is present in — not only on the initial creation. This means:

If you hardcode it in your integration, the participant will receive a registration email every time their record is updated, not just when they register
This applies to any update call: changing a job title, updating a photo, modifying notification settings — all of these will trigger another email if send_email=true is included

Best practice: Pass send_email=true only in the specific request where you intentionally want to trigger the registration email. Do not include it in update calls.