Sandbox Tripadd TripAdd API

Name: TripAdd API
Brand: TripAdd API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentE CommerceStorefrontbearer5 EndpointsREST

For Agents

Programmatically create bundle offer, get bundle offer. Covers 5 operations with bearer authentication.

Install Jentic One Beta

Connect the TripAdd API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the TripAdd API, 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://jentic.com/install.sh?src=apis&api=%2Fapis%2Fsandbox.tripadd.com%2Fsandbox-tripadd" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fsandbox.tripadd.com%2Fsandbox-tripadd" | 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 TripAdd API.

Create Bundle Offer

Get Bundle Offer

Cancel Order

Query and filter TripAdd API records by parameters

GET STARTED

Start building with TripAdd API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use TripAdd API for, with concrete tasks.

★ E-Commerce Operations

Use the TripAdd API to perform e commerce operations programmatically. The API provides 5 endpoints covering core functionality including create bundle offer, get bundle offer, create order.

Call POST /bundle_offers to create bundle offer

Automated Orders Management

Automate orders operations by combining multiple TripAdd API endpoints. Agents can get bundle offer and then create order in a single workflow.

Call GET /bundle_offers/{bundle_offer_id} to get bundle offer, then verify the result

AI Agent Integration via Jentic

AI agents discover and call TripAdd 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 bearer tokens manually.

Search Jentic for 'create bundle offer', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

5 endpoints — tripadd api enables you to create personalized travel ancillary product bundles and make orders.

METHOD

PATH

DESCRIPTION

POST

/bundle_offers

Create Bundle Offer

GET

/bundle_offers/{bundle_offer_id}

Get Bundle Offer

POST

/orders

Create Order

GET

/orders/{order_id}

Get Order

POST

/orders/{order_id}/cancel

Cancel Order

POST

/bundle_offers

Create Bundle Offer

GET

/bundle_offers/{bundle_offer_id}

Get Bundle Offer

POST

/orders

Create Order

GET

/orders/{order_id}

Get Order

POST

/orders/{order_id}/cancel

Cancel Order

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the TripAdd API by hand means learning its bearer auth, choosing the sandbox or production tripadd.com host, and handling bundle-offer and order retries yourself. Through Jentic you install once, import TripAdd from the API Directory, store the bearer token once, and your agent calls it.

Permission scoping

TripAdd puts the order and offer ids in the URL path (/orders/{order_id}, /bundle_offers/{bundle_offer_id}), so a rule can pin your agent to specific orders and offers: it can read the ones you allow and nothing else. You choose the operations it may call, so actions like cancelling an order are not included unless you add them.

Credential isolation

Your TripAdd bearer token 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 'create a bundle offer' or 'get an order', and Jentic returns the matching TripAdd operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Shopify

Alternative e commerce API

Choose Shopify when you need a different approach to e commerce operations

Alternative

Stripe

Alternative e commerce API

Choose Stripe when you need a different approach to e commerce operations

FAQs

Specific to using TripAdd API through Jentic.

What authentication does the TripAdd API use?

The TripAdd API 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 create bundle offer with the TripAdd API?

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

What are the rate limits for the TripAdd 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 create bundle offer through Jentic?

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

How many endpoints does the TripAdd API have?

The TripAdd API exposes 5 endpoints covering orders, bundle offers operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which TripAdd operations the agent may call and which bearer credentials it may use. Since order and offer ids sit in the URL path (/orders/{order_id}, /bundle_offers/{bundle_offer_id}), you can pin the agent to specific orders and offers so it reads only the ones you allow. You also choose the operations it can run, so an action like cancelling an order via POST /orders/{order_id}/cancel is not available to the agent unless you grant it.