Events API

The Events API lets your own tools put an event on the calendar and keep it current: create the event when it is booked in an external system, move a date when it shifts, search what is coming up, and read who has bought tickets. It shares everything with the Constituents API, the Volunteerism API and the Donations API — the same API keys, the same base URL, the same error shape.

Authentication

Use the same key you use for the other APIs (Subscription Settings → API Keys, team admins only), sent as a bearer token on every request:

Authorization: Bearer argenta_sk_...

The base URL is https://app.argentasoftware.com/api/v1. All requests and responses are JSON.

Endpoints

Create an event

curl -X POST "https://app.argentasoftware.com/api/v1/events" \
  -H "Authorization: Bearer argenta_sk_..." \
  -H "Content-Type: application/json" \
  -d '{
    "EventTitle": "Fall Gala 2026",
    "StartDate": "2026-10-17",
    "StartTime": "18:00",
    "EndDate": "2026-10-17",
    "EndTime": "22:00",
    "MaxGuests": 250,
    "ContactName": "Dana Whitfield",
    "ContactEmail": "[email protected]",
    "EventLocation": "Riverside Hall",
    "EventLocationCity": "Jacksonville",
    "EventLocationState": "FL"
  }'

You get 201 with {"created": true, "event": {...}}. Argenta builds the event exactly as the Add Event button does: the notification templates are seeded, your team's public form defaults are applied, and the event appears on the Events list immediately.

Update an event

Send only the fields that change. Everything you leave out is untouched.

curl -X PATCH "https://app.argentasoftware.com/api/v1/events/8814" \
  -H "Authorization: Bearer argenta_sk_..." \
  -H "Content-Type: application/json" \
  -d '{ "StartDate": "2026-10-24", "EndDate": "2026-10-24" }'

Event fields

Reads return more than you can write. Chapter, division, department, district and precinct come back on every event so you can see where it sits in your organization, but they are not writable through the API. Neither are the switches that publish an event or take money for it (IsPublic, IsTicketSales), the budget and attendance figures, the public form design, or the lock and view-only flags. Everything else an event carries in Argenta — sessions, guests and guest groups, seating, committees, checklists, itineraries, meal choices, financials and waitlists — is managed in-app.

Unknown fields are rejected with 400 unknown_field rather than ignored, so a typo can never silently drop data. A locked or view-only event returns 403 on a write and still reads normally.

Reading ticket sales

curl "https://app.argentasoftware.com/api/v1/event-tickets?eventId=8814&isPaidInFull=true" \
  -H "Authorization: Bearer argenta_sk_..."

Each row carries the purchaser, the ticket type and quantity, the gross paid, merchant fees, net revenue and the tax-deductible portion, plus the linked donation id where the ticket generated one. Leave eventId off to read ticket sales across every event, or pass constituentId to read one person's purchases.

Errors

Same shape as the other APIs: an HTTP status plus a JSON body with a machine code and a human message.

Rate limits

Two limits apply, not one. Per key it is 15 requests a second and 600 a minute. There is also a per-IP limit of 40 a second and 1200 a minute, checked before we even read your key, so several keys calling from the same server share that budget. Either limit returns a 429 with a Retry-After header saying how many seconds to wait. The AI writing assistant is metered on its own separate from these: 10 requests a minute and 100 an hour for each person, and 1,000 an hour across the whole system. It also refuses text longer than 10,000 characters before any limit is counted.

The same per-key limits as the rest of /api/v1. Bulk loading a season of events is fine — pace it and honor 429 responses with a backoff and it will sail through.