---
title: "List message attempts for an event"
method: GET
path: "/v1/events/{event_token}/attempts"
tags: ["Event"]
---

# List message attempts for an event

`GET /v1/events/{event_token}/attempts`

List all the message attempts for a given event.

## Path parameters

- `event_token` string, required

## Query parameters

- `status` 'FAILED' | 'PENDING' | 'SENDING' | 'SUCCESS'
- `begin` string, date-time
- `end` string, date-time
- `ending_before` string
- `page_size` integer
- `starting_after` string

## Response `200`

OK

- object
  - `data` MessageAttempt[], required
    - `created` string, date-time, required — An RFC 3339 timestamp for when the event was created. UTC time zone. If no timezone is specified, UTC will be used.
    - `event_subscription_token` string, required — Globally unique identifier.
    - `event_token` string, required — Globally unique identifier.
    - `response` string, required — The response body from the event subscription's URL.
    - `response_status_code` integer, required — The response status code from the event subscription's URL.
    - `status` 'FAILED' | 'PENDING' | 'SENDING' | 'SUCCESS', required — The status of the event attempt.
    - `token` string, required — Globally unique identifier.
    - `url` string, uri, required
  - `has_more` boolean, required

## Other responses

- `400` — A parameter in the query given in the request does not match the valid queries for the endpoint.
- `401` — | | | |---|---| | User has not been authenticated | Invalid or missing API key | | API key is not active | The API key used is no longer active | | Could not find API key | The API key provided is not associated with any user | | Please provide API key in Authorization header | The Authorization header is not in the request | | Please provide API key in the form Authorization: [api-key] | The Authorization header is not formatted properly | | Insufficient privileges. Issuing API key required | Write access requires an Issuing API key. Reach out at [lithic.com/contact](https://lithic.com/contact) | | Insufficient privileges to create virtual cards. | Creating virtual cards requires an additional privilege | Reach out at [lithic.com/contact](https://lithic.com/contact) |
- `404` — The specified resource was not found.
- `409` — The request could not be completed due to a conflict with the current state of the target resource.
- `422` — Unprocessable entity.
- `429` — Client has exceeded the number of allowed requests in a given time period. | | | |---|---| | Rate limited, too many requests per second | User has exceeded their per second rate limit | | Rate limited, reached daily limit | User has exceeded their daily rate limit | | Rate limited, too many keys tried | One IP has queried too many different API keys |

---

[API](https://skmtc.net/lithic-com/apis/lithic-developer-api.md) · [All operations](https://skmtc.net/lithic-com/apis/lithic-developer-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/lithic-com/lithic-developer-api/versions/53ab5d4e2adb/schema)