API and Integrations

The HelpOut REST API — getting your API key, authenticating, and reading your events and responses programmatically.

The HelpOut API

HelpOut has a read-only REST API available to every account. Use it to pull your events and responses into a spreadsheet, a dashboard, a website, or anything else you build.

Full endpoint reference: helpout.us/developer.

Getting Your API Key

  1. Sign in at helpout.us.
  2. Go to Profile > API, or open helpout.us/users/api.
  3. Click Copy to copy your key.
Your API key gives access to everything in your account, including the names and email addresses of everyone who responded to your events. Treat it like a password — don’t put it in a public repository, a shared spreadsheet, or client-side code in a web page.

Authenticating

Every request needs your key in the X-API-Key header.

curl --header "X-API-Key: YOUR_API_KEY" https://helpout.us/api/v1/ping

Requests without a valid key return 401 Unauthorized.

Base URL

https://helpout.us/api/v1

Endpoints

Method Path Returns
GET /ping Your account’s email address — use it to verify a key works
GET /events Every event in your account, newest first
GET /events/:id A single event
GET /events/:event_id/responses Every response and contribution for an event

Events are addressed by their slug — the last part of the event’s web address. An event at helpout.us/events/walnut-grove-science-fair has the id walnut-grove-science-fair.

Events

curl --header "X-API-Key: YOUR_API_KEY" \
  https://helpout.us/api/v1/events

Each event includes its id, url, title, eventat, description (as plain text and as HTML), eventtype, location, owner, imageurl if a header image is attached, and timestamps. Gift It! events also include recipientname, recipient_email, and the contributions total.

Responses

curl --header "X-API-Key: YOUR_API_KEY" \
  https://helpout.us/api/v1/events/walnut-grove-science-fair/responses

Responses and contributions come back in one list, and the fields tell them apart:

  • Show Up! responses have quantity and rsvp
  • Bring It! and Sign Up! responses have quantity and a slots array; on Sign Up! events each slot carries start_date and end_date
  • Gift It! contributions have amount and processing_fee

All timestamps are UTC in ISO 8601 format.

Rate Limits

Endpoint Limit
/events and /events/:id/responses 100 requests per minute
/ping 10 requests per minute

Going over returns 429 Too Many Requests. If you’re syncing on a schedule, poll every few minutes rather than continuously — event data doesn’t change that fast.

Scope

The API is read-only. Events, responses, and contributions can’t be created or changed through it, and it only ever returns data from your own account.


Was this helpful?