Operation

Update Layout Area

PATCH/venues/{id}/layouts/{layoutId}/areas/{areaId}

Update an area's properties within a venue layout. Change the area name, capacity limits, or general admission settings. This doesn't affect the individual seats within the area-use the seat endpoints for that.

When to use this

Renaming an area to match updated signage
Adjusting capacity limits for safety compliance
Converting between reserved seating and general admission

Path parameters

idstringRequired: Venue ID
layoutIdstringRequired: Layout ID
areaIdstringRequired: Area ID

Headers

Idempotency-KeystringOptional: Makes the write safe to retry. The first request with a key does the work and its response is stored for 24 hours; a repeat with the same key and the same request (method, path, query, X-Ticketlayer-Channel, TL-Version and body) gets that stored status and body back, marked `Idempotent-Replay: true`, without running again. The key is scoped to your organisation and your credential. The same key with a different request is 422 IDEMPOTENCY_KEY_REUSED; a repeat while the first is still running waits for it, then answers 409 IDEMPOTENT_REQUEST_IN_PROGRESS if it has not finished. Only a 2xx is stored: after an error the key is free again. Omit the header and the request behaves as it always has.

Body

namestringArea name

descriptionstringArea description

type"unallocated" | "allocated"Area type

status"active" | "inactive"Area status

capacitynumberTotal capacity

displayOrdernumberDisplay order in UI

colorstringHex color

seatsany[]Seats array

▼positionobjectVisual positioning for GA areas on seating map

x*number

y*number

width*number

height*number

categoryIdstringCategory ID for pricing (especially for GA areas)

Returns

Area updated successfully

Errors

400: Bad Request - Invalid input
401: Unauthorized - Authentication required
403: Forbidden - Insufficient permissions
404: Not Found - Resource not found
500: Internal Server Error

Every error names its code and links to it. All error codes

Notes

Note

Changing capacity limits won't affect existing ticket sales for this area.

Tip

Use clear, venue-specific names that customers will recognise when choosing seats.

import { BackstageClient } from '@ticketlayer/backstage';const client = new BackstageClient({  organisationSlug: 'your-org',});client.setAccessToken('YOUR_ACCESS_TOKEN');// Update venuelayoutareaconst updated = await client.venuelayoutarea.update('{{VENUELAYOUTAREA_ID}}', {  name: 'Updated Name',  // Add fields to update});console.log(`Updated venuelayoutarea: ${updated.name}`);

Response 200

{
  "area": {
    "id": "vla_abc123",
    "name": "Main Floor",
    "description": "General admission area",
    "type": "unallocated",
    "status": "active",
    "capacity": 500,
    "displayOrder": 1,
    "color": "#FFD700",
    "seats": []
  }
}

Update Layout Area

When to use this

Path parameters

Headers

Body

Returns

Errors

Notes

Related

Try it in test mode

Path parameters

Body