Supported API for Square Online temporary fulfillment closures and reopening?

Questions
1

We are building an internal manager tool for an existing Square merchant, while retaining Square POS, Square Online, and existing marketplace integrations.

As of October 2026, is there a supported API or approved integration operation to:

  1. Create, extend, and remove date-specific Square Online pickup/delivery downtime without changing regular weekly hours or accepted orders?
  2. Pause all new/advance orders for a vacation, then reopen only after manager confirmation?
  3. Independently read the effective ordering/fulfillment availability and saved exceptions, including whether future-day ordering remains available?
  4. Control/read back Square’s native DoorDash, Uber Eats, and Grubhub channel pauses, separately from menu synchronization?

Please identify the supported endpoint/product, required OAuth scopes/access program, sandbox or non-disruptive qualification method, and restoration/concurrency semantics. If these controls are Dashboard-only, please confirm that limitation and whether an approved unattended mechanism exists. We will not use private endpoints or unapproved browser automation.

Prior reference: Using Square API, how can I pause online order? (staff answers March 2023 and March 2025). We are seeking current confirmation, not assuming that historical answer establishes October 2026 capability.

3

Square’s public APIs don’t currently expose controls to create/remove Square Online fulfillment downtime, pause/reopen ordering, or read back the effective availability. The Locations and Catalog APIs also don’t provide pause controls for Square’s built-in DoorDash, Uber Eats, and Grubhub integrations.

Changing location business hours isn’t a supported substitute for a temporary fulfillment closure. Changing catalog availability or zeroing inventory can affect POS and other channels without reliably stopping all new or advance orders.

For this workflow, use the controls in Square Dashboard. There isn’t a supported public API workaround that meets the requirements you outlined. Feel free to create a new post under the “Feature Request” type!