> For the complete documentation index, see [llms.txt](https://guide.pay.gov.sg/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guide.pay.gov.sg/api-resources/events/the-event-object.md).

# The event object

**Attributes**

***

**id** string

Unique identifier for the object.

***

**data** hash

Object containing data associated with the event.

<details>

<summary>show child attributes</summary>

**data.object** hash

Object containing the API resource relevant to the event. For example, an `payment.succeeded` event will have a full payment object as the value of the `object` key.

</details>

***

**type** string

Description of the event (for example, `payment.succeeded` )

***

#### More attributes

***

**object** string, value is "event"

String representing the object’s type. Objects of the same type share the same value.

***

**payment\_service\_id** string

The payment service that originates the event.

***

**created** timestamp

Time at which the object was created. Measured in milliseconds since the Unix epoch.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://guide.pay.gov.sg/api-resources/events/the-event-object.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.