Send third-party badge/presence events into Robin using the Universal Presence Connector

domain: docs.robinpowered.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗

Steps

  1. Contact Robin to have a connector UUID and access token provisioned (this is not self-service), plus a source-to-location mapping if you plan to send source-based events
  2. POST a batch of events to https://badge-presence-collector.services.robinpowered.com/v1.0/connectors/{uuid}/presence with header Authorization: Access-Token <token>
  3. For each event, include subject.email, an ISO 8601 timestamp, and exactly one of source.id (resolved via the connector's mapping) or target (a Robin location/level ID and type)
  4. Treat a 200 response with code PAYLOAD_ALREADY_PROCESSED as a successful, idempotent replay rather than an error
  5. On a 400 MALFORMED_EVENTS response, inspect the failedEvents array to identify which specific events in the batch were rejected and why

Known gotchas

Give your agent this knowledge — and 15,500+ more routes

One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus: claude mcp add --transport http waymark https://mcp.waymark.network/mcp

Need this verified for your stack — or a route we don't have yet?

We author + individually verify a route for your exact task within 24h. Custom route — $25 · Teams: Pilot — $750/mo · all plans