Testflight Tremendous API Endpoints

Name: API Endpoints API
Brand: API Endpoints
Availability: InStock

★ Only Publicly Available OpenAPI DocumentHR recruitingEmployee Managementbearer36 EndpointsREST

For Agents

Programmatically list rewards, retrieve single reward. Covers 36 operations 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.

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 | sh

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 instance

Jentic 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

GET STARTED

Start building with API Endpoints API

Explore with Jentic

View OpenAPI Document

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

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

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.

Intent-based discovery

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.

Time to first call

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 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.

Testflight Tremendous API Endpoints

Connect the API Endpoints to your agent

Capabilities

Start building with API Endpoints API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs