List Entries
Business+Read, add, change and delete the entries of a list, for example the booth staff of an exhibitor. Values are checked exactly like in the forms (required fields, choices, numbers, dates, e-mail, length and format rules), so you get the same messages as a person filling in the form. Dates use YYYY-MM-DD. Like the admin form, the API is not bound to the exhibitor deadline or the maximum number of entries. Every change is logged and sends the webhooks list_entry.created, list_entry.updated or list_entry.deleted.
Required scopes:
lists
Feature flag:
lists
Endpoints
GET
/api/v1/list-entries
List the entries of a list (template_id or template_key is required)
GET
/api/v1/list-entries/{id}
Retrieve a single entry
POST
/api/v1/list-entries
Add an entry
PUT/PATCH
/api/v1/list-entries/{id}
Change the given values of an entry (the others stay)
DELETE
/api/v1/list-entries/{id}
Delete an entry
Query Parameters
| Parameter | Description |
|---|---|
template_id
|
ID of the list (alternatively template_key) |
template_key
|
Key of the list, together with parent_entity_type |
parent_entity_type
|
event_participant (default), event or contact |
parent_entity_id
|
Only the entries of this participant, event or contact |
event_key
|
Participant lists only: the entries of all participants of this event |
search
|
Search in the values |
Request Schema
| Parameter | Type | Required | Description |
|---|---|---|---|
template_id
|
integer | No | ID of the list (or template_key) |
template_key
|
string | No | Key of the list (alternative to template_id) |
parent_entity_type
|
string | No | event_participant (default), event or contact |
parent_entity_id
|
integer | Yes | ID of the participant, event or contact the entry belongs to |
values
|
object | Yes | The field values as an object: {"field_key": value}. Choice fields take the option value, checkboxes true/false, dates YYYY-MM-DD, attendance grids a list of dates. On PATCH only the given fields change. |
Response Schema
| Field | Type |
|---|---|
id
|
integer |
template_id
|
integer |
template_key
|
string |
parent_entity_type
|
string |
parent_entity_id
|
integer |
values
|
object |
created_at
|
string |
updated_at
|
string |
Code Examples
curl -X GET "https://your-tenant.plandocket.com/api/v1/list-entries?template_key=YOUR_LIST_KEY&parent_entity_id=123" \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Accept: application/json"<?php
$apiKey = 'YOUR_API_KEY';
$baseUrl = 'https://your-tenant.plandocket.com';
$ch = curl_init();
curl_setopt_array($ch, [
CURLOPT_URL => $baseUrl . '/api/v1/list-entries?template_key=YOUR_LIST_KEY&parent_entity_id=123',
CURLOPT_RETURNTRANSFER => true,
CURLOPT_HTTPHEADER => [
'Authorization: Bearer ' . $apiKey,
],
]);
$response = curl_exec($ch);
curl_close($ch);
$data = json_decode($response, true);
print_r($data);const apiKey = 'YOUR_API_KEY';
const baseUrl = 'https://your-tenant.plandocket.com';
const response = await fetch(`${baseUrl}/api/v1/list-entries?template_key=YOUR_LIST_KEY&parent_entity_id=123`, {
method: 'GET',
headers: {
'Authorization': `Bearer ${apiKey}`,
},
});
const data = await response.json();
console.log(data);import requests
api_key = 'YOUR_API_KEY'
base_url = 'https://your-tenant.plandocket.com'
headers = {
'Authorization': f'Bearer {api_key}',
}
response = requests.get(f'{base_url}/api/v1/list-entries?template_key=YOUR_LIST_KEY&parent_entity_id=123', headers=headers)
data = response.json()
print(data)Sample Response
200 OK
{
"data": [
{
"id": 1,
"template_id": 1,
"template_key": "string",
"parent_entity_type": "string",
"parent_entity_id": 1,
"values": {},
"created_at": "2026-01-15T10:00:00+01:00",
"updated_at": "2026-01-15T10:00:00+01:00"
}
],
"meta": {
"current_page": 1,
"per_page": 25,
"total": 1,
"total_pages": 1
}
}