Event Vesta Partner Integration Guide

This guide outlines the data structure needed to share events and organizations with Event Vesta. All events must be associated with a Company (Organization). For trial imports, you may provide a static file (CSV, JSON, XML) or a feed URL.

Entities Overview

• Company (Organization) – The organizer or promoter of events.
• Event Listing – An individual event tied to a Company.
• Boosts (Optional) – Extra promotion attached to an Event Listing.

1. Companies (Organizations)

Required Fields

• organization_name (string) – Name of the organization.

• markets (string) – Default market for the organization. Full list of markets.

  Note: Markets can later be refined based on event locations, but each company must have a default market at creation.

• contact_name (string) – Primary contact person. Listed publicly on some calendars.
• public_contact_email (string) – Email displayed on events for attendee questions. Listed publicly on some calendars.

• vesta_communications_emails (string, one or more emails) – Used for reporting and updates. Private, not listed publicly.

  If white-labeling Vesta, include your own team’s contact email here in addition to the organization’s.

Optional Fields

• organization_description (string) – Short description of the company.
• profile_image_url (string) – Recommended: 300x300px square, max 1200x1200px.
• phone_number (string)
• facebook_link (string)
• team_admins (list of strings) – Additional admin users.

2. Event Listings

Required Fields

• event_name (string)
• event_teaser (string) – Up to ~150 characters.
• event_description (string) – Up to 500 characters.
• event_image_url (string) – Aspect ratio 2:1, .png or .jpeg format.
• primary_category (string) – Main event category.
• venue_name (string) – Required if in-person.
• street, city, state, zip (strings) – Required address fields for in-person events.
• start_time (string) – Format: MM/DD/YYYY hh:mm AM/PM . Multiple occurrences allowed.
• end_time (string) – Format: MM/DD/YYYY hh:mm AM/PM . Multiple occurrences allowed.
• weekly_reoccurring (boolean) – Yes/No.
  • day_of_week (string) – Only use if weekly_reoccurring is Yes.
    • reoccurring_start_time (string) – hh:mm AM/PM. Only use if weekly_reoccurring is Yes. (one needed for each day_of_week)
    • reoccurring_end_time (string) – hh:mm AM/PM. Only use if weekly_reoccurring is Yes. (one needed for each day_of_week)
• timezone (string)
• ticket_purchase_url (string) – Link to buy tickets or RSVP (or mark as “registration not required”).
• family_friendly (boolean) – Yes/No.

Optional Fields

• additional_categories (list of up to 2 strings)
• age_group (string or list)
• different_parking_address (string) – If different than event venue.
• cheapest_tickets (number) – Lowest ticket price.
• max_attendance (number)
• contact_name, contact_phone, contact_email – Event-specific contact details (overrides company defaults). Listed publicly on some calendars.

3. Boosts (Optional)

Boosts represent add-on marketing channels.

• event_id (string) – Must match an existing Event Listing.
• boost_type (string) – Example: “email_blast”, “featured_listing”, “press_release”. Contact for full up-to-date list.
• schedule (string) – Format: MM/DD/YYYY hh:mm AM/PM to MM/DD/YYYY hh:mm AM/PM

4. Delivery Options

• API/Feed URL – Preferred if available.
• Flat File (CSV/JSON/XML) – Acceptable for initial trials.

5. Next Steps

1. Provide a sample feed of at least one Company and a few Events.
2. Event Vesta will validate and manually import for the trial.
3. Upon successful partnership, we’ll build a tailored connector for automated sync.