canonical: https://jentic.com/apis/patreon.com/patreon

# Patreon API

Jentic publishes the only available OpenAPI specification for Patreon API, keeping it validated and agent-ready. The Patreon API v2 provides programmatic access to the Patreon creator and membership platform, enabling management of campaigns, members, posts, and webhooks. It supports OAuth 2.0 authentication and offers 14 endpoints for retrieving creator identities, listing campaign members with pledge data, managing content posts, and configuring webhook subscriptions for real-time event notifications.

## For AI agents

Access Patreon campaign data, manage membership lists, retrieve post content, and configure webhooks for real-time pledge and membership event notifications.

## Scope

Does not handle payment processing, content hosting, or community chat - use for campaign data retrieval, membership management, and event webhooks only.

## Capabilities

- Retrieve authenticated creator identity and linked campaign information
- List campaign members with pledge amounts, tiers, and payment status
- Query individual member details including lifetime support totals
- Manage campaign posts including content, publish dates, and tier visibility
- Configure webhook endpoints for real-time pledge and membership events
- Access live stream metadata and scheduling information
- Retrieve campaign metadata including creation date, patron count, and earnings

## Use cases

### Membership and Pledge Management

Retrieve and monitor campaign membership data including pledge amounts, tier assignments, and payment status for each patron. The `/campaigns/{campaign_id}/members` endpoint returns paginated member lists with relationship data linking to pledge tiers. This enables automated patron management, tier-based access control, and membership analytics.

Example prompt: List all active members for campaign ID 'camp_123' via GET `/api/oauth2/v2/campaigns/{campaign_id}/members` and filter for currently_entitled_amount_cents greater than 0

### Content and Post Management

Access and manage campaign posts through the Patreon API. The posts endpoints return content including title, body, publish dates, and tier-specific visibility settings. This supports content syndication, automated publishing workflows, and cross-platform content distribution for creators.

Example prompt: Retrieve the 10 most recent posts for campaign 'camp_123' via GET `/api/oauth2/v2/campaigns/{campaign_id}/posts` and return titles with publish dates

### Webhook Event Integration

Configure webhook subscriptions to receive real-time notifications for Patreon events including new pledges, pledge updates, pledge deletions, and member updates. The /webhooks endpoint supports creating, retrieving, and managing webhook configurations with specific event triggers tied to campaigns.

Example prompt: Create a webhook subscription for campaign 'camp_123' via POST `/api/oauth2/v2/webhooks` targeting new pledge events at callback URL https://example.com/hooks/patreon

### AI Agent Creator Platform Integration

AI agents integrate with Patreon through Jentic to automate campaign management without handling OAuth token exchanges directly. Agents search for operations like 'list patreon campaign members' and Jentic returns the operation schema with parameter requirements, managing credential isolation and token refresh.

Example prompt: Search Jentic for 'list patreon campaign members', load the operation schema, and execute for a specific campaign ID to retrieve all active patrons

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/api/oauth2/v2/identity` | Get authenticated user identity |
| GET | `/api/oauth2/v2/campaigns` | List user campaigns |
| GET | `/api/oauth2/v2/campaigns/{campaign_id}/members` | List campaign members |
| GET | `/api/oauth2/v2/members/{member_id}` | Get member details |
| GET | `/api/oauth2/v2/campaigns/{campaign_id}/posts` | List campaign posts |
| POST | `/api/oauth2/v2/webhooks` | Create a webhook subscription |
| GET | `/api/oauth2/v2/webhooks` | List webhook subscriptions |

## Key resources

- **Identity** — Retrieve authenticated user profile and linked campaign data
- **Campaigns** — Access campaign metadata, patron counts, and earnings information
- **Members** — List and retrieve individual campaign members with pledge details
- **Posts** — Query campaign posts with content, dates, and tier visibility
- **Webhooks** — Create and manage webhook subscriptions for real-time events
- **Lives** — Access live stream metadata and scheduling

## Why Jentic

- **Setup:** Wiring Patreon by hand means running its OAuth 2.0 flow, managing access and refresh token rotation, and paging campaign, member, and post data yourself. Through Jentic you install once, import the Patreon API from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** Patreon puts the campaign id in the URL path (`/api/oauth2/v2/campaigns/{campaign_id}/members`), so a rule can pin your agent to one campaign: it can read that campaign's members and posts and nothing else. You choose the operations it may call, so webhook creation is not included unless you add it.
- **Credential handling:** Your Patreon OAuth tokens are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'list my Patreon campaign patrons' or 'get recent posts for a campaign', and Jentic returns the matching Patreon operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Buy Me a Coffee API** — Creator tipping and membership platform with simpler API surface
- **GoFundMe API** — Crowdfunding platform for campaigns and donations
- **Discord API** — Community chat platform often paired with Patreon for member perks

## FAQ

### Why is there no official OpenAPI spec for Patreon API?

Patreon does not publish an OpenAPI specification for their v2 API. Jentic generates and maintains this spec so that AI agents and developers can call Patreon 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 Patreon API use?

The Patreon API uses OAuth 2.0 with authorization code flow. Applications redirect users to Patreon for consent, then exchange the authorization code for access and refresh tokens. The API also supports creator access tokens for accessing your own campaign data. Through Jentic, OAuth tokens are stored in the credential vault with automatic refresh.

### Can I get pledge amounts for individual patrons?

Yes. The GET `/api/oauth2/v2/members/{member_id}` endpoint returns detailed member data including currently_entitled_amount_cents, lifetime_support_cents, patron_status, and the associated tier. You can also list all members via the campaign members endpoint with pledge data included.

### How do I set up webhooks for pledge notifications?

Create a webhook via POST `/api/oauth2/v2/webhooks` specifying the callback URL, campaign ID, and event triggers. Supported events include members:pledge:create, members:pledge:update, and members:pledge:delete. Patreon sends signed POST requests to your callback URL when events occur.

### How do I list campaign members through Jentic?

Search Jentic for 'list patreon campaign members', load the operation schema for GET `/api/oauth2/v2/campaigns/{campaign_id}/members`, and execute with your campaign ID. Jentic handles OAuth token injection. Install with pip install jentic.

### What data does the identity endpoint return?

GET `/api/oauth2/v2/identity` returns the authenticated user's profile including full name, email, image URL, and relationships to owned campaigns. Including the campaigns relationship returns linked campaign IDs which you can then query for members and posts.

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

Yes. Because you run Jentic One yourself, your own rules decide which Patreon operations and credentials the agent may use. Since the campaign id sits in the URL path (`/api/oauth2/v2/campaigns/{campaign_id}/members`), you can pin the agent to a single campaign so it only reads that campaign's members and posts. You also choose the exact operations it may call, so writing actions such as creating a webhook via POST `/api/oauth2/v2/webhooks` stay out of reach unless you explicitly allow them.