POST /api/v2/account/exists
Checks whether a participant account exists in the system, and whether it is registered for a specific event. Accepts an account ID, External ID, or email address as the lookup identifier.
Authentication
Authorization: Bearer <your_api_key>
Endpoint
POST /api/v2/account/exists
Body Parameters
Content-Type: multipart/form-data
|
Parameter |
Type |
Required |
Accepted Values / Format |
Description |
|---|---|---|---|---|
|
|
string |
Yes |
Numeric account ID, External ID string, or email address |
The identifier to look up. The endpoint tries to match it as an integer ID first, then as an External ID, then as an email address |
|
|
integer |
Yes |
Valid event ID |
The event to check membership against |
How the lookup works
The endpoint resolves the account by trying three strategies in order, stopping at the first match:
-
By numeric ID — if the value is an integer, it's matched against the internal account ID
-
By External ID — the value is matched against stored External IDs
-
By email — the value is matched against account email addresses
The info field in the response indicates which strategy produced the match.
Response
Success Response (HTTP 200)
{
"code": 200,
"data": {
"id": 12345,
"exist": true,
"event_exist": true,
"info": ["Account match: id"]
},
"response_id": "1700000000.12345"
}
|
Field |
Type |
Description |
|---|---|---|
|
|
integer |
Resolved internal account ID. Returns |
|
|
boolean |
|
|
|
boolean |
|
|
|
array |
Present only when a match is found. Describes which lookup strategy was used (e.g. |
Account not found
{
"code": 200,
"data": {
"id": 0,
"exist": false,
"event_exist": false
},
"response_id": "1700000000.12345"
}
Error Responses
|
HTTP Code |
Condition |
Error Message |
|---|---|---|
|
400 |
|
|
|
400 |
|
|
|
400 |
|
|
|
400 |
Event not found |
|
|
403 |
Missing or invalid API key |
|
Example Request — check by email
curl -X POST "https://your-event-domain.com/api/v2/account/exists" \
-H "Authorization: Bearer your_api_key_here" \
-F "id=john.doe@example.com" \
-F "event_id=7"
Example Response — found and registered
{
"code": 200,
"data": {
"id": 12345,
"exist": true,
"event_exist": true,
"info": ["Account match: email"]
},
"response_id": "1700000000.12345"
}
Example Response — account exists but not registered for this event
{
"code": 200,
"data": {
"id": 12345,
"exist": true,
"event_exist": false,
"info": ["Account match: email"]
},
"response_id": "1700000000.12345"
}