> ## Documentation Index
> Fetch the complete documentation index at: https://developers.momogood.com/llms.txt
> Use this file to discover all available pages before exploring further.

# List events

> GET /{your-namespace}/v1/events — list events the service user can access, filtered by `since`. Custom Data Export only today; coming soon on the connector families.

```http theme={null}
GET {EMS_BASE_URL}/<your-namespace>/v1/events
```

Returns events the dedicated service user has access to and that have changed since the `since` cursor.

<Note>
  This endpoint is **available on the Custom Data Export family only** today. The Salesforce and Blackbaud connector namespaces don't expose a list-events endpoint — those integrations typically receive event IDs out-of-band from the destination CRM.
</Note>

<Info>
  **Coming Soon — list-events on the connector families.** Contact [support@givergy.com](mailto:support@givergy.com) if you need it.
</Info>

<Note>
  Custom Data Export endpoints require a dedicated service user provisioned per customer. Contact [support@givergy.com](mailto:support@givergy.com) to set up your integration.
</Note>

## Authorization

The authenticated caller must be the dedicated service user provisioned for your Custom Data Export integration. Any other authenticated user receives `403 Forbidden`. See [Authentication → Authorization rules per family](/events-auctions/authentication#step-2-authorization-rules-per-family).

## Query parameters

| Name      | Type                 | Default      | Notes                                                      |
| --------- | -------------------- | ------------ | ---------------------------------------------------------- |
| `since`   | long (epoch seconds) | `1606062358` | Lower bound on `updated`. Use `-1` to backfill everything. |
| `orderBy` | string               | `createdAsc` | See ordering options below.                                |
| `offset`  | int                  | `0`          | Pagination offset.                                         |
| `limit`   | int                  | `1000`       | Page size. Maximum `1000`.                                 |

### Ordering options

`orderBy` accepts any of:

`createdAsc`, `createdDesc`, `updatedAsc`, `updatedDesc`, `eventDateAsc`, `eventDateDesc`, `startTimeAsc`, `startTimeDesc`, `endTimeAsc`, `endTimeDesc`, `nameAsc`, `nameDesc`, `clientNameAsc`, `clientNameDesc`, `agentNameAsc`, `agentNameDesc`, `venueNameAsc`, `venueNameDesc`

## Response

[`Event[]`](/events-auctions/schemas#event-custom-data-export-variant) — Custom Data Export variant. Includes `projectType` and `externalId` fields not present on the connector variants.

## Example

```bash theme={null}
curl --cookie session.cookie \
  '{EMS_BASE_URL}/<your-namespace>/v1/events?since=1714000000&orderBy=updatedDesc&limit=100'
```

```json theme={null}
[
  {
    "id": "8f3c2a1d-9b4e-4c7a-a1d2-6e5f4c3b2a10",
    "name": "Spring Charity Gala 2026",
    "status": "active",
    "inAidOf": "Hope Foundation",
    "startTime": 1715250600,
    "endTime": 1715279400,
    "eventDate": 1715250600,
    "timezone": "Europe/London",
    "currency": "GBP",
    "created": 1709123456,
    "updated": 1714003200,
    "projectType": "auction",
    "externalId": "EXT-2026-SPRING-001"
  }
]
```

## What's in the response

See the full [`Event` schema](/events-auctions/schemas#event-custom-data-export-variant) for the field-by-field reference. Key things to know:

* All amounts are integers in the event's minor currency unit (see [Conventions → Money fields](/events-auctions/conventions#money-fields)).
* Timestamps are Unix epoch seconds in UTC.
* `status` is always `"active"` because of the implicit active-only filter on list endpoints.
* `timezone` is an IANA timezone id (e.g. `Europe/London`, `America/New_York`).

## Next steps

Once you have an event id, fetch its detail:

* [List items for the event](/events-auctions/endpoints/items)
* [List purchases for the event](/events-auctions/endpoints/purchases)
* [List guests for the event](/events-auctions/endpoints/guests)

For ongoing sync, see the [polling pattern](/events-auctions/polling-pattern).