Action Network API

Name: Action Network API
Brand: Action Network API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentMarketingMarketing AutomationapiKey52 EndpointsREST

For Agents

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

Install Jentic One Beta

Connect the Action Network API to your agent

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

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

GET STARTED

Start building with Action Network API

Explore with Jentic

View OpenAPI Document

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.

Use Cases

Patterns agents use Action Network API for, with concrete tasks.

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

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.

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.

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 the Jentic vault rather than passed through prompts.

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

Key Endpoints

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

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

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

Why Jentic?

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

Credential isolation

OSDI-API-Token values are stored encrypted in the Jentic vault per group. Agents receive scoped execution handles, so raw tokens never appear in prompt context or logs.

Intent-based discovery

Agents search Jentic by intent, e.g. 'add a supporter' or 'create a petition', and Jentic returns the matching Action Network operation with its input schema.

Time to first call

Direct Action Network integration: 1-2 days for auth, OSDI hypermedia handling, and tagging logic. Through Jentic: under 1 hour.

FAQs

Specific to using Action Network API through Jentic.

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 at https://app.jentic.com/sign-up.

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 the Jentic vault 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.

Action Network API

Connect the Action Network API to your agent

Capabilities

Start building with Action Network API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs