Using the Business Hours API

Required scopes

Check the box in "API scopes" on the app editing screen, and include the scope in the scope parameter of the authorization URL.

Authentication

This follows the same token conventions as the other v1 APIs.

• A token bound to a business account — call it as-is
• A user-scoped token (for native mobile apps) — append ?organizationId= to the query

Endpoints

Business hours vs. workable hours

• Business hours — the opening and closing times published to customers. You can register multiple time slots per day of week (for example, a daytime session and an evening session)
• Workable hours — the operating window that acts as the upper bound for the hours a shift can be created for. Set a range that includes pre-open preparation and post-close cleanup

The shift management feature and the shift creation API can only register shifts within the workable hours range.

Setting workable hours

PUT /api/v1/stores/{storeId}/business-hours/work-hours-limit
Authorization: Bearer {token}
Content-Type: application/json

{
  "standardWorkStartTime": "08:00",
  "standardWorkEndTime": "23:00"
}

Specify times in HH:mm format; the start must be earlier than the end. Setting both to an empty string means no limit (24-hour shifts can be registered).

Registering a special business day

PUT /api/v1/stores/{storeId}/business-hours/special-days/2026-08-13
Authorization: Bearer {token}
Content-Type: application/json

{
  "isClosed": true,
  "note": "Summer closure"
}

Besides temporary closures, you can also register a change to the business hours for a specific date only. The open-status determination evaluates special business days first.

Related guides

• API authentication guide (OAuth 2.0 authorization code flow)
• OAuth scopes reference and availability
• Using the Reservations API
• Using the Staff API