Documentation
Gestures
ARKH Ring supports seven gesture types. When a user installs your app, all gesture events are automatically forwarded to your webhook — no additional configuration required.
Gesture Type
Description
single_tapQuick single tap on the ring surface
double_tapTwo quick taps in succession
triple_tapThree quick taps in succession
swipe_upSwipe finger upward on ring
swipe_downSwipe finger downward on ring
swipe_leftSwipe finger left on ring
swipe_rightSwipe finger right on ring
How It Works
Automatic Forwarding: Once your app is installed and a webhook URL is configured, every gesture the user performs is sent to your webhook. You don't need to "enable" specific gestures.
Action Labels (Optional): In the developer console, you can provide descriptive names for each gesture (e.g., "Play/Pause" for single tap). These labels are shown to users in the companion app's info card, helping them understand what each gesture does. If you skip this step, gestures still work — users just won't see descriptions.
Privacy Controls: Users can disable gesture forwarding for your app in the widget manager. If disabled, your webhook will not receive gesture events from that user.
Receiving Gestures
When a user performs a gesture, your webhook receives a POST request with the gesture event. The payload includes the gesture_type, your app's user_app_id for the user, and a timestamp.
See Webhooks Documentation
For the complete payload structure, verification, and response handling, see the Webhooks documentation. Gesture events use "event": "gesture" with the specific gesture_type in the payload data.
Responding to Gestures
Your webhook should respond with a 200 status code to acknowledge receipt. You can optionally trigger a vibe in your response to give the user haptic feedback.
See Webhook Response Handling for the complete response format and options.