Buy Me a Coffee API
Agent-ready OpenAPI document · curated by JenticPaymentsBilling Subscriptionsbearer6 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Read Buy Me a Coffee supporters, members, and extras for a creator account. Authenticate with a Bearer personal access token.
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 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.
Install Jentic One Beta
Connect the Buy Me a Coffee API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Buy Me a Coffee 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.
1
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%2Fbuymeacoffee.com%2Fbuymeacoffee" | sh2
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%2Fbuymeacoffee.com%2Fbuymeacoffee" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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 Buy Me a Coffee 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
Retrieve an individual extras purchase by ID
Use Cases
Patterns agents use Buy Me a Coffee 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
/extras/{id}
Retrieve a single extras purchase
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring Buy Me a Coffee by hand means generating a personal access token from the developer settings, learning its bearer auth, and writing your own pagination over the supporters, subscriptions, and extras lists. Through Jentic you install once, import the Buy Me a Coffee API from the API Directory, store the token once, and your agent calls it.
Permission scoping
Buy Me a Coffee puts the record id in the URL path (/supporters/{id}, /subscriptions/{id}, /extras/{id}), so you can pin your agent to specific records rather than the full account. Every operation on this surface is read-only, so you choose which of the supporter, subscription, and extras reads it may call and it can do nothing else.
Credential isolation
Your Buy Me a Coffee personal access 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 'list buymeacoffee supporters' or 'get my buymeacoffee members', and Jentic returns the matching read 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.
FAQs
Specific to using Buy Me a Coffee 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 with Jentic One, the self-hosted execution layer.
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.
Can I limit what my agent is allowed to do with the Buy Me a Coffee API?
Yes. Because you run Jentic One yourself, your own rules decide which operations and credentials the agent may use. Every operation on this API is read-only, so you can allow just the supporter, subscription, and extras reads it needs and deny the rest. Since the record id sits in the URL path (/supporters/{id}, /subscriptions/{id}, /extras/{id}), you can also pin the agent to specific records rather than the full account.
GET STARTED