Buy Me a Coffee API

Name: Buy Me a Coffee API API
Brand: Buy Me a Coffee API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentPaymentsBilling Subscriptionsbearer6 EndpointsREST

For Agents

Read Buy Me a Coffee supporters, members, and extras for a creator account. Authenticate with a Bearer personal access token.

Quickstart

Get started with Buy Me a Coffee 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:
"list buymeacoffee supporters"

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

Capabilities

What an agent can do with Buy Me a Coffee API API.

List one-time supporters and the amounts they tipped

Look up an individual supporter by ID

List active members and their subscription tiers

Retrieve a single subscription record by ID

List extras purchases such as digital products

GET STARTED

Start building with Buy Me a Coffee API API

Explore with Jentic

View OpenAPI Document

Use for: I need to list supporters who tipped me this month, Retrieve the details of a specific supporter by ID, Get all active members of my Buy Me a Coffee page, Find the subscription tier for a particular member

Not supported: Does not create or update supporters, accept payments directly, or manage page content — use for read-only access to supporters, subscriptions, and extras only.

Jentic publishes the only available OpenAPI document for Buy Me a Coffee API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for Buy Me a Coffee API, keeping it validated and agent-ready. Buy Me a Coffee is a creator support platform where supporters tip, subscribe to memberships, and purchase extras. This read-only API surface exposes supporters, subscriptions (members), and extras data so creators can sync activity into dashboards, CRMs, or personal websites. Authentication uses a Bearer personal access token from the developer settings.

Use Cases

Patterns agents use Buy Me a Coffee API API for, with concrete tasks.

★ Creator Dashboard Sync

Pull supporter, member, and extras data into a personal dashboard or website widget. Independent creators use this to display recent supporters, total tips, or member counts in real time. A simple polling job every few minutes is sufficient since the data is read-only and modest in volume.

Fetch /supporters, sum the amounts, and write a 'this month tipped' figure to a static JSON file rendered on the creator's homepage

Supporter CRM Sync

Push supporters into a CRM or email tool so creators can send thank-you messages, member-only updates, or product launches. Useful for creators with paid memberships who want to segment supporters by tier or contribution amount.

List subscriptions, identify members on the highest tier, and add them as contacts in the CRM with a 'top-tier-supporter' tag

Extras Sales Reporting

Track sales of extras (digital products, commissioned work, or one-off offerings) by listing /extras and aggregating by date or item. Creators selling digital downloads or services use this to understand what is converting and to reconcile fulfillment.

Fetch /extras for the last 30 days, group purchases by item, and post a sales summary to a Slack channel

AI Agent Creator Operations

Through Jentic, an AI agent can read Buy Me a Coffee data on a creator's behalf — pulling supporters, drafting thank-you messages, and reporting on member churn. Useful for solo creators who want to delegate routine reporting to an assistant.

Search Jentic for 'list buymeacoffee supporters', load the schema for GET /supporters, and execute, then summarise the top three supporters by amount

Key Endpoints

6 endpoints — jentic publishes the only available openapi specification for buy me a coffee api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/supporters

List supporters

GET

/supporters/{id}

Retrieve a single supporter

GET

/subscriptions

List members (subscriptions)

GET

/subscriptions/{id}

Retrieve a single subscription

GET

/extras

List extras purchases

GET

/extras/{id}

Retrieve a single extras purchase

GET

/supporters

List supporters

GET

/supporters/{id}

Retrieve a single supporter

GET

/subscriptions

List members (subscriptions)

GET

/subscriptions/{id}

Retrieve a single subscription

GET

/extras

List extras purchases

GET

Why though Jentic?

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

Credential isolation

Buy Me a Coffee personal access tokens are stored encrypted in the Jentic vault. Agents receive a scoped token at execution time — raw tokens never enter the agent's context window.

Intent-based discovery

Agents search by intent (e.g., 'list buymeacoffee supporters') and Jentic returns the matching read operation with its input schema.

Time to first call

Direct Buy Me a Coffee integration: a few hours for auth and pagination handling. Through Jentic: under 30 minutes for the first working call.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Patreon

Membership platform with broader tier management and content gating

Choose Patreon when richer membership tiers and content delivery matter; Buy Me a Coffee is simpler and tip-led

Alternative

Gumroad

Creator commerce platform for digital products and subscriptions

Use Gumroad when selling digital products is the primary use case rather than tipping

Complementary

MailerLite

Email platform to thank supporters and run member-only sends

Pair with Buy Me a Coffee to email supporters at scale

Complementary

ConvertKit (Kit)

Creator-focused email platform with automations

Use alongside Buy Me a Coffee to run welcome and thank-you sequences for new supporters

FAQs

Specific to using Buy Me a Coffee API API through Jentic.

Why is there no official OpenAPI spec for Buy Me a Coffee API?

Buy Me a Coffee does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Buy Me a Coffee 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 Buy Me a Coffee API use?

Buy Me a Coffee uses a Bearer personal access token, generated from the developer settings on the creator's account. Through Jentic, the token is stored in the encrypted vault and never enters the agent's context.

Can I list members of my Buy Me a Coffee page?

Yes. GET /subscriptions returns active members with their tier and metadata; GET /subscriptions/{id} retrieves a single member record.

What are the rate limits for the Buy Me a Coffee API?

Buy Me a Coffee does not publish hard rate limits in the spec. The API is read-only and returns modest volumes per creator, so polling every few minutes is reasonable; back off on 429 responses if they appear.

How do I retrieve supporters through Jentic?

Run pip install jentic, then search Jentic with the query 'list buymeacoffee supporters', load the schema for GET /supporters, and execute. The response includes supporter name, amount, and message.

Can I create or update records with this API?

No. The available endpoints are read-only — they expose supporters, subscriptions, and extras but do not provide write operations. Use the Buy Me a Coffee dashboard for content and product management.