Temporarily Close a Business Location via API

Mark a location closed for a holiday or a renovation with specialHours, and why you must not use archival for a temporary closure.

Em resumo

O que este guia realiza

Close a location for a holiday or a date range without telling publishers the business is gone for good.

APIs utilizadas

patch/api/v1/locations/{id}Atualizar um local
post/api/v1/locations/{id}/archiveAgendar o arquivamento de um local

Referência

Locations

Pré-requisitos

An API key with write access
The locationId to update

Casos de uso típicos

Setting holiday closures ahead of time
Closing a location during a renovation
Marking a one-off closed day

There are two ways to close a location, and picking the wrong one is a real mistake. A temporary closure is a date override, not an archive. Use specialHours on PATCH /api/v1/locations/{id}, with one entry per closed date and closed: true.

# Closed on Christmas Day, half day on New Year's Eve
curl -X PATCH https://ai.synup.com/api/v1/locations/LOCATION_ID \
  -H "Authorization: Bearer $SYNUP_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "specialHours": [
      { "date": "2026-12-25", "closed": true },
      { "date": "2026-12-31", "closed": false, "open": "09:00", "close": "13:00" }
    ]
  }'

A renovation that closes the location for three weeks is one specialHours entry per closed day. Generate the date range and send them together. The regular weekly schedule still covers every day you don't override.

If the location really has closed for good, that is archival, and it is covered in the managing listings guide. To reverse a temporary closure, send the affected dates again with closed: false and the normal hours, or drop them from specialHours once they are in the past.