Testflight Tremendous API Endpoints
★ Only Publicly Available OpenAPI DocumentHR recruitingEmployee Managementbearer36 EndpointsREST
For Agents
Programmatically list rewards, retrieve single reward. Covers 36 operations with bearer authentication.
Use for: I need to rewards, I want to single reward, Search for generate a reward url, Find all generate a reward token
Not supported: Does not handle payments, communications, or crm — use for hr and recruiting only.
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.
Install Jentic One Beta
Connect the API Endpoints to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the API Endpoints, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with API Endpoints API.
List rewards
Retrieve single reward
Generate a reward URL
Resend reward
Create order
Use Cases
Patterns agents use API Endpoints API for, with concrete tasks.
★ 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.
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.
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.
Search Jentic for 'list rewards', load the operation schema, and execute with Jentic-managed credentials
Key Endpoints
36 endpoints — deliver monetary rewards and incentives to employees, customers, survey participants, and more through the tremendous api.
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
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
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
API Endpoints bearer credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw secrets never enter the agent context.
Intent-based discovery
Agents search by intent (e.g., 'list rewards') and Jentic returns the matching API Endpoints operation with its input schema, so the agent can call the right endpoint without browsing docs.
Time to first call
Direct API Endpoints integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using API Endpoints API through Jentic.
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 the MAXsystem vault 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 at https://app.jentic.com/sign-up, 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.
GET STARTED