1) Endpoint & HTTP Method

Base endpoints

API Endpoint: https://api.sitelytics.tech/pixel/core/api/sync
Send‑event (GET): https://api.sitelytics.tech/pixel/core/api/send-event/get

Supported methods

GET
POST (for POST the body is not URL‑encoded — “not URLENCODED!!!!”)

Recommendation: use GET with query parameters and URL‑encode event_data and event_url. For POST, send a JSON body and do not URL‑encode event_data.

2) Request Parameters

Required parameters

event_type — String. The tracked event type. Must be a non‑empty string.
event_data — URL‑encoded JSON (for GET). Event payload:
- The server URL‑decodes this value before processing.
- The decoded value must be valid JSON and match your schema (if any).
- For POST, this is not URL‑encoded (sent as JSON).
organization_id — String (UUID). Organization identifier.
- Must be a valid UUID.
pixel_id — String (UUID). Pixel instance identifier.
- Must be a valid UUID.
event_url — URL‑encoded string (for GET). Source page URL.
- Must be a valid URL after decoding.

Optional parameters

gdpr — String. Optional GDPR consent string.
gpp — String. Optional IAB GPP string.
redir — URL‑encoded string. Optional redirect URL supporting placeholders:
- Supported: $DLVRCOOKIE, $DLVRHEM, $REF, $EVENTTIME.

3) Validation rules (short)

event_type — non‑empty string.
event_data — URL‑decode and parse as JSON (GET); valid JSON (POST).
organization_id, pixel_id — valid UUIDs.
event_url — valid URL after decoding (GET).
gdpr, gpp — if present, follow their respective formats/length constraints (IAB GPP).
redir — valid URL after decoding; placeholders are substituted by the server.