canonical: https://jentic.com/apis/reachr.co/reachr

# Reachr API

Reachr API for OAuth2 authentication, user verification, and webhook management. The API exposes 5 endpoints secured with bearer authentication.

## For AI agents

Programmatically oauth2 authorization, exchange authorization code for token. Covers 5 operations with bearer authentication.

## Scope

Does not handle payments, communications, or crm - use for developer tools only.

## Capabilities

- OAuth2 authorization
- Exchange authorization code for token
- Verify connection
- Register webhook
- Unregister webhook

## Use cases

### Developer Tools Operations

Use the Reachr API to perform developer tools operations programmatically. The API provides 5 endpoints covering core functionality including oauth2 authorization, exchange authorization code for token, verify connection.

Example prompt: Call GET `/oauth/authorize` to oauth2 authorization

### Automated OAuth Management

Automate oauth operations by combining multiple Reachr API endpoints. Agents can exchange authorization code for token and then verify connection in a single workflow.

Example prompt: Call POST `/oauth/token` to exchange authorization code for token, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Reachr API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle bearer tokens manually.

Example prompt: Search Jentic for 'oauth2 authorization', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/oauth/authorize` | OAuth2 authorization |
| POST | `/oauth/token` | Exchange authorization code for token |
| GET | `/integrations/zapier/me` | Verify connection |
| POST | `/integrations/zapier/hooks/subscribe` | Register webhook |
| DELETE | `/integrations/zapier/hooks/subscribe` | Unregister webhook |

## Key resources

- **OAuth** — Operations related to OAuth
- **Zapier** — Operations related to Zapier

## Why Jentic

- **Setup:** Wiring the Reachr API by hand means running its OAuth authorize and token exchange, then managing the Zapier hook subscribe and unsubscribe calls with a bearer token yourself. Through Jentic you install once, import the Reachr API from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** The Reachr API passes hook details in the request body, so you limit the agent to the operations it needs, such as reading the current integration identity or subscribing a hook. It only calls the operations you allow, so unsubscribing a hook is out of scope unless you add it.
- **Credential handling:** Your Reachr API token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'get the current integration identity' or 'subscribe a webhook', and Jentic returns the matching Reachr API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Github** — Alternative developer tools API
- **Gitlab** — Alternative developer tools API

## FAQ

### What authentication does the Reachr API use?

The Reachr API uses a Bearer token in the Authorization header. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I oauth2 authorization with the Reachr API?

Yes. Use the GET `/oauth/authorize` endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Reachr API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I oauth2 authorization through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'oauth2 authorization'. Jentic returns the matching Reachr API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Reachr API have?

The Reachr API exposes 5 endpoints covering oauth, zapier operations.

### Can I limit what my agent is allowed to do with the Reachr API?

Yes. Jentic One is self-hosted by you, so your own rules decide which Reachr API operations and credentials the agent can use. You can allow only the operations the agent needs, such as reading the current integration identity or subscribing a webhook, while keeping others out of reach. Because it calls only the operations you permit, actions like unsubscribing a webhook or exchanging an authorization code for a token stay out of scope unless you add them.