API · v1 · read-only
PASE API
The PASE API lets another system read the data of an event: its totals, the registrations and the check-ins recorded at the door. It is read-only, it is meant for server to server use, and each key belongs to a single event.
Overview
- Read-only. Every request is a
GET. The API does not create, edit or delete anything. - Version 1. The version is part of the path:
/api/v1. - Server to server. It is meant to be called from your server (a CRM, a dashboard, a sync job), not from a browser.
- One key per event. Each key sees a single event. The event always comes from the key: no request parameter selects it.
- JSON over HTTPS. Responses are JSON in UTF-8. Dates are in ISO 8601 format with a time zone offset.
Base URL
https://pase.somosder.ar/api/v1
Getting a key
The event organizer creates the key from the PASE panel. There is no need to request it from anyone.
- Log in to the panel with a user that has manager permission on the event (the organizer or an administrator).
- Open the event and go to the "API" section.
- Give the key a name that will help you recognize it later (for example, the system that will use it) and create it.
- Copy it right then and store it somewhere safe.
- It is shown only once. PASE stores a hash of the key, not the key itself. A lost key cannot be recovered: revoke it and create another one.
- It can be revoked. From the same section, at any time. A revoked key stops working right away and requests that use it get a
401with the codellave_revocada. - Up to 10 active keys per event. Using one key per system lets you revoke one without cutting off the others.
- Last use. PASE records when each key was last used, to the nearest minute.
If you do not see the "API" section in your event, or the panel says the API is not enabled yet, write to contacto@somosder.com.ar or message us on WhatsApp at +54 9 11 7154-0675.
Authentication
Every request carries the key in the Authorization header, with the Bearer scheme:
Authorization: Bearer <key>
A key is made of pase_, 8 hexadecimal characters, an underscore and 48 more hexadecimal characters. The first 13 characters (for example pase_1a2b3c4d) are the prefix the panel shows so you can recognize the key; the rest is the secret.
The examples on this page read the key from an environment variable. The sample key is not real:
export PASE_API_KEY="pase_1a2b3c4d_..."
curl "https://pase.somosder.ar/api/v1/event" \
-H "Authorization: Bearer $PASE_API_KEY"
- Do not send the key in the URL or as a parameter: it is only read from the header.
- Do not put it in the code of a web page or an app: anyone who sees it can read the event data.
- If you send
event_id,eventoreventowith the id of a different event, the response is404.
Endpoints
There are three, all GET. Successful responses return 200 with an object that has a data key; lists add a pagination key.
| Path | What it returns |
|---|---|
/api/v1/event | Basic data and totals of the event the key belongs to. |
/api/v1/registrations | Registrations of the event, paginated. |
/api/v1/check-ins | Check-ins accepted at the door, paginated. |
GET /api/v1/event
Returns the basic data of the event and its totals. It takes no parameters.
Request
curl "https://pase.somosder.ar/api/v1/event" \
-H "Authorization: Bearer $PASE_API_KEY"
Response
{
"data": {
"id": "3f2b8c1e-5d4a-4f6b-9a7c-0e1d2c3b4a5f",
"name": "Sample Conference 2027",
"slug": "sample-conference-2027",
"status": "open",
"starts_at": "2027-03-18T12:00:00+00:00",
"venue": "Sample Convention Center, Buenos Aires",
"capacity": 800,
"totals": {
"registered": 412,
"checked_in": 187,
"by_attendee_type": [
{
"id": "a1a1a1a1-0000-4000-8000-000000000001",
"name": "General",
"registered": 350,
"checked_in": 160
},
{
"id": "a1a1a1a1-0000-4000-8000-000000000002",
"name": "Press",
"registered": 62,
"checked_in": 27
}
]
}
}
}
Fields
| Field | Type | Description |
|---|---|---|
id | uuid | Event identifier. |
name | string | Event name. |
slug | string | Short name used in the registration URL. |
status | string | draft, open or closed. |
starts_at | date or null | Start date and time. |
venue | string or null | Event venue. |
capacity | number or null | Capacity set on the event, if any. |
totals.registered | number | Registrations of the event, in any status. |
totals.checked_in | number | Passes that have already checked in. Each pass is counted once. |
totals.by_attendee_type | array | The same two totals per attendee type, with the id and name of each type, sorted by name. |
GET /api/v1/registrations
Returns the registrations of the event, sorted by registration date from oldest to newest.
Parameters (all optional)
| Parameter | Description |
|---|---|
limit | Page size, from 1 to 200. Default: 50. A value above 200 is lowered to 200. |
cursor | The next_cursor of the previous page, unchanged. See Pagination. |
updated_since | ISO 8601 date, for example 2027-03-18T12:00:00Z. Returns registrations created, approved or rejected, or checked in since that date. It does not detect data edits yet, such as a name change. |
type | Name of the attendee type, case-insensitive (for example press), or its id. |
checked_in | true returns only those who checked in; false, only those who did not. |
Request
curl "https://pase.somosder.ar/api/v1/registrations?limit=2&checked_in=true" \
-H "Authorization: Bearer $PASE_API_KEY"
Response
{
"data": [
{
"id": "11111111-1111-4111-8111-111111111111",
"first_name": "Lucía",
"last_name": "Ferreyra",
"full_name": "Lucía Ferreyra",
"email": "lucia.ferreyra@example.com",
"company": "Sample Company Inc.",
"attendee_type": "General",
"status": "confirmed",
"registered_at": "2027-03-02T13:15:27.48211+00:00",
"updated_at": "2027-03-18T12:04:09.512+00:00",
"checked_in": true,
"checked_in_at": "2027-03-18T12:04:09.512+00:00"
},
{
"id": "22222222-2222-4222-8222-222222222222",
"first_name": "Martín",
"last_name": "Sosa",
"full_name": "Martín Sosa",
"email": "martin.sosa@example.com",
"company": null,
"attendee_type": "Press",
"status": "confirmed",
"registered_at": "2027-03-10T14:25:41.120394+00:00",
"updated_at": "2027-03-18T12:31:55.07+00:00",
"checked_in": true,
"checked_in_at": "2027-03-18T12:31:55.07+00:00"
}
],
"pagination": {
"limit": 2,
"has_more": true,
"next_cursor": "MjAyNy0wMy0xMFQxNDoyNTo0MS4xMjAzOTQrMDA6MDB8MjIyMjIyMjItMjIyMi00MjIyLTgyMjItMjIyMjIyMjIyMjIy"
}
}
Fields
| Field | Type | Description |
|---|---|---|
id | uuid | Registration identifier. |
first_name | string | First name. If the event form does not ask for first and last name separately, it holds the full name. |
last_name | string or null | Last name, if the form asks for it separately. |
full_name | string | Full name. |
email | string | Email used to register. |
company | string or null | Company, if the form asks for it. |
attendee_type | string or null | Name of the attendee type. |
status | string | confirmed, pending (waiting for approval) or rejected. |
registered_at | date | When the person registered. |
updated_at | date | Latest activity: the most recent of the registration, the approval or rejection, and the last check-in. |
checked_in | boolean | Whether the person has checked in. |
checked_in_at | date or null | When the person first checked in. |
GET /api/v1/check-ins
Returns the check-ins of the event: one row per scan accepted at a control point, sorted by time from oldest to newest. Rejected scans (a repeated QR code, or one without permission for that zone) are not included.
Parameters (all optional)
| Parameter | Description |
|---|---|
limit | Page size, from 1 to 200. Default: 50. A value above 200 is lowered to 200. |
cursor | The next_cursor of the previous page, unchanged. See Pagination. |
since | ISO 8601 date. Returns check-ins from that date and time onward. |
control_point | Id of a control point (the control_point_id returned by this same endpoint). Returns only the check-ins of that point. |
Request
curl "https://pase.somosder.ar/api/v1/check-ins?since=2027-03-18T12:00:00Z&limit=2" \
-H "Authorization: Bearer $PASE_API_KEY"
Response
{
"data": [
{
"id": "aaaaaaaa-aaaa-4aaa-8aaa-aaaaaaaaaaaa",
"registration_id": "11111111-1111-4111-8111-111111111111",
"attendee_type": "General",
"control_point_id": "cccccccc-cccc-4ccc-8ccc-cccccccccccc",
"control_point": "Main entrance",
"sector": "Main hall",
"companions": 0,
"scanned_at": "2027-03-18T12:04:09.512+00:00"
},
{
"id": "bbbbbbbb-bbbb-4bbb-8bbb-bbbbbbbbbbbb",
"registration_id": "22222222-2222-4222-8222-222222222222",
"attendee_type": "Press",
"control_point_id": "cccccccc-cccc-4ccc-8ccc-cccccccccccc",
"control_point": "Main entrance",
"sector": "Main hall",
"companions": 1,
"scanned_at": "2027-03-18T12:31:55.07+00:00"
}
],
"pagination": {
"limit": 2,
"has_more": false,
"next_cursor": null
}
}
Fields
| Field | Type | Description |
|---|---|---|
id | uuid | Check-in identifier. |
registration_id | uuid or null | Registration the scanned pass belongs to. It is the id returned by /api/v1/registrations. |
attendee_type | string or null | Name of the attendee type. |
control_point_id | uuid or null | Identifier of the control point where the pass was scanned. |
control_point | string or null | Name of the control point. |
sector | string or null | Name of the zone. |
companions | number | Companions recorded on that scan. 0 if there were none. |
scanned_at | date | Date and time of the scan. |
Pagination
Lists (/registrations and /check-ins) use cursor pagination. Every response includes a pagination object:
| Field | Type | Description |
|---|---|---|
limit | number | The page size that was applied. |
has_more | boolean | true if there are more results. |
next_cursor | string or null | The cursor of the next page. It is null when there are no more results. |
To get the next page, repeat the request with the same filters and add cursor with the value of next_cursor. Keep going until has_more is false.
curl "https://pase.somosder.ar/api/v1/registrations?limit=2&checked_in=true&cursor=MjAyNy0wMy0xMFQxNDoyNTo0MS4xMjAzOTQrMDA6MDB8MjIyMjIyMjItMjIyMi00MjIyLTgyMjItMjIyMjIyMjIyMjIy" \
-H "Authorization: Bearer $PASE_API_KEY"
- The cursor is opaque: do not build or modify it. An altered cursor returns
400. - The cursor only marks the position. Filters (
type,checked_in,updated_since,since,control_point) must be sent again on every page. - The order is always ascending by date, so anything registered or checked in while you walk the pages shows up at the end.
- For a periodic sync, store the time the last run started and send it as
updated_since(registrations) orsince(check-ins). - In dates, use the
Zsuffix or encode the+sign as%2B: a bare+in a URL is read as a space.
Errors
All errors have the same shape. To decide what to do in your code use code, which is fixed; message is a text in Spanish meant for a person and may change. Error codes are in Spanish.
{
"error": {
"code": "llave_invalida",
"message": "La llave no es válida."
}
}
| Status | Code | When it happens |
|---|---|---|
400 | parametro_invalido | A parameter has a value that cannot be read: a limit that is not a number of 1 or more, a date that is not ISO 8601, an altered cursor, a checked_in that is neither true nor false, or a control_point that is not an id. |
401 | sin_llave | The Authorization: Bearer header is missing. |
401 | llave_invalida | The key does not have the expected format or does not exist. |
401 | llave_revocada | The key was revoked from the panel. |
404 | no_encontrado | The path does not exist, or the request carries the id of an event other than the one the key belongs to. |
405 | metodo_no_permitido | The method is not GET. The response includes the header Allow: GET. |
429 | demasiados_pedidos | The request limit was exceeded. The Retry-After header says how many seconds to wait. |
500 | error_interno | Something failed on the PASE side. You can retry a moment later. |
503 | api_no_habilitada | The API is not enabled yet. Write to us to have it enabled. |
Limits
- 120 requests per minute per key. The counter is kept in memory, per server instance: it is not a global counter, so the cutoff may not be exact when requests land on different instances. Responses to requests with a valid key include the header
X-RateLimit-Limit: 120. - 600 requests per minute per IP address, counted before the key is validated.
- When a limit is exceeded the response is
429with theRetry-Afterheader, in seconds. Wait that long before sending another request. - Up to 200 results per page.
- No CORS. The API does not send the
Access-Control-Allow-Originheader, so a page on another site cannot read it from the browser. It has to be called from a server. - No caching. Every response is sent with
Cache-Control: no-storeand every request reads the current data.
Data it does not return
The API returns only the fields listed on this page. Even if the event asked for them at registration, it does not return:
- ID document numbers.
- Phone numbers.
- Photos or selfies.
- Biometric data.
- Internal fields used by the event team.
What it does not do yet
- Writing. Creating or editing registrations and recording check-ins through the API: coming soon, no date set.
- Webhooks. Automatic notifications to your system when someone registers or checks in: coming soon, no date set. For now, changes are polled with
updated_sinceandsince. - There are also no keys that cover several events, no SDKs and no OAuth.
Contact
For questions about the API, or if you do not see the "API" section in the panel of your event:
Email: contacto@somosder.com.ar
WhatsApp: +54 9 11 7154-0675