# Turn event information into structured records.

Send information about an event, such as a link or a description. Events organizes the available details, including dates and places, into a structured record your application can store, review and display.

[Get started](https://cloud.gomry.com/orgs) · [All Cloud services](/cloud)

Example request · POST /v1/events/enrich

```sh
curl https://api.cloud.gomry.com/v1/events/enrich \
  -H "Authorization: Bearer $GOMRY_CLOUD_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "events": [{
    "text": "Concert in London, Nov 14, 2026, 7:30pm."
  }]
}'
```

## Prepare event details for your listings.

Event information can arrive as a web page, a short description or a record with some details already filled in. Events reads the information supplied for each event and organizes it into the same set of fields, so your application can work with a consistent record rather than parse each submission separately.

A city guide could use Events to prepare incoming listings for review. One submission might contain an event-page link; another might contain a short caption. Each becomes its own record with the available details, such as the event name, date and venue, ready for the guide’s listing pages and filters.

The record can also include local start, end and door times, timezone and UTC time, venue address, organizer, age limit and status. Performers and teams have roles such as headliner, support, home or away team. Image and ticket links accompany the result when supported by the source, along with the event classification that Classify would return.

## See which details come from the source.

Field provenance distinguishes stated information from inferred information. For example, a source may name a city without specifying its timezone; a timezone worked out from that context is different from one explicitly supplied in your input.

Unsupported fields are null rather than filled with defaults. Returned URLs must occur in the source. A page containing several events is marked multiple_events instead of being forced into one record; a calendar therefore needs a different collection step in your application.

## Enrich text, a link or fields you already know.

Example request · POST /v1/events/enrich

```json
{
  "events": [
    {
      "id": "submission-1",
      "text": "Evening concert at Riverside Hall, London. 14 November 2026, doors at 7pm, music at 7:30pm.",
      "event": {
        "name": "Evening concert",
        "timezone": "Europe/London",
        "attendance": "in_person"
      }
    }
  ]
}
```

Example event record

**Event name:** Evening concert

**Local start:** 14 November 2026, 19:30

**Timezone:** Europe/London

**UTC start:** 2026-11-14T19:30:00Z

**Venue:** Riverside Hall, London

**Attendance:** in_person

**End time:** null

The supplied timezone and attendance mode remain stated values. The end time has no support in the input, so it stays null. Your application can use the structured start time in its calendar and review other fields against their provenance.

A URL request reads that page, including its declared schema.org event data. It does not crawl a calendar, look up prices on other websites or resolve venue and performer names to canonical IDs.

## Event processing and URL fetching are separate units.

| Unit | Rate | When used |
| --- | --- | --- |
| Event enriched | $0.03 | Each event processed by the model |
| Page fetched | 0.5¢ | Each source URL fetched |

Text and partial-record inputs do not add a page-fetch charge. URL inputs can incur both units. If a URL cannot be fetched and there is no other information to process, nothing is charged.

## Build with Events

Enable Events for your project and issue a key with event-enrichment permission. Send a Bearer-authenticated JSON request to POST /v1/events/enrich. Each item needs at least a URL, text or event.name; your own ID can keep the response tied to its source record.

[Get started](https://cloud.gomry.com/orgs)

[Classify](/cloud/classify) · [Images](/cloud/images) · [All Cloud services](/cloud)