canonical: https://jentic.com/apis/redeal.io/redeal-analytics-api

# Redeal Analytics API

Access analytics for Redeal. The API exposes 1 endpoints.

## For AI agents

Programmatically get events for analytics. Covers 1 operations.

## Scope

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

## Capabilities

- get events for analytics
- Manage analytics data programmatically
- Integrate Redeal Analytics API into automated workflows
- Query and filter Redeal Analytics API records by parameters
- Monitor Redeal Analytics API operational status and events

## Use cases

### Analytics Operations

Use the Redeal Analytics API to perform analytics operations programmatically. The API provides 1 endpoints covering core functionality including get events for analytics.

Example prompt: Call GET /events to get events for analytics

### Data Retrieval and Monitoring

Query Redeal Analytics API resources on a schedule to track changes, generate alerts, or feed downstream dashboards. Agents poll relevant endpoints, compare against previous state, and trigger actions when thresholds are crossed.

Example prompt: Poll the primary Redeal Analytics API endpoint, compare response to last known state, and alert if changed

### AI Agent Integration via Jentic

AI agents discover and call Redeal Analytics 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 none tokens manually.

Example prompt: Search Jentic for 'get events for analytics', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/events` | get events for analytics |

## Key resources

- **developers** — Operations available to regular developers

## Why Jentic

- **Setup:** Wiring the Redeal Analytics API by hand means pointing requests at its analytics.redeal.io host and calling its events endpoint yourself. Through Jentic you install once, import the Redeal Analytics API from the API Directory, and your agent calls it.
- **Permission scoping:** The Redeal Analytics API exposes a single read-only events lookup, so limit the agent to the operations it needs, such as reading events. You choose that set, so nothing beyond the operations you allow is available to the agent.
- **Credential handling:** Any credential this Redeal Analytics API needs 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 analytics events', and Jentic returns the matching Redeal Analytics operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Mixpanel** — Alternative analytics API
- **Amplitude** — Alternative analytics API
- **Segment** — Complementary analytics API
- **Pendo** — Complementary analytics API

## FAQ

### What authentication does the Redeal Analytics API use?

The Redeal Analytics API uses no authentication. 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 get events for analytics with the Redeal Analytics API?

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

### What are the rate limits for the Redeal Analytics 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 get events for analytics through Jentic?

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

### How many endpoints does the Redeal Analytics API have?

The Redeal Analytics API exposes 1 endpoints covering developers operations.

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

Yes. The Redeal Analytics API exposes a single read-only events lookup (GET /events), and because Jentic One is self-hosted, your own rules decide which operations the agent may call. You can restrict the agent to just reading events, so nothing beyond the operations you allow is available to it. Credentials are held by your own instance and injected only at execution time, never entering the agent's context.