FastSpring API

Name: FastSpring API
Brand: FastSpring API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentPaymentsBilling Subscriptionsbasic60 EndpointsREST

For Agents

Manage products, subscriptions, orders, quotes, coupons, accounts, and webhook events on a FastSpring merchant-of-record store.

Install Jentic One Beta

Connect the FastSpring API to your agent

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

Create and update product entries used by FastSpring storefronts and checkout sessions

Manage subscription lifecycle including pause, resume, and cancellation through dedicated subscription endpoints

Retrieve order history with filters by date range, product path, and return status

GET STARTED

Start building with FastSpring API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use FastSpring API for, with concrete tasks.

★ Subscription Lifecycle Automation for SaaS

SaaS vendors using FastSpring as merchant of record automate pause, resume, and cancellation flows from in-product self-service screens. The API exposes subscription endpoints that map to the product UI, so the front-end calls Jentic which calls FastSpring without the SaaS team handling card data. Cuts support tickets for billing changes and keeps tax compliance with FastSpring.

GET /accounts/{account_id} to confirm the customer, then call the subscription pause endpoint with the subscription id when the user clicks pause

Order Reconciliation and Reporting

Finance teams reconcile FastSpring revenue by pulling orders with date and product filters from /orders. The query parameters support begin and end date ranges plus product paths, so reports can be sliced by SKU per period. Replaces brittle export scripts with a structured API pull.

Call GET /orders with begin and end date parameters covering the prior month and aggregate revenue by product path

Coupon Campaign Management

Marketing teams launch and revoke coupon campaigns against FastSpring without UI work by calling /coupons and /coupons/{coupon_id}/codes. The agent can issue a campaign, generate codes, and revoke them when the promo ends. Useful for time-boxed promotions where speed and auditability matter.

POST /coupons to create a campaign, then DELETE /coupons/{coupon_id}/codes when the promotion window closes

Webhook Replay for Reliable Integrations

Engineering teams use /events/processed and /events/unprocessed to retrieve webhook event history when their listener missed deliveries or needs to backfill state. The endpoints turn FastSpring webhooks into a pull-based source-of-truth that the integration can replay against. Critical for systems that cannot tolerate missed billing events.

GET /events/unprocessed to fetch missed webhook events, replay each through the local handler, then POST /events/{event_id} to mark as processed

AI Billing Assistant via Jentic

Conversational billing agents use Jentic to call FastSpring on behalf of operations and CX teams. The agent searches 'pause a subscription' and Jentic returns the right operation with input schema. Basic-auth credentials live in the vault, so the agent does not handle secrets and integrations ship in under an hour rather than a week.

Through Jentic, search 'pause a subscription on fastspring', load the operation, and execute with the subscription id parsed from the support ticket

Key Endpoints

60 endpoints — the fastspring api is the merchant-of-record platform's backend for managing products, subscriptions, orders, quotes, accounts, coupons, returns, and webhooks.

METHOD

PATH

DESCRIPTION

GET

/orders/{order_id}

Retrieve a single order

POST

/accounts

Create a customer account

GET

/accounts/{account_id}

Retrieve a customer account

POST

/coupons

Create a coupon campaign

GET

/events/unprocessed

List unprocessed webhook events

POST

/events/{event_id}

Mark a webhook event as processed

GET

/orders/{order_id}

Retrieve a single order

POST

/accounts

Create a customer account

GET

/accounts/{account_id}

Retrieve a customer account

POST

/coupons

Create a coupon campaign

GET

/events/unprocessed

List unprocessed webhook events

Why Jentic?

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

Credential isolation

FastSpring basic-auth credentials are stored encrypted in the Jentic vault. Agents receive scoped execution access — the raw username and password never enter prompts or logs.

Intent-based discovery

Agents search by intent (e.g. 'pause a subscription on fastspring') and Jentic returns the matching operation with its input schema, so the agent can act without browsing the 60-endpoint surface.

Time to first call

Direct integration: 3-5 days across auth, the breadth of endpoints, webhook reconciliation, and error handling. Through Jentic: under an hour per intent — search, load, execute.

FAQs

Specific to using FastSpring API through Jentic.

What authentication does the FastSpring API use?

FastSpring uses HTTP Basic authentication — supply your API username and password in the Authorization header. Through Jentic both halves of the basic-auth credential live in the vault and are injected at execution time.

Can I manage subscriptions with the FastSpring API?

Yes. The API exposes subscription endpoints for pausing, resuming, and cancelling, alongside /accounts/{account_id} to identify the customer. Pair with /events to react to subscription state changes asynchronously.

What are the rate limits for the FastSpring API?

FastSpring does not document explicit rate limits in the spec. Plan for moderate concurrency, paginate /orders and /events queries with reasonable page sizes, and back off on 429 responses.

How do I replay missed webhook events through Jentic?

Install with pip install jentic, search 'list unprocessed fastspring events', load GET /events/unprocessed, replay each event in your local handler, then POST /events/{event_id} to mark each processed. Sign up at https://app.jentic.com/sign-up.

Does FastSpring handle tax compliance for me?

Yes. FastSpring acts as merchant of record, so global tax calculation, collection, and remittance are handled on their side. The API endpoints expose order and account data — the tax handling is a property of the platform, not a separate endpoint to call.

FastSpring API

Connect the FastSpring API to your agent

Capabilities

Start building with FastSpring API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs