Goody API

Name: Goody API API
Brand: Goody API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentE CommerceOrder Managementbearer9 EndpointsREST

For Agents

Send personalised gifts at scale by creating orders or batches, browsing the Goody product catalog, and managing recipients through 9 endpoints.

Quickstart

Get started with Goody API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"send a goody gift to a customer"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Goody API API.

Create a gift order for one recipient with a chosen Goody product

Send a batch order to many recipients in one API call

Cancel an order before it has been redeemed by the recipient

List Goody products and read full product details before sending

Look up recipient records and their order history

GET STARTED

Start building with Goody API API

Explore with Jentic

View OpenAPI Document

Use for: Send a Goody gift to a prospect after a discovery call, I want to create a batch gift order for 200 customers in our Q2 retention campaign, List all available Goody products under £50, Get the details for a specific Goody product before sending it

Not supported: Does not handle physical-good fulfilment outside the Goody catalog, gift card balance management, or marketing email campaigns — use for Goody single and batch gift orders, product browsing, and recipient lookup only.

Jentic publishes the only available OpenAPI document for Goody API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for Goody API, keeping it validated and agent-ready. The Goody API provides 9 endpoints for sending personalised gifts at scale, covering orders, batches, recipients, and the Goody product catalog. It supports single-recipient gift orders, multi-recipient batch orders, order cancellation, and product browsing so businesses can run programmatic gifting for sales, recruiting, and customer success use cases. Authentication is a bearer token issued from the Goody dashboard.

Use Cases

Patterns agents use Goody API API for, with concrete tasks.

★ Sales Prospect Gifting

Sales teams trigger personalised gifts after discovery calls or stage changes. POST /orders creates a single-recipient order with a chosen product and message, and Goody handles redemption — recipients pick a swap if the gift does not suit them, which avoids delivery friction.

Create a gift order for prod_coffee_sampler to prospect@example.com after the deal stage moves to 'Discovery Complete'.

Customer Retention Batch Gifting

Customer success teams send a single batch gift order to dozens or hundreds of customers around renewals, milestones, or apologies. POST /batches accepts the recipient list and one product so finance gets one charge and ops gets one job to monitor.

Create a batch gift order with prod_curated_box for the 200 enterprise customers whose renewal is in 90 days.

Recruiting Welcome Gifts

People teams send welcome gifts to new hires on their start date by automating POST /orders from the HR system. Goody schedules delivery so the gift lands when the new hire is most likely to share it, which boosts day-one sentiment.

On a new hire's start date, create a Goody order with prod_welcome_kit to their personal email.

AI Agent Gifting Step via Jentic

An AI agent that handles customer follow-up adds personalised gifting as a step by calling Goody through Jentic. The agent searches for the right operation, loads the order schema, and executes with the bearer token held in the vault — no manual REST plumbing or product-ID hunting in the docs.

When a CSAT score of 9+ comes in, search Goody for products under $40, pick one, and send the gift to the customer.

Key Endpoints

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

METHOD

PATH

DESCRIPTION

GET

/orders

List orders

POST

/orders

Create an order

GET

/orders/{orderId}

Get an order

PATCH

/orders/{orderId}

Update an order

POST

/orders/{orderId}/cancel

Cancel an order

GET

/products

List products

POST

/batches

Create a batch order

GET

/orders

List orders

POST

/orders

Create an order

GET

/orders/{orderId}

Get an order

PATCH

/orders/{orderId}

Update an order

POST

/orders/{orderId}/cancel

Cancel an order

GET

/products

List products

Why though Jentic?

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

Credential isolation

Goody bearer tokens are stored encrypted in the Jentic vault (MAXsystem) and scoped to a single Goody workspace. Agents receive a short-lived execution handle, so the raw token never enters the model context or logs.

Intent-based discovery

Agents search Jentic by intent (e.g. 'send a goody gift to a customer') and Jentic returns the matching POST /orders or POST /batches operation with its input schema.

Time to first call

Direct Goody integration: 1 day for auth, product lookup, and error handling. Through Jentic: under 30 minutes — search, load, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Giftogram

Digital gift card platform aimed at the same incentive and recognition use cases.

Choose Giftogram when the recipient should pick a digital gift card from many brands rather than a physical curated gift.

Complementary

Stripe

Provides the underlying card or invoice payment that funds Goody orders at scale.

Pair when the agent needs to also charge the customer or reconcile gifting spend in finance.

Complementary

Salesforce REST API

Source of the contact and stage-change events that drive sales gifting.

Use alongside Goody when gifting is triggered by Salesforce opportunity stage changes.

FAQs

Specific to using Goody API API through Jentic.

Why is there no official OpenAPI spec for Goody API?

Goody does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Goody API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Goody API use?

Goody uses bearer token authentication on the Authorization header. Tokens are issued from the Goody dashboard and scoped to one workspace. Through Jentic the token is held in the encrypted vault and never enters the agent's context.

Can I send gifts to many recipients in one call?

Yes. POST /batches accepts a list of recipients and a single product so finance is charged once and you only need to monitor one batch ID. POST /orders is the right choice when each recipient gets a different product or message.

What are the rate limits for the Goody API?

Goody applies per-workspace rate limits documented at ongoody.com/help. The OpenAPI spec does not encode exact numbers, so check Goody support before running batch sends to thousands of recipients — for those, POST /batches is preferable to a loop of POST /orders.

How do I send a personalised gift through Jentic?

Search Jentic for 'send a goody gift', load the schema for POST /orders, and execute with the recipient and product ID. Jentic injects the bearer token at execution so the agent only handles the gift contents and recipient details.

Can I cancel a gift after sending it?

Yes, until the recipient redeems it. POST /orders/{orderId}/cancel cancels an unredeemed order and refunds the workspace, but once the recipient has accepted the gift the cancellation will fail and the order is final.