Donalsien Akwo Kum   •   13 days ago

Ring track: does “simulator” include one I wrote myself?

My project integrates the Ring Partner API: OAuth token exchange and refresh, device discovery, the capabilities relationship, and the event history endpoint. I verified those against api.amazonvision.com using a Developers Playground token, and my adapter parses Ring’s real JSON:API envelope.

The part my product actually consumes is motion and door events. The Developers Playground simulates a live view session (WHEP/SDP) and I could find no way to make it deliver a motion or doorbell event to a registered webhook, and its history endpoint returns zero events for the sandbox device. I have written this up in my friction log.

So I built an event feeder that posts Ring-shaped payloads to my own /ring/events endpoint over HTTPS, signed with the real HMAC key. Everything past the endpoint is the production path: signature verification, the Ring adapter, the store, the detection engine and the notifications.

The rules say “Any Ring API, SDK, simulator, or device listed in Ring’s developer documentation is acceptable” and then “The demo video must show the project working through a simulator or an actual Ring device.”

My question: does “a simulator” in that second sentence include a simulator I wrote myself, given that the Ring integration itself is against the real API? Or does the demo need to show a Ring-provided simulator specifically?