canonical: https://jentic.com/apis/redoxengine.com/redoxengine

# Redoxengine Redox Platform API

Redox healthcare data exchange API for managing patient data, clinical summaries, orders, results, and scheduling via FHIR-compatible endpoints. The API exposes 7 endpoints secured with bearer authentication.

## For AI agents

Programmatically send message, query data. Covers 7 operations with bearer authentication.

## Scope

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

## Capabilities

- Send message
- Query data
- Authenticate
- Refresh token
- List destinations
- Get logs

## Use cases

### Healthcare Operations

Use the Redox Platform API to perform healthcare operations programmatically. The API provides 7 endpoints covering core functionality including send message, query data, authenticate.

Example prompt: Call POST /endpoint to send message

### Automated Auth Management

Automate auth operations by combining multiple Redox Platform API endpoints. Agents can query data and then authenticate in a single workflow.

Example prompt: Call POST /query to query data, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Redox Platform 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 'send message', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/endpoint` | Send message |
| POST | `/query` | Query data |
| POST | `/auth/authenticate` | Authenticate |
| POST | `/auth/refreshToken` | Refresh token |
| GET | `/organization/{orgId}/destinations` | List destinations |
| GET | `/organization/{orgId}/sources` | List sources |
| GET | `/logs` | Get logs |

## Key resources

- **Auth** — Operations related to Auth
- **Logs** — Operations related to Logs
- **Messages** — Operations related to Messages
- **Organization** — Operations related to Organization
- **Queries** — Operations related to Queries

## Why Jentic

- **Setup:** Wiring the Redox Platform API by hand means running its authenticate and refreshToken exchange to keep a bearer token fresh and handling retries against the api.redoxengine.com host yourself. Through Jentic you install once, import the Redox Platform API from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** The Redox Platform API puts the organization id in the URL path (`/organization/{orgId}/destinations` and `/organization/{orgId}/sources`), so a rule can pin your agent to one organization and let it list that organization's destinations and sources. You choose the operations it may call, so write operations like posting to /endpoint are not included unless you add them.
- **Credential handling:** Your Redox Platform API bearer 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 'query a patient record' or 'list organization destinations', and Jentic returns the matching Redox Platform API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Oystehr** — Alternative healthcare API
- **Athenahealth** — Alternative healthcare API

## FAQ

### What authentication does the Redox Platform API use?

The Redox Platform 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 send message with the Redox Platform API?

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

### What are the rate limits for the Redox Platform 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 send message through Jentic?

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

### How many endpoints does the Redox Platform API have?

The Redox Platform API exposes 7 endpoints covering auth, logs, messages operations.

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

Yes. Jentic One is self-hosted by you, so your own rules decide which Redox Platform API operations and credentials the agent may use. Because the organization id sits in the URL path, you can pin the agent to a single organization and let it read only that organization's destinations and sources via GET `/organization/{orgId}/destinations` and GET `/organization/{orgId}/sources.` Write operations such as POST /endpoint to send a message or POST /query are excluded unless you explicitly add them.