Greenpeace Greenwire Public API
Community OpenAPI document · agent-readySocial MediaSocial Managementnone6 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Read public Greenpeace Greenwire data - list and fetch events, activist groups, and volunteer profiles by UUID for environmental campaign coordination.
Use for: List all upcoming Greenpeace Greenwire events, Retrieve the details of a specific Greenwire event by UUID, Find activist groups on Greenwire working on a campaign, Get the profile of a Greenwire volunteer by UUID
Not supported: Does not handle donations, petition signing, or member messaging - use for read-only access to public Greenwire events, groups, and volunteers only.
The Greenwire Public API exposes read-only data from Greenpeace's Greenwire community platform, where volunteers, activists, and groups coordinate on environmental campaigns worldwide. Agents can list and retrieve public events, activist groups, and volunteer profiles by UUID. The API is read-only and limited to public-facing community data, with no authentication required for the published endpoints.
Install Jentic One Beta
Connect the Greenwire Public API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Greenwire Public 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%2Fgreenpeace.org%2Fgreenpeace" | 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%2Fgreenpeace.org%2Fgreenpeace" | 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 Greenwire Public API.
List Greenwire public events with their UUIDs and metadata
Retrieve a single event's full record by UUID
List activist groups participating in Greenpeace campaigns
Fetch a specific group's profile by UUID for volunteer matching
List public volunteer profiles available on Greenwire
Retrieve a single volunteer's public profile by UUID
Use Cases
Patterns agents use Greenwire Public API for, with concrete tasks.
★ Campaign Event Aggregation
Pull a current list of Greenwire public events into a campaign dashboard or newsletter. The /events endpoint returns event metadata that can be filtered and rendered for supporters looking to attend a local action. Useful for climate organisations syndicating Greenpeace mobilisations alongside their own.
Call GET /events, then for each event call GET /events/{UUID} and assemble a JSON list of upcoming Greenpeace actions for the next 30 days.
Volunteer Group Discovery
Help supporters find an existing Greenwire group rather than start a new one. Agents call /groups to list public groups and /groups/{UUID} to fetch a specific group's details, supporting recommendations based on cause area or geography.
Call GET /groups, filter by a region keyword in the agent's query, and return the top three matching groups with their /groups/{UUID} profile details.
Volunteer Profile Lookup
Look up a volunteer's public profile by UUID - useful when reconciling Greenwire identifiers with a CRM or activist database. The /volunteers and /volunteers/{UUID} endpoints expose only fields the volunteer has chosen to make public.
Given a Greenwire volunteer UUID, call GET /volunteers/{UUID} and return the public profile fields for matching against a CRM record.
AI Agent Greenwire Integration
An AI assistant for an environmental NGO uses Jentic to surface Greenwire data on demand - answering questions like 'what Greenpeace events are happening this week?' without bespoke integration work. The agent searches Jentic for the right Greenwire operation, loads the schema, and executes the call.
Search Jentic for 'list greenpeace events', load the GET /events schema, execute the call, and summarise the next five upcoming events for the user.
Key Endpoints
6 endpoints — the greenwire public api exposes read-only data from greenpeace's greenwire community platform, where volunteers, activists, and groups coordinate on environmental campaigns worldwide.
METHOD
PATH
DESCRIPTION
GET
/events
List public Greenwire events
GET
/events/{UUID}
Retrieve a single event by UUID
GET
/groups
List activist groups on Greenwire
GET
/groups/{UUID}
Retrieve a single group by UUID
GET
/volunteers
List public volunteer profiles
GET
/volunteers/{UUID}
Retrieve a single volunteer profile by UUID
GET
/events
List public Greenwire events
GET
/events/{UUID}
Retrieve a single event by UUID
GET
/groups
List activist groups on Greenwire
GET
/groups/{UUID}
Retrieve a single group by UUID
GET
/volunteers
List public volunteer profiles
GET
/volunteers/{UUID}
Retrieve a single volunteer profile by UUID
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Greenwire Public API by hand means handling its unauthenticated public reads and mapping the events, groups, and volunteers endpoints yourself. Through Jentic you install once, import the Greenwire Public API from the API Directory, and your agent calls it.
Permission scoping
Greenwire Public is a read-only service, so limit the agent to the operations it needs, such as listing public events or looking up a group by its UUID. Every operation you allow only reads public data, and you leave out any you do not want the agent to call.
Credential isolation
Greenwire Public needs no credential for its public reads, and Jentic One executes the calls directly. No token enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'list upcoming public events' or 'find local volunteer groups', and Jentic returns the matching Greenwire 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 Greenwire Public API through Jentic.
What authentication does the Greenwire Public API use?
The published Greenwire endpoints in this spec are public read-only and do not declare a security scheme - calls to /events, /groups, and /volunteers can be made without an API key. Through Jentic, the calls are still routed via your Jentic One instance so any future credential changes can be applied centrally without updating agent code.
Can I list upcoming Greenpeace events with this API?
Yes. Call GET /events to retrieve the list of public Greenwire events, then GET /events/{UUID} for the full record on any specific event. The API does not provide a date filter directly - agents should sort the returned events by date client-side.
What are the rate limits for the Greenwire Public API?
The OpenAPI spec does not publish explicit rate limits. Treat the API as a community resource and back off on any 429 response. Jentic's executor surfaces non-2xx responses to the agent so retries can be handled in the workflow.
How do I retrieve a Greenwire volunteer profile through Jentic?
Search Jentic with the query 'get a Greenwire volunteer profile', load the GET /volunteers/{UUID} schema, then execute with the volunteer UUID. Only fields the volunteer has marked public will be returned.
Is the Greenwire Public API free to use?
Greenpeace publishes the Greenwire data as a public community resource. There is no published pricing or paid tier in the spec. Use it respectfully and within reasonable request volumes.
Can this API write or update Greenwire data?
No. All six endpoints in this spec are GET - there are no POST, PUT, PATCH, or DELETE operations. The API is read-only.
Can I limit what my agent is allowed to do with the Greenwire Public API?
Yes. Because you run Jentic One yourself, your own rules decide which Greenwire operations the agent may call, so you can allow only the reads it needs, such as GET /events to list public events or GET /groups/{UUID} to look up a group, and leave the rest out. The API is read-only, so every operation you enable only fetches public event, group, or volunteer data and none can write or change anything. Jentic One executes these unauthenticated public calls directly, so no credential ever reaches the agent's prompt or logs.
GET STARTED