Chimeling API

Presence, devices, apps, everything, over HTTP.

Open reference

One job per call, verbs you already know, and standards-compliant

Room
in the object

A device stores presence as an open object. status, reportedAt, and activity are the fields this API reads today.

The next fact does not need a new endpoint. A track, a game, or a playable character can sit in that same object, and the public read grows when those fields do.

{
status: "online"
reportedAt: "2026-11-07T09:00:00Z"
activity: { appId, startedAt }
}

Call it from anything

The reference is generated from the routes. Start with the public read, or take the document and generate a client.

  • POST/api/v1/icons
  • GET/api/v1/devices/{deviceId}/apps
  • HEAD/api/v1/icons/{hash}
  • GET/api/v1/devices
  • GET/api/v1/devices/{deviceId}/apps/{appId}
  • POST/api/v1/devices
  • DELETE/api/v1/devices/{deviceId}/presence
  • DELETE/api/v1/devices/{deviceId}/apps/{appId}
  • GET/api/v1/icons/{hash}/image
  • GET/api/v1/presence/{userId}
  • PATCH/api/v1/devices/{deviceId}/apps/{appId}
  • PUT/api/v1/devices/{deviceId}/presence
  • PATCH/api/v1/devices/{deviceId}
  • GET/api/v1/devices/{deviceId}
  • DELETE/api/v1/devices/{deviceId}
  • POST/api/v1/devices/{deviceId}/apps
  • GET/api/v1/icons/{hash}

Grow with Chimeling

Save your seat. We’ll call you over.