Greenwire Public API

Name: Greenwire Public API API
Brand: Greenwire Public API
Availability: InStock

★ Only Publicly Available SpecSocial MediaSocial Managementnone6 EndpointsREST

For Agents

Read public Greenpeace Greenwire data — list and fetch events, activist groups, and volunteer profiles by UUID for environmental campaign coordination.

Quickstart

Get started with Greenwire Public API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"list greenpeace events on greenwire"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Greenwire Public API 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

GET STARTED

Start building with Greenwire Public API API

Explore with Jentic

View OpenAPI Spec

Jentic publishes the only available OpenAPI specification for Greenwire Public API, keeping it validated and agent-ready.

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.

Use Cases

Patterns agents use Greenwire Public API 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

Why though Jentic?

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

Credential isolation

The Greenwire Public API does not require credentials for these endpoints. Jentic still routes the call through the MAXsystem so that, if Greenpeace introduces auth in the future, agents do not need code changes — only the vault entry updates.

Intent-based discovery

Agents search Jentic with intents like 'list greenpeace events' and Jentic returns the matching Greenwire operation with its input schema, so the agent can call the right endpoint without browsing Greenpeace docs.

Time to first call

Direct integration: a few hours to read the spec, wire HTTP calls, and handle pagination. Through Jentic: minutes — search for the operation, load its schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Meetup API

General-purpose event and group platform — pair with Greenwire when an agent needs broader event coverage beyond Greenpeace.

Choose Meetup when the user wants any local environmental event, not just Greenpeace-organised ones.

Complementary

Mailchimp Marketing API

Email marketing platform — combine with Greenwire to push event lists to a supporter newsletter.

Use Mailchimp when the agent has Greenwire event data and needs to send it to a campaign audience.

Complementary

HubSpot CRM Contacts

CRM for matching Greenwire volunteer UUIDs to existing supporter records.

Choose HubSpot when reconciling a Greenwire volunteer with a CRM contact rather than working only inside Greenwire.

FAQs

Specific to using Greenwire Public API 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 the MAXsystem 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.