Accessing and Integrating with the Rhythms REST API

Last updated: August 25, 2026

The Rhythms REST API allows you to connect external tools and platforms to your Rhythms data, enabling integrations with Business Intelligence tools, third-party platforms, and custom workflows. This article covers how to obtain API access, what data is available, and what integration options exist.

API Documentation

Full API documentation is available at https://apidocs.rhythms.ai/, covering available endpoints, authentication, and request formats. REST API endpoints are specifically documented at https://apidocs.rhythms.ai/rest/v2.

The live docs are the best place for developers to go deeper. Alongside the full request and response schema for every endpoint, they offer:

  • Try it — send a real, authenticated request from the browser and see the actual response, without writing any code.
  • Connect to Cursor — load the API definition straight into an AI coding assistant such as Cursor, so it can read the available endpoints and fields while you build your integration.

This article covers access and options. Use the live docs when you are ready to explore specific endpoints or test requests.

Obtaining an API Token

To get an API token for connecting external tools to Rhythms, contact Rhythms support. When reaching out, please provide the following information:

  • Whether the person requesting the token is a Rhythms admin or a member

  • If the requester is a member (non-admin), their name and email address

The type of token generated depends on the requester's role:

  • Admin: An org-wide token will be created.

  • Member (non-admin): A token specific to that individual user will be created.

API tokens follow the format tokp_ followed by a hexadecimal string (e.g., tokp_1abc23c45d...). This token is used as a Bearer token in the Authorization header of your API requests.

What Data Can You Access?

The Rhythms REST API allows you to retrieve information including:

  • Check-ins

  • Team owners

  • Goal descriptions and other goal-related fields

Consider Native Alternatives Before Building a Custom Integration

Before investing in a custom API integration, it's worth considering whether one of Rhythms' built-in options already meets your needs:

  • Native document/dashboard capability: This feature can pull data directly from your OKRs and connected tools (such as Slack and HubSpot) and auto-updates as your team checks in. For many reporting and BI use cases, this may be a faster and simpler solution than building a custom API integration.

  • Rhythms MCP server: For more advanced use cases—such as natural language queries, analyzing documents, pulling check-in compliance rates, or traversing a knowledge graph of your organization's operating data—the Rhythms MCP server may be more powerful than the REST API. It supports AI tools like Claude, ChatGPT, and Cursor. Documentation on the MCP server is available in the Rhythms help center.

If you require a custom or external integration that isn't covered by these native options, the REST API is the appropriate path. Contact Rhythms support to request your API token and get started.