---
title: "Test Android Chronometer"
method: POST
path: "/api/scheduled-notifications/admin/test-android-chronometer"
tags: ["scheduled-notifications"]
---

# Test Android Chronometer

`POST /api/scheduled-notifications/admin/test-android-chronometer`

Send the Android streak-saver chronometer push to one user's device for testing.

Android counterpart of /admin/test-live-activity: fires the exact Expo data push the
streak-loss cron sends (type="streak" + the user's local-midnight deadline); the app's
native FCM handler renders the ongoing countdown notification. Deliberately BYPASSES
the android_streak_chronometer_enabled feature flag so the flow stays testable in
production while the cron is dormant — single-user only, so there is no broadcast risk.

- x-user-id (header): user to send to (must have stored Expo push_tokens)
- Body (optional): {"streakCount": N} to override the count shown; defaults to 7.
- Requires x-api-key header for authentication.

## Headers

- `x-user-id` string, required
- `x-api-key` string, required

## Request body

- TestAndroidChronometerRequest
  - `streakCount` integer, nullable — Streak count shown on the card (defaults to 7)

## Response `200`

Successful Response

- unknown

## Other responses

- `422` — Validation Error

---

[API](https://skmtc.net/usecreed/apis/creed-api.md) · [All operations](https://skmtc.net/usecreed/apis/creed-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/usecreed/creed-api/revisions/cb25d3fef898/schema)