How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Tremendous Orders API

Create and manage reward orders

Tremendous Orders API is one of 9 APIs that Tremendous publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Order. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, and a GitHub repository.

This API exposes 4 operations across 3 paths, and defines 5 schemas. It is described by OpenAPI 3.2.0, at version 2.0.

Requests are made against 2 base URLs: https://testflight.tremendous.com/api/v2, https://www.tremendous.com/api/v2.

4 operations 3 paths 5 schemas 2 GET2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2.0
Base URL
https://testflight.tremendous.com/api/v2
Authentication
HTTP Bearer, OAuth 2.0
License
Proprietary
Terms of Service
Resource Areas
1

Authentication & Security 2

Tremendous Orders API declares 2 security schemes for authenticating requests. It accepts HTTP bearer tokens (BearerAuth). It supports OAuth 2.0 (OAuth2) using the authorizationCode flow, exposing 3 scopes. By default, every request must be authenticated.

  • BearerAuth — Bearer token authentication using a Tremendous API key. Generate API keys in your Tremendous dashboard Settings API.
  • OAuth2 — OAuth 2.0 for third-party integrations

Paths & Operations 4

Across 3 paths, the API surfaces 4 operations — 2 GET, 2 POST. Each is listed below with its method, path, parameters, and response codes.

Orders 4

Create and manage reward orders

GET
/orders
List Orders
listOrders 4 params → 200401429
POST
/orders
Create Order
createOrder body → 200400401402409422429
GET
/orders/{id}
Get Order
getOrder 1 param → 200401404
POST
/orders/approve
Approve Order
approveOrder body → 200401404

Schemas 5

The contract defines 5 schemas that model the data the API accepts and returns. The most detailed are Reward (8 properties), Order (6 properties), RewardInput (6 properties), CreateOrderRequest (3 properties). Each schema is shown below with its type and property counts.

Recipient
object
3 properties 2 required
Reward
object
8 properties
RewardInput
object
6 properties
Order
object
6 properties
CreateOrderRequest
object
3 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

tremendous-orders-api-openapi.yml Raw ↑

Other APIs Tremendous publishes across the network.

Tremendous Campaigns API
Tremendous Funding Sources API
Tremendous Invoices API
Tremendous Members API
Tremendous Organizations API
Tremendous Products API
Tremendous Rewards API
Tremendous Webhooks API
Where this information came from

This is an independent, third-party profile of Tremendous Orders API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.