Skip to main content

Places (Venues & Physical Locations)

Menu Path: Relations > Places

The Places module serves as the centralized master directory for all physical spaces, event venues, concert arenas, pop-up studios, workshop locations, and store branches across your tenant. Instead of typing redundant address details every time an Event or Route is created, venues are defined once and linked everywhere.


🏗️ Creating and Configuring a Place​

  1. Navigate to Relations > Places.
  2. Click "Add Place" (or use keyboard shortcut N).

1. General Profile & Branding​

  • Name: Official name of the venue (e.g., "KüçükÇiftlik Park", "Moda Sahnesi").
  • Slug: URL-friendly unique identifier automatically generated from the title.
  • Abstract & Description: Brief hook for card previews, followed by a rich description of acoustic qualities, amenities, and technical infrastructure.
  • Brand Color: Custom accent color used in map pins and mobile headers.
  • Status: Choose between DRAFT (in preparation) and PUBLISHED (active for storefront vitrine and event binding).

2. Location & Precise Map Geocoding​

  • Physical Address: Street name, building/door number, neighborhood, district, city, and postal code.
  • Map Coordinates (Latitude & Longitude): Point coordinates on the map (GeoJSON Point [lng, lat]).
  • Area / Regional Categorization: Link to regional categories (e.g., "Kadıköy / Anadolu Yakası" or "Tarihi Yarımada").

Tip: Accurate coordinates are critical for route waypoint sequencing, proximity search ("Places near me"), and driving directions on the storefront.

3. Capacity & Daily Schedule​

  • Capacity Limits (min / max): Defines attendee boundaries. The maximum capacity acts as an upper ceiling for ticketing engines and seating planners.
  • Operating Schedule: Define weekly operating hours for each day (e.g., Monday through Sunday with distinct opening and closing times).

4. Pricing & Rental Models​

Venues can operate as free open spaces or commercial rental areas:

  • Free vs. Paid Venue: Toggle whether the venue is available for paid rental/booking.
  • Billing Type:
    • HOURLY: Workshop rooms, rehearsal studios, photo studios.
    • DAILY: Conference halls, exhibition centers.
    • PER_EVENT: Festival grounds, concert stadiums.
    • FIXED: Flat contract rate.
  • Base Rate & Currency: Standard rate (e.g., 250,000 TRY).

5. Media Assets​

  • Logo & Featured Image: High-resolution icons and showcase banners.
  • Cover Image & Gallery: Multiple interior and exterior photos, stage angles, and seating plan previews.

6. Ownership, Public Pools & Event Authorization​

Venues have explicit multi-tenant ownership models:

  • Owner Types:
    • WORKSPACE: Global venue managed by the tenant operators.
    • ORGANIZATION: Master guild, chamber, or cooperative venue.
    • MERCHANT: Privately owned venue by a marketplace vendor.
    • BRAND: Registered venue owned by a brand manufacturer.
  • Access Scopes:
    • Public Pool (isPublicPool: true): When enabled, all verified merchants and brands in the workspace can select this venue when organizing events.
    • Affiliate Inheritance (inheritToAffiliates: true): When owned by an Organization, all member artisans/merchants can host events at this venue.
    • Direct Authorization (authorizedMerchants): Specific sellers granted exclusive hosting privileges.
    • Lease / Rentals (rentals): Time-bound contracts allowing third-party entities to host events during specified periods.

🛡️ Enforcement: When a merchant or brand creates an event, the backend automatically validates if they own, rent, or have delegated permission to host at the selected venue. Unauthorized attempts trigger 403 Forbidden.


🔒 Soft Delete & Relational Integrity​

To protect historical ticket sales, past event logs, and active reservations:

  • Deleting a venue performs a soft-delete (deletedAt: Date).
  • Venues with upcoming active ticketed events cannot be permanently purged without reassigning or cancelling those events first.

💻 Developer SDK Integration​

Query venues from your storefront frontend with @avci/sdk or Python SDK:

import { AvciCMS } from '@avci/sdk';

const cms = new AvciCMS({ apiKey: 'YOUR_KEY', clientId: 'your-tenant-id' });

// List venues filtered by regional area
const { data: places } = await cms.place.list({ area: '6735c03a9f1a2b3c4d5e6f70', limit: 12 });

// Fetch full venue details by slug
const { data: venue } = await cms.place.getBySlug('kucukciftlik-park');
console.log(venue.capacity.max, venue.pricing?.amount);