Pro feature, off by default. Webhooks can send your location data off your device — to a server you choose. Nothing is sent until you configure an endpoint, and the settings screen leads with a prominent warning card.
What it's for
If you run your own location infrastructure — Dawarich, an OwnTracks recorder, Traccar, or anything that accepts HTTP posts — webhooks turn iso.me into a source for it. Known-good endpoint patterns:
| Service | Endpoint shape | Format |
|---|---|---|
| Dawarich | …/api/v1/owntracks/points | OwnTracks |
| OwnTracks recorder | …/pub | OwnTracks |
| Traccar | per your installation | JSON / OwnTracks |
| Anything else | any HTTPS URL | any of the 8 formats |
Configuration
- Endpoint — the URL to POST to.
- Format — JSON, CSV, Markdown, GeoJSON, GPX, KML, OwnTracks, or Overland.
- Authentication — none, API key in the query string, Bearer token, Basic auth, or a custom header. Credentials live in the iOS Keychain, never in plain preferences, and error messages mask them.
Send modes
| Mode | Behavior |
|---|---|
| Real-time (default) | Each newly recorded point is sent as it's saved. On launch the sender “arms” itself first, so enabling webhooks never bulk-dumps your history. |
| By count | Points queue and flush every 5 / 10 / 25 / 50 / 100 points. |
| By time | Queued points flush every 1–60 minutes. |
| Manual | Nothing sends automatically; Send now posts your entire saved history (visits and points). |
Batch modes show a live queue count with a Flush queue button. Failed sends retry automatically with backoff on network errors and server hiccups (5xx, timeouts, rate limits); authentication failures don't retry — they surface as an error. Test connection posts a single harmless sample point so you can verify an endpoint before committing.
Know your destination. This is the one feature that transmits your location data off-device. Use endpoints you trust (ideally your own servers), and remember queued-but-unsent points in batch modes are lost if iOS terminates the app before a flush.