Events

An Event represents an activity associated with an Organization, such as a meeting, workshop, fundraiser, or social gathering.

Events contain the information needed to describe and display an activity, including its name, description, schedule, location, and visibility. Events can be created directly in Join It or imported through an integration, such as Eventbrite.

Each Event belongs to one Organization. Registrations or tickets are stored as separate objects associated with the Event.

Below is a JSON example of an Event. Optional fields may be omitted or contain null, depending on the Event’s configuration and source.


{
  "_id": "eV7kRp2mNx9qTs4Wa",
  "organization_id": "oR3mKv8pLq2sNx6Tb",
  "name": "Annual Member Gathering",
  "description": "<p>Join us for an afternoon of updates and networking.</p>",
  "shortDescription": "Connect with fellow members at our annual gathering.",
  "status": 100,
  "source": "joinit",
  "external_id": null,
  "url": null,
  "logo": null,
  "members_only": false,
  "start_date": "2027-01-15T18:00:00.000Z",
  "end_date": "2027-01-15T20:00:00.000Z",
  "start_time": "13:00",
  "end_time": "15:00",
  "timezone": "America/New_York",
  "address": {
    "street": "123 Example Street",
    "city": "New York",
    "region": "NY",
    "country": "US",
    "zip": "10001"
  },
  "registration_count": 24,
  "created": "2026-11-19T10:00:00.000Z",
  "updated": "2026-12-01T15:30:00.000Z"
}

FieldTypeDescription
_idstringUnique ID identifying the Event in Join It.
organization_idstringID of the Organization that owns the Event.
namestringName of the Event.
descriptionstringFull description of the Event. May contain HTML formatting.
shortDescriptionstringBrief summary of the Event. Note the camelCase field name.
statusnumberStatus of the Event: 50 = Draft, 100 = Active, 300 = Expired.
sourcestringSystem where the Event originated. Examples include joinit, eventbrite, and zoom.
external_idstringID assigned by the originating external system. May be absent or null for Events created directly in Join It.
urlstringExternal URL associated with the Event, such as a registration page or meeting link. May be absent or null.
logostringURL of the image used to represent the Event.
members_onlybooleanWhether the Event’s visibility is restricted to members. Ticket eligibility is configured separately.
start_datedatetimeDate and time when the Event starts, represented as a UTC timestamp.
end_datedatetimeDate and time when the Event ends, represented as a UTC timestamp.
start_timestringLocal start time in the Event’s timezone, in 24-hour HH:mm format.
end_timestringLocal end time in the Event’s timezone, in 24-hour HH:mm format.
timezonestringIANA timezone identifier for the Event, such as America/New_York or Europe/London.
addressobjectPhysical location of the Event, when provided.
address.streetstringStreet address.
address.citystringCity.
address.regionstringState, province, or region.
address.countrystringCountry.
address.zipstringZIP or postal code.
registration_policystringOptional registration policy. Values are no-registration-required, free-registration-required, paid-registration-required, or other.
registration_countnumberCount of registrations recorded through Join It for the Event. This is not an attendance or check-in count.
members_order_countnumberStored count of associated member orders, when populated.
createddatetimeDate and time when the Event record was created in Join It.
updateddatetimeDate and time when the Event record was last updated.
last_published_ondatetimeRecorded publication timestamp, when available. Older records may use the Event’s creation timestamp.

Working with dates and times

Datetime values in the example use ISO 8601 format. The trailing Z indicates UTC.

Use start_date and end_date for chronological comparisons, and timezone to display the schedule in the Event’s local time. For example, 2027-01-15T18:00:00.000Z corresponds to 13:00 in America/New_York.

The start_time and end_time fields represent local clock times; they do not include a date or timezone offset.

Relationship to tickets and registrations

An Event describes the activity itself. Its related objects describe how people attend:

  • Registration Types represent ticket options, including price, capacity, and eligibility. Each references the Event through event_id.
  • Registrations represent individual attendee registrations and reference the Event through event_id.
    An Event’s members_only setting controls visibility. Registration Types have their own eligibility settings, so a publicly visible Event can still offer tickets restricted to members.

Did this page help you?