Skip to content
Logistics & shipping

waterlinked.com

The Water Linked Underwater GPS sandbox and mock API

API for the Water Linked Underwater GPS. For more details: http://www.waterlinked.com Recommended approach for connecting to a Underwater GPS via the API is: - If "GET /api/" times out, the Underwater GPS is not running (on this IP address) - If "GET /api/" responds with 200 OK check that the api version returrned (eg "v1") is supported by the client (eg: also supports "v1"). - If the api version Writes persist, data moves on a schedule and every change can fire a signed webhook.

Operations
38
Collections
-
Event types
-
Start this simulation
example request
curl https://your-waterlinked.slurry.io/api/ \
  -H "Authorization: Bearer slurry_sim_..."

Your simulation gets its own hostname, key and IP allow-list. Built from API version 1.0.0.

What gets simulated

Collections, relationships and state machines are worked out from the spec when you start the simulation.

  • State. Creates, updates and deletes persist and show up in later reads.
  • Behaviour. Records move through their states on a schedule you control, and you can fast-forward up to 30 days.
  • Webhooks. Every change emits a signed, retried event.
  • Failure. Per-endpoint errors, latency and chaos rules, on demand.

Operations

First 12 of 38.

  • GET/api/
  • GET/api/v1/about
  • POST/api/v1/about/factoryreset
  • GET/api/v1/about/led
  • GET/api/v1/about/status
  • GET/api/v1/about/temperature
  • GET/api/v1/config/antenna
  • PUT/api/v1/config/antenna
  • GET/api/v1/config/generic
  • PUT/api/v1/config/generic
  • GET/api/v1/config/ip
  • PUT/api/v1/config/ip