canonical: https://jentic.com/apis/actionnetwork.org/actionnetwork

# Action Network API

Jentic publishes the only available OpenAPI specification for Action Network API, keeping it validated and agent-ready. Action Network is a progressive organising platform built on the OSDI standard, exposing endpoints to manage people, petitions, events, fundraising pages, forms, tags, and broadcast messages. The API uses a per-group OSDI-API-Token header for authentication and follows hypermedia conventions, with collections under /api/v2/. The spec covers 52 operations across nine resource groups including campaigns, wrappers, and messages.

## For AI agents

Manage progressive organising work - sign-ups, petitions, events, donations, and broadcast messages - through Action Network's OSDI-compliant API.

## Scope

Does not handle voter file management, peer-to-peer texting platforms, or paid advertising - use for OSDI-compliant supporter, petition, event, and fundraising data only.

## Capabilities

- Create and update people records and apply tags through /api/v2/people and /api/v2/tags
- Publish petitions and read signature counts via /api/v2/petitions and /api/v2/petitions/{id}
- Create events and accept RSVPs through /api/v2/events and its attendances sub-resource
- Run fundraising pages and pull donation records via /api/v2/fundraising_pages
- Send broadcast email and SMS messages with /api/v2/messages
- Build sign-up forms and capture submissions through /api/v2/forms
- Group activity into campaigns and reuse layouts via /api/v2/wrappers

## Use cases

### Supporter onboarding and tagging

Progressive campaigns onboard new supporters from rallies, sign-up sheets, and partner lists. An agent can call POST /api/v2/people to add each supporter, then POST /api/v2/tags and the people-tags taggings sub-resource to segment them by issue or geography. Action Network's OSDI design means tag-based segments stay in sync across petitions, events, and email blasts without re-uploading lists.

Example prompt: POST a new person to /api/v2/people with email and zip, then attach the 'climate-volunteer' tag through the taggings sub-resource

### Event RSVP automation

Field organisers create dozens of events per week and need RSVP data flowing into their CRM. An agent can create the event with POST /api/v2/events, expose the RSVP page, and then GET /api/v2/events/{id}/attendances to pull RSVPs back. Pair this with tag updates so attendees get re-targeted for follow-up phone banks.

Example prompt: Create an event at /api/v2/events for next Saturday, then list attendances after 24 hours and tag attendees as 'rally-attended'

### Petition and fundraising sync

Campaigns run petitions and fundraising in parallel, often promoting the petition to drive donations. An agent can publish the petition with POST /api/v2/petitions, set up the fundraising page via POST /api/v2/fundraising_pages, and report aggregate signatures and donation totals daily. Both feed the same OSDI people graph, so the same supporter is tracked across actions.

Example prompt: List signatures on petition 789, list donations on fundraising_page 456, and produce a daily summary

### AI agent integration

Campaigns building agent assistants for their organising team use Jentic to expose Action Network alongside SMS and email-marketing APIs. Through Jentic, the agent searches by intent, e.g. 'add a supporter to Action Network', and the OSDI-API-Token is held in your Jentic One instance rather than passed through prompts.

Example prompt: Search Jentic for 'add a person to Action Network', load the schema, and execute it with email and zip code

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | /api/v2/people | Add a supporter |
| GET | /api/v2/people | List supporters |
| POST | /api/v2/petitions | Create a petition |
| POST | /api/v2/events | Create an event |
| POST | /api/v2/fundraising_pages | Create a fundraising page |
| POST | /api/v2/tags | Create a tag |
| POST | /api/v2/messages | Send a broadcast message |
| GET | /api/v2/forms | List forms |

## Key resources

- **People** — Create, update, and tag supporter records
- **Petitions** — Publish petitions and read signatures
- **Events** — Create events and pull RSVPs
- **Fundraising Pages** — Run fundraising pages and pull donation records
- **Forms** — Build sign-up forms and capture submissions
- **Tags** — Segment supporters across all actions
- **Messages** — Send broadcast email and SMS
- **Campaigns** — Group related actions into campaigns
- **Wrappers** — Reusable header and footer layouts for actions

## Why Jentic

- **Setup:** Wiring the Action Network API by hand means attaching the OSDI-API-Token header per group and mapping intents onto OSDI-compliant people, petition, and event resources yourself. Through Jentic you install once, import the Action Network API from the API Directory, store the OSDI-API-Token once, and your agent calls it.
- **Permission scoping:** These endpoints take supporter, petition, and event details in the request body rather than a resource id in the URL, so limit the agent to the operations it needs, such as adding a supporter or creating a petition. You choose the operations it may call, so creating fundraising pages or sending messages is not included unless you add them.
- **Credential handling:** Your OSDI-API-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.
- **Discovery method:** Agents search Jentic by intent such as 'add a supporter' or 'create a petition', and Jentic returns the matching Action Network operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Mailchimp API** — Pair Action Network supporter lists with Mailchimp's email design and deliverability tooling.
- **Donorbox API** — Run dedicated donation pages alongside Action Network campaigns.

## FAQ

### Why is there no official OpenAPI spec for Action Network API?

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

Action Network uses a per-group API key passed in the OSDI-API-Token header. Each Action Network group issues its own token, so you scope access by group. Through Jentic, the OSDI-API-Token is held in your Jentic One instance and the agent receives a scoped execution handle rather than the raw token.

### Can I add supporters and tag them with the Action Network API?

Yes. POST a new supporter to /api/v2/people with email, postal code, and any custom fields. Tags live as their own resource at /api/v2/tags, and you attach them via the taggings sub-resource on a person. The same tag can then be used to filter audiences for messages, events, and fundraising.

### What are the rate limits for the Action Network API?

The OpenAPI spec does not declare rate limits, so consult Action Network's developer docs for the current ceiling. Bulk imports should be paged through the OSDI hypermedia next links rather than parallelised aggressively, and 429 responses should be retried with exponential backoff.

### How do I create an event with the Action Network API through Jentic?

Run pip install jentic, search Jentic for 'create an Action Network event', load the schema for POST /api/v2/events, and execute it with a title, start_date, and location. Jentic injects the OSDI-API-Token from the vault, so the agent only supplies event details.

### Does the Action Network API follow the OSDI standard?

Yes. Action Network is one of the reference implementations of the Open Supporter Data Interface, so endpoints under /api/v2/ use OSDI naming and hypermedia conventions. That makes it easier to portfolio-match an integration across other OSDI-compliant tools.

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

Yes. Jentic One is self-hosted by you, and your own rules decide which Action Network operations and credentials the agent may use. Because these endpoints take supporter, petition, and event details in the request body rather than a resource id in the URL, you scope the agent to only the operations it needs, such as adding a supporter to /api/v2/people or creating a petition at /api/v2/petitions. You choose the operations it may call, so creating fundraising pages or sending broadcast messages stays excluded unless you add them.