Oura Ring Tag Routes API
**Note:** Tag is deprecated. We recommend transitioning to [Enhanced Tag](#tag/Enhanced-Tag-Routes).~~The Tags data scope includes tags that Oura users enter within the Oura mobile app. Tags are a growing list of activities, environment factors, symptoms, emotions, and other aspects that provide broader context into what's happening with users beyond the objective data generated by the Oura Ring.~~~~[More information on tag translations](https://cloud.ouraring.com/edu/tag-translations)~~
Oura Ring Tag Routes API is one of 21 APIs that Oura Ring publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
This API exposes 1 JSON Schema definition.
Tagged areas include Tag Routes. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, authentication docs, and 1 JSON Schema.
This API exposes 2 operations across 2 paths, and defines 6 schemas. It is described by OpenAPI 3.2.0, at version 2.0.
Requests are made against a single base URL, https://api.ouraring.com.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 4
Oura Ring Tag Routes API declares
4 security schemes
for authenticating requests.
It accepts HTTP bearer tokens (BearerAuth).
It supports OAuth 2.0 (OAuth2) using the authorizationCode flow, exposing 8 scopes.
An API key is passed in the header as x-client-id (ClientIdAuth).
An API key is passed in the header as x-client-secret (ClientSecretAuth).
ClientIdAuth— Client ID for webhook subscription endpoints. Must be used together with x-client-secret header.ClientSecretAuth— Client Secret for webhook subscription endpoints. Must be used together with x-client-id header.
Paths & Operations 2
Across 2 paths, the API surfaces 2 operations — 2 GET. Each is listed below with its method, path, parameters, and response codes.
Note: Tag is deprecated. We recommend transitioning to [Enhanced Tag](tag/Enhanced-Tag-Routes). ~~The Tags data scope includes tags that Oura users enter within the Oura mobile ap…
Schemas 6
The contract defines 6 schemas that model the data the API accepts and returns. The most detailed are TagModel (5 properties), ValidationError (3 properties), MultiDocumentResponseDict (2 properties), MultiDocumentResponse_TagModel_ (2 properties). Each schema is shown below with its type and property counts.
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from Oura Ring 12
Other APIs Oura Ring publishes across the network.
This is an independent, third-party profile of Oura Ring Tag Routes API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.