Welcome to the Nowatch Research API

The Nowatch Research API lets you access physiological and contextual data collected by NOWATCH devices and processed by the NOWATCH App, designed for scientific and research use.

Getting Started

• Quick start guide

Data description and Context

• User
• Timeline
  • Sleep
  • Activities
  • Check-ins
• Overview
• Check-Ins
• Feelings
• Intentions
• Coming soon

API Reference

• User
• Timeline
  • Sleep
  • Activities
  • Check-ins
  • Timezone
  • Crown Presses
• Overview
• Feelings
• Intentions

Rate limits

Each endpoint enforces a per-API-key budget. Every response carries the standard rate-limit headers so clients can pace themselves:

Header	Meaning
X-RateLimit-Limit	Total quota for this bucket.
X-RateLimit-Remaining	Requests left in the current window.
X-RateLimit-Reset	Seconds until the window resets.
Retry-After	Only on 429 — seconds until retry.

Buckets are keyed on the X-API-KEY header. A single key calling from multiple IPs (CI, laptop, prod) shares one bucket. Requests without a key fall back to per-IP bucketing.

When the limit is exceeded, the API returns 429 Too Many Requests as an RFC 7807 problem document with code: "rate_limited", the same rate-limit headers, and a Retry-After value. Clients should honour Retry-After rather than guess.

Use cases & Examples

• Tips & Best Practices
• Examples

Contact and Support

For questions or support, please reach out to samson@nowatch.com.