> For the complete documentation index, see [llms.txt](https://vendorspace.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://vendorspace.gitbook.io/docs/events/creating-an-event.md).

# Creating an event

Events are the core of everything you do in Vendor Space. Each event acts as its own workspace with its own vendors, products, booths, forms, and payments. Whether you're organizing a weekend craft market or a multi-day trade show, it all starts here.

***

## How to Create an Event

1. From your **Dashboard**, click the **Create Event** button in the top-right corner
2. Fill in the event details:
   * **Event Name** (required) -- Give your event a clear, recognizable name. This is what vendors will see.
   * **Start Date** and **End Date** (required) -- Select the dates your event runs. For single-day events, set both to the same date.
   * **Start Time** and **End Time** (optional) -- Add specific times if your event has set hours.
   * **Location** -- The venue name or address where your event takes place.
   * **Description** -- A summary of your event. This appears on your public event page when published.
   * **Event Type** -- Categorize your event (e.g., Craft Market, Food Festival, Trade Show).
   * **Tags** -- Add keywords to help you organize and filter your events later.
   * **Image URL** -- Link to a banner or hero image for your public event page.
3. Click **Create** to save your event

Your event is created in **Draft** status, which means it's only visible to you. You can take your time setting up products, booths, and forms before making anything public.

> **Tip:** You don't need to fill in every field right away. The only required fields are the event name and dates. You can always come back and add more details later.

***

## What to Do After Creating an Event

Once your event exists, you'll want to start building it out. Here's a typical setup flow:

1. **Add products** -- Create booth types, add-ons, and sponsorship packages with pricing
2. **Set up booths** -- Define your booth inventory and layout
3. **Configure event settings** -- Set vendor categories, approval rules, and vendor limits
4. **Create a form** -- Build an application or registration form for vendors
5. **Connect Stripe** -- Make sure your Stripe account is connected so you can collect payments
6. **Publish** -- When everything looks good, publish your event to make it available to vendors

> **Tip:** Don't worry about getting everything perfect before publishing. You can update event details, add new products, and adjust settings at any time -- even after vendors have started registering.

***

## A Few Things to Keep in Mind

* **Each event is independent.** Vendors, payments, and forms are all scoped to the event they belong to. This keeps your data organized, especially if you run multiple events.
* **Events start as drafts.** Nothing is public until you decide to publish. Take the time you need to set things up.
* **Running a recurring event?** You can duplicate an existing event instead of starting from scratch. See [Duplicating and archiving](/docs/events/duplicating-and-archiving.md) for 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 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://vendorspace.gitbook.io/docs/events/creating-an-event.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.