---
title: "Submit a consumer event by URL"
method: GET
path: "/events/{event_name}"
tags: ["Events"]
---

# Submit a consumer event by URL

`GET /events/{event_name}`

Fires the named consumer event using data from the query string and optional JWT claim. Always returns HTTP 200 regardless of outcome — check for an `X-Extole-Error-Message` response header to detect processing errors. A new `access_token` cookie may be set on the response when the event establishes or upgrades a consumer identity.

## Path parameters

- `event_name` string, required

## Response `200`

Always return 200. Strongly typed response body, see SubmitEventResponse.

- SubmitEventResponse
  - `cookie_consent` string, nullable, required — Cookie consent string set by the platform during event processing. Null when no consent update occurred.
  - `id` string, required — Extole-assigned event identifier for the fired event.
  - `token` string, required — Current access token for the consumer. Allows client code to read the token without relying on cookies.

## Other responses

- `400` — Bad Request
- `401` — Unauthorized
- `403` — Forbidden
- `415` — Unsupported Media Type
- `429` — Too Many Requests

---

[API](https://skmtc.net/extole/apis/integration-api-server-to-extole.md) · [All operations](https://skmtc.net/extole/apis/integration-api-server-to-extole/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/extole/integration-api-server-to-extole/revisions/c16e62e66755/schema)