Skip to main content
GET
/
event
/
getEventData
/
{event_id}
Get Event Details (Legacy)
curl --request GET \
  --url https://app.flashquotes.com/api/event/getEventData/{event_id} \
  --header 'x-api-key: <api-key>'
{
  "id": "<string>",
  "name": "<string>",
  "startDate": "2023-11-07T05:31:56Z",
  "endDate": "2023-11-07T05:31:56Z",
  "location": {
    "name": "<string>",
    "address": "<string>",
    "city": "<string>",
    "state": "<string>",
    "zip": "<string>"
  },
  "resources": [
    {
      "id": "<string>",
      "name": "<string>",
      "quantity": 123
    }
  ],
  "staff": [
    {
      "id": "<string>",
      "firstName": "<string>",
      "lastName": "<string>",
      "email": "<string>"
    }
  ],
  "addons": [
    {
      "id": "<string>",
      "name": "<string>",
      "quantity": 123,
      "price": 123
    }
  ],
  "booking": {
    "id": "<string>",
    "entityToInvoice": "<string>",
    "email": "<string>",
    "phone": "<string>"
  },
  "eventBriefUrl": "<string>"
}

Documentation Index

Fetch the complete documentation index at: https://docs.flashquotes.com/llms.txt

Use this file to discover all available pages before exploring further.

Deprecated. This endpoint returns the original flat response shape. It is maintained for backwards compatibility only. For new integrations, use GET /events/{id}, which supports the standard public API conventions (object discriminators, expand[], slim canonical shapes, and the standard error envelope).
This endpoint returns comprehensive information about a specific event, including its location, resources, staff assignments, and associated booking details.

​
Response

The response includes a detailed event object containing:
  • Event identification and basic details
  • Location information (venue name, address)
  • Assigned resources (equipment, machines)
  • Staff assignments
  • Associated addons
  • Booking status and details
  • Event brief reference

​
Common Use Cases

  • Retrieving event details for display
  • Checking resource and staff assignments
  • Verifying event location and timing
  • Accessing booking information
  • Confirming addon selections

​
Notes

  • The event ID must be valid and associated with your company
  • Returns a 404 error if the event is not found
  • All event times are returned in ISO 8601 format with timezone
  • Access requires a valid API key with appropriate permissions

​
Migrating to GET /events/{id}

The new endpoint returns a slim default body with foreign-key ids; relations move behind expand[]. Key mappings:
Legacy (top-level flat)v2 (nested via expand)
leadCompanyNamebooking.lead.companyName (with expand[]=booking.lead)
booking.eventTypeNamebooking.eventType.name (with expand[]=booking.eventType)
location, resources, staff, addons (always present)Available via expand[]=location, expand[]=resources, etc.

Authorizations

​
x-api-key
string
header
required

API key for authentication

Path Parameters

​
event_id
string
required

The unique identifier of the event

Response

Event data retrieved successfully

Legacy event shape returned by GET /event/getEventData/{event_id}.

​
id
string
​
name
string
​
startDate
string<date-time>
​
endDate
string<date-time>
​
location
object
​
resources
object[]
​
staff
object[]
​
addons
object[]
​
booking
object
​
eventBriefUrl
string

URL to access the event brief