canonical: https://jentic.com/apis/testflight.tremendous.com/testflight-tremendous

# Testflight Tremendous API Endpoints

Deliver monetary rewards and incentives to employees, customers, survey participants, and more through the Tremendous API. For organizational tasks, like managing your organization and it's members within Tremendous, please see the Tremendous Organizational API. The API exposes 36 endpoints secured with bearer authentication.

## For AI agents

Programmatically list rewards, retrieve single reward. Covers 36 operations with bearer authentication.

## Scope

Does not handle payments, communications, or crm - use for hr and recruiting only.

## Capabilities

- List rewards
- Retrieve single reward
- Generate a reward URL
- Resend reward
- Create order

## Use cases

### HR and Recruiting Operations

Use the API Endpoints to perform hr recruiting operations programmatically. The API provides 36 endpoints covering core functionality including list rewards, retrieve single reward, generate a reward url.

Example prompt: Call GET /rewards to list rewards

### Automated Invoices Management

Automate invoices operations by combining multiple API Endpoints endpoints. Agents can retrieve single reward and then generate a reward url in a single workflow.

Example prompt: Call GET /rewards/{id} to retrieve single reward, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call API Endpoints 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 'list rewards', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | /rewards | List rewards |
| GET | /rewards/{id} | Retrieve single reward |
| POST | /rewards/{id}/generate_link | Generate a reward URL |
| POST | /rewards/{id}/generate_embed_token | Generate a reward token |
| POST | /rewards/{id}/resend | Resend reward |
| POST | /orders | Create order |
| GET | /orders | List orders |
| GET | /orders/{id} | Retrieve order |

## Key resources

- **Invoices** — Operations related to Invoices
- **Rewards** — Operations related to Rewards
- **Orders** — Operations related to Orders
- **Webhooks** — Operations related to Webhooks
- **Organizations** — Operations related to Organizations

## Why Jentic

- **Setup:** Wiring the Tremendous API by hand means learning its bearer API-key auth and choosing the right sandbox testflight.tremendous.com or production www.tremendous.com host, then coding each reward and order call yourself. Through Jentic you install once, import the Tremendous API from the API Directory, store the API key once, and your agent calls it.
- **Permission scoping:** The Tremendous API puts the reward and order id in the URL path (/rewards/{id}, /orders/{id}), so a rule can pin your agent to one reward or order: it can read that record and nothing else. You choose the operations it may call, so generating a redemption link or resending a reward is not included unless you add it.
- **Credential handling:** Your Tremendous API key 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 'list rewards' or 'read an order', and Jentic returns the matching Tremendous API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Greenhouse** — Alternative hr recruiting API
- **Lever** — Alternative hr recruiting API
- **Workday** — Complementary hr recruiting API

## FAQ

### What authentication does the API Endpoints use?

The API Endpoints 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 list rewards with the API Endpoints?

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

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

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 list rewards through Jentic?

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

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

The API Endpoints exposes 36 endpoints covering invoices, rewards, orders operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which Tremendous operations and credentials the agent may use. Since the Tremendous API carries the reward or order id in the URL path (/rewards/{id}, /orders/{id}), you can pin the agent to a single reward or order so it only reads that record and nothing else. You also choose the operations it may call, so actions like generating a redemption link or resending a reward stay off limits until you add them.