AirGift API

Name: AirGift API
Brand: AirGift API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentMarketingMarketing AutomationapiKey2 EndpointsREST

For Agents

Send a digital gift to a recipient and check the delivery status, used in sales outreach, customer success, and incentive flows.

Install Jentic One Beta

Connect the AirGift API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the AirGift 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://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 AirGift API.

Send a branded digital gift to a recipient via POST /gifts

Retrieve the status of a previously sent gift via GET /gifts/{id}

Drive sales prospecting and customer success campaigns with personalised gifting

GET STARTED

Start building with AirGift API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use AirGift API for, with concrete tasks.

★ Sales Prospecting Gift Drops

Boost outbound response rates by attaching a small digital gift to high-priority prospect emails. POST /gifts sends the gift with the recipient email and amount, and the response includes a redemption link the rep can paste into the outreach sequence.

Send a $25 digital gift to prospect@example.com with the message 'Thanks for taking the meeting' and capture the redemption link in the CRM activity record

Customer Success Thank-You Workflow

Trigger a thank-you gift after a customer hits a milestone - first renewal, NPS promoter, case study contribution. The two-endpoint surface makes integration into a workflow tool a simple POST followed by an optional status poll for redemption confirmation.

Send a $50 gift to a customer who scored 9 or 10 on the latest NPS survey, then check the gift status 7 days later and flag any unredeemed gifts for follow-up

AI Agent Gifting Operator

An agent driving outreach can decide when to attach a gift, send it via Jentic, and capture the redemption link in the same flow. The Authorization API key stays in your Jentic One instance and only the two scoped operations are exposed.

Search Jentic for 'send a digital gift', load the POST /gifts schema, send a $20 gift to recipient@example.com, and store the returned gift ID in the CRM

Key Endpoints

2 endpoints — jentic publishes the only available openapi specification for airgift api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/gifts

Send a digital gift

GET

/gifts/{id}

Get gift details and status

POST

/gifts

Send a digital gift

GET

/gifts/{id}

Get gift details and status

Why Jentic?

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

Credential isolation

Your AirGift 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 'send a digital gift', and Jentic returns the AirGift /gifts 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 AirGift API through Jentic.

Why is there no official OpenAPI spec for AirGift API?

AirGift does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call AirGift API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

What authentication does the AirGift API use?

AirGift uses an API key passed in the Authorization header. Jentic stores the key encrypted in the vault and adds the header at call time, so the raw API key is never exposed to the agent.

Can I send a digital gift with the AirGift API?

Yes. POST /gifts accepts the recipient details, gift amount, and any personalised message and returns a gift ID and redemption URL the recipient can use to claim the gift.

What are the rate limits for the AirGift API?

The spec does not declare formal rate limits. With only two endpoints, AirGift is best used in burst-and-pause patterns from a workflow rather than tight loops; respect HTTP 429 responses if you hit them.

How do I check whether a gift was redeemed through the AirGift API via Jentic?

Run pip install jentic, search Jentic for 'check airgift status', load the schema for GET /gifts/{id}, then execute with the gift ID. The response contains the redemption state. Jentic applies the Authorization header automatically.

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

Yes. Because you run Jentic One yourself, your own rules decide which AirGift operations and credentials the agent can use. The AirGift API exposes just two operations, sending a digital gift with POST /gifts and reading its status with GET /gifts/{id}, so you can scope the agent to only the ones it needs. For example, you can allow it to check gift status while withholding the ability to send new gifts, and the API key stays with your instance rather than the agent.