Documentation Index
Fetch the complete documentation index at: https://developer.trackpilots.com/llms.txt
Use this file to discover all available pages before exploring further.
๐งช Beta FeatureWebhook Simulations let you fire a real, signed test event to your endpoint โ no need to trigger a live desktop event.
๐ Overview
Webhook Simulations allow you to verify that your webhook endpoint is correctly receiving, parsing, and responding to Trackpilots events. When you run a simulation, Trackpilots:- Builds a realistic sample payload for the selected event type
- Signs it with your webhookโs secret key (identical to live delivery)
- POSTs it directly to your configured webhook URL
- Returns the HTTP status, response body, and latency back to you in the dashboard
๐ How to Run a Simulation
- Open Developer Tools โ Simulations in your Trackpilots dashboard.
- Select the Webhook Endpoint you want to test from the dropdown.
- Choose the Event Type to simulate โ only events registered for that webhook are shown.
- Click Send Test Event.
- View the result in the Simulation Result panel on the right.
โ ๏ธ Your webhook endpoint must be publicly accessible for the simulation to reach it.
Use ngrok or a similar tunnel to expose a local server during development.
Use ngrok or a similar tunnel to expose a local server during development.
๐ Simulation Result Panel
After sending, the result panel shows:| Field | Description |
|---|---|
| Status | HTTP status code returned by your endpoint (color-coded) |
| Latency | Round-trip time in milliseconds |
| Delivered / Failed | Whether your endpoint returned a 2xx response |
| Delivery Headers | The X-Webhook-Signature and X-Webhook-Timestamp sent |
| Sent Payload | The exact JSON body that was posted to your endpoint |
| Endpoint Response | The raw response body returned by your server |
๐ฆ Simulation Payload Structure
Simulation payloads are identical in structure to live events with one additional field โ"simulation": true โ so your server can distinguish test events from real ones if needed.
Activity Tracking
App Tracking
Screenshot Tracking
๐ธ Screenshot imageBufferReal screenshot events include a raw binary image buffer.
Simulations send a placeholder string instead:
Make sure your parser handles both gracefully.
Simulations send a placeholder string instead:
"[simulation-placeholder: binary image buffer not included]".Make sure your parser handles both gracefully.
๐ Signature Verification
Simulation requests are signed exactly like live events using HMAC SHA-256. Your server receives:X-Webhook-Signature. See the Webhooks verification guide for the full implementation.
๐งช Testing Locally with ngrok
- Start your local webhook server (e.g. on port 3000)
- Expose it with ngrok:
- Copy the generated HTTPS URL and set it as your Webhook URL in Trackpilots:
- Run a simulation โ the request will tunnel through ngrok to your local server.
โ What a Successful Simulation Looks Like
TRACKPILOTS_WEBHOOKS_SECRET_KEY in your environment matches the secret shown on your webhook in the dashboard.
If you see 400 Missing signature โ make sure your server reads both x-webhook-signature and x-webhook-timestamp headers (lowercase).
๐ Related
