Patreon API

Name: Patreon API
Brand: Patreon API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentSocial MediaSocial Managementoauth214 EndpointsREST

For Agents

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

Install Jentic One Beta

Connect the Patreon API to your agent

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

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

GET STARTED

Start building with Patreon API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Patreon API for, with concrete tasks.

★ 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.

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.

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.

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.

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

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

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

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

Why Jentic?

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

Credential isolation

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.

Intent-based discovery

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.

Time to first call

FAQs

Specific to using Patreon API through Jentic.

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.