> For the complete documentation index, see [llms.txt](https://docs.decentraland.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.decentraland.org/faqs/posting-events.md).

# Posting Events

How to post events in Decentraland

<details>

<summary>Can anyone post an event on the Event Page?</summary>

Yes, anyone in the Decentraland community can create an Event listing for an event that takes place within Genesis City or a World. Being a LAND owner is not a requirement.

</details>

<details>

<summary>How do I post an event to the Event page?</summary>

Check out a quick breakdown here: <https://www.youtube.com/watch?v=jMNk\\_W1yqjU>

And yes you can edit event details after publishing!

</details>

<details>

<summary>How does the event review process work?</summary>

Review times depend on day/time of event submission, but won't take longer than a few hours. Events are reviewed by the team at the Decentraland Foundation. Add your email or Discord username so you can be contacted if necessary.

</details>

<details>

<summary>My event wasn't published, why not?</summary>

Your event may not have passed review because you did not fill in all the required information. Make sure you complete every field in the form when submitting an event.

</details>


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.decentraland.org/faqs/posting-events.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.