> ## Documentation Index > Fetch the complete documentation index at: https://devs.izap.ai/llms.txt > Use this file to discover all available pages before exploring further. # Replace opening hours > Replaces the whole week's opening hours in one call — a weekday omitted from the request is treated as closed. Changes take effect on live conversations immediately. The business is taken from the `business-id` header rather than the URL; the path-scoped form of this operation is deprecated. ## OpenAPI ````yaml /api-reference/openapi.json put /api/v1/businesses/hours openapi: 3.1.0 info: contact: email: suporte@izap.ai name: iZap API Support description: Public REST API for the iZap WhatsApp business messaging platform. license: name: MIT url: https://opensource.org/licenses/MIT title: iZap API version: v1 servers: - description: Production url: https://api.izap.ai - description: Staging url: https://api-staging.izap.ai security: [] tags: - description: >- Personal access tokens for calling this API, plus introspection of the token presented on a request. name: api-tokens - description: >- Create a business, read and update its profile, and manage its opening hours. name: businesses - description: >- Reusable images belonging to the caller's business, referenced when composing messages. name: business-library - description: Product catalog menus a business publishes to its customers. name: menus - description: >- Provision and inspect the WhatsApp Cloud API numbers attached to a business: registration, WABA details, per-number assistant binding and catalog sends. name: whatsapp-cloud - description: >- Conversation lifecycle — list, create and delete chats, and control read, snooze, status and AI pause state. name: chats - description: >- Read a conversation's messages, send free-form or template replies, and upload attachments. name: messages - description: >- Manage WhatsApp message templates: draft them locally, submit them to Meta for review and sync approval status back. name: whatsapp-templates - description: >- Bulk template sends. A transmission is previewed into a draft, then confirmed or cancelled — confirming dispatches to real recipients. name: transmissions - description: >- Register URLs that receive signed event deliveries when something happens in a business, rotate their signing secrets, and replay an individual delivery. name: webhooks - description: >- Server-rendered order visualisation page for a business slug, behind HTTP Basic auth. name: orders paths: /api/v1/businesses/hours: put: tags: - businesses summary: Replace opening hours description: >- Replaces the whole week's opening hours in one call — a weekday omitted from the request is treated as closed. Changes take effect on live conversations immediately. The business is taken from the `business-id` header rather than the URL; the path-scoped form of this operation is deprecated. operationId: updateCurrentBusinessHours parameters: - description: >- UUID of the business the request is scoped to. Required on this route; the deprecated /businesses/{business_id}/... form takes it from the path instead. in: header name: business-id required: true schema: anyOf: - type: string - type: 'null' description: >- UUID of the business the request is scoped to. Required on this route; the deprecated /businesses/{business_id}/... form takes it from the path instead. title: Business-Id requestBody: content: application/json: schema: $ref: '#/components/schemas/BusinessHoursIn' required: true responses: '200': content: application/json: schema: $ref: '#/components/schemas/BusinessHoursOut' description: Successful Response '401': content: application/json: schema: $ref: '#/components/schemas/ApiError' description: Missing or invalid credentials. '403': content: application/json: schema: $ref: '#/components/schemas/ApiError' description: The credential is valid but not authorized for this action. '404': content: application/json: schema: $ref: '#/components/schemas/ApiError' description: The resource, or the business named in the request, does not exist. '422': content: application/json: schema: $ref: '#/components/schemas/HTTPValidationError' description: Validation Error default: content: application/json: schema: $ref: '#/components/schemas/ApiError' description: Unexpected error. security: - bearerAuth: [] components: schemas: BusinessHoursIn: properties: friday: $ref: '#/components/schemas/BusinessHoursDayIn' monday: $ref: '#/components/schemas/BusinessHoursDayIn' saturday: $ref: '#/components/schemas/BusinessHoursDayIn' sunday: $ref: '#/components/schemas/BusinessHoursDayIn' thursday: $ref: '#/components/schemas/BusinessHoursDayIn' tuesday: $ref: '#/components/schemas/BusinessHoursDayIn' wednesday: $ref: '#/components/schemas/BusinessHoursDayIn' required: - monday - tuesday - wednesday - thursday - friday - saturday - sunday title: BusinessHoursIn type: object BusinessHoursOut: properties: friday: $ref: '#/components/schemas/BusinessHoursDayOut' monday: $ref: '#/components/schemas/BusinessHoursDayOut' saturday: $ref: '#/components/schemas/BusinessHoursDayOut' sunday: $ref: '#/components/schemas/BusinessHoursDayOut' thursday: $ref: '#/components/schemas/BusinessHoursDayOut' tuesday: $ref: '#/components/schemas/BusinessHoursDayOut' wednesday: $ref: '#/components/schemas/BusinessHoursDayOut' required: - monday - tuesday - wednesday - thursday - friday - saturday - sunday title: BusinessHoursOut type: object ApiError: description: >- The response body of a handled API error. ``detail`` is either a plain string (FastAPI's default for an ``HTTPException`` raised with a string, and for the ``default`` fastapi-users messages like ``"Not authenticated"``) or the structured :class:`ApiErrorDetail` object described above. ``code`` is present only on the top-level shape ``aizap.core.exceptions.AppException`` produces for its own 5xx responses (``"INTERNAL_ERROR"`` / ``"DB_ERROR"``); it does not duplicate the ``code`` nested inside a structured ``detail``. properties: code: anyOf: - type: string - type: 'null' default: null title: Code detail: anyOf: - type: string - $ref: '#/components/schemas/ApiErrorDetail' title: Detail required: - detail title: ApiError type: object HTTPValidationError: properties: detail: items: $ref: '#/components/schemas/ValidationError' title: Detail type: array title: HTTPValidationError type: object BusinessHoursDayIn: properties: mode: enum: - open_all_day - closed - custom title: Mode type: string ranges: items: $ref: '#/components/schemas/TimeRangeIn' title: Ranges type: array required: - mode title: BusinessHoursDayIn type: object BusinessHoursDayOut: properties: mode: enum: - open_all_day - closed - custom title: Mode type: string ranges: items: $ref: '#/components/schemas/TimeRangeOut' title: Ranges type: array required: - mode title: BusinessHoursDayOut type: object ApiErrorDetail: additionalProperties: true description: |- The structured ``detail`` object some error responses carry. Several handlers (the REST API plan gate, the free-tier limits, the webhooks entitlement gate, the closed customer-service window) raise ``HTTPException(detail={"code": ..., "message": ..., ...})`` — a fixed ``code``/``message`` pair plus extra fields specific to that error. ``extra="allow"`` keeps those fields in the documented shape instead of dropping them. properties: code: title: Code type: string message: title: Message type: string required: - code - message title: ApiErrorDetail type: object ValidationError: properties: ctx: title: Context type: object input: title: Input loc: items: anyOf: - type: string - type: integer title: Location type: array msg: title: Message type: string type: title: Error Type type: string required: - loc - msg - type title: ValidationError type: object TimeRangeIn: properties: end: title: End type: string start: title: Start type: string required: - start - end title: TimeRangeIn type: object TimeRangeOut: description: >- Echoes stored ``start_hour``/``end_hour`` verbatim, unvalidated. Existing rows predate the strict HH:MM format ``TimeRangeIn`` enforces on new writes (``BusinessService.is_open`` itself tolerates "H", "HH:MM", "HH:MM:SS"), so a read must never 500 on legacy data shaped that way. properties: end: title: End type: string start: title: Start type: string required: - start - end title: TimeRangeOut type: object securitySchemes: bearerAuth: description: >- Personal access token (izap_pat_…) sent as Authorization: Bearer ; dashboard session JWTs are also accepted. scheme: bearer type: http ````