Look up a venue by ID

the VenueDataSource of the ID for the artist

the unique ID for the Venue

Use true to include the event node with any upcoming Concerts and Festivals for the venue.

Use true to suppress the performer node in Concert and Festival objects.

Use true to include external IDs for Concert, Artist, and Venue objects.
Note: expandExternalIdentifiers is included on Startup and higher plans and on Trial. Looking up a record by a third-party ID (for example /v3/artists/id/spotify:{id}) works on every plan; see Reverse ID Lookup.

Use true to include sameAs (i.e. links) for Artist responses.
Note: expandArtistSameAs is included on Startup and higher plans and on Trial. Looking up a record by a third-party ID (for example /v3/artists/id/spotify:{id}) works on every plan; see Reverse ID Lookup.

Use true to explicitly request past/historical Concert and Festival objects.
On entity-scoped historical access, including standard Pro, combine it with one of the six accepted scope selectors: artistId, artistSlug, artistName, venueId, venueSlug, or venueName. Requests without a scope selector are denied with a 403 explaining how to correct the request. An explicit all-scope entitlement removes that gateway scope requirement, but the request remains subject to endpoint validation and its independent historical window.
Note: dateModifiedFrom is a modification-date filter, not an entity scope or request for history, and cannot substitute for a scope selector.
Availability is tiered by plan: Trial and the free MCP plan get a rolling 1-year window, Pro a rolling 3-year window (artist/venue lookups only), and Pro+ and Enterprise include all-scope access with the full archive. Scope and time window are independent contract dimensions: a per-subscription all-scope grant widens which queries may use history but does not change that subscription's historical window.
On plans with geo + historical search (Enterprise baseline, or granted by request), a licensed past event-date window together with any geo parameter such as geoCountryIso2 is sufficient, with no expand flag needed. This flag is also accepted as explicit historical intent on an entitled geo request. Geo filters alone return normal upcoming events. When an authorized historical request omits its lower event-date bound, the gateway forwards its effective fixed-plus-rolling historical floor before fetching; truly unlimited history receives no invented floor.