Skip to main content
POST
/
location-outages
/
outage-number
/
{outageNumber}
/
actions
/
cancel
Cancel outage using outageNumber
curl --request POST \
  --url https://api.fabric.inc/v3/location-outages/outage-number/{outageNumber}/actions/cancel \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --header 'x-fabric-tenant-id: <x-fabric-tenant-id>' \
  --data '
{
  "reasonCode": "NOT_REQUIRED"
}
'
{
  "outageNumber": "OUTAGE1",
  "locationNumber": 23,
  "status": "CANCELLED",
  "type": "SHIP",
  "startDate": "2022-05-12T09:30:31.198Z",
  "endDate": "2022-05-12T09:30:31.198Z",
  "createdBy": "Carl Doe",
  "createdAt": "2022-05-12T09:30:31.198Z",
  "updatedBy": "Carl Doe",
  "updatedAt": "2022-05-12T09:30:31.198Z"
}

Authorizations

​
Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Headers

​
x-fabric-tenant-id
string
required

A header used by fabric to identify the tenant making the request. You must include tenant id in the authentication header for an API request to access any of fabric’s endpoints. You can retrieve the tenant id , which is also called account id, from Copilot. This header is required.

​
x-fabric-request-id
string

Unique request ID

​
x-fabric-channel-id
string

x-fabric-channel-id identifies the sales channel through which the API request is being made; primarily for multichannel use cases. It is an optional field. The default US channel is 12 while the default Canada channel is 13.

Path Parameters

​
outageNumber
string
required

Merchant-specified unique number to identify the outage

Body

application/json

Outage cancellation request

​
reasonCode
string
required

Merchant-defined reason code for outage

Example:

"NOT_REQUIRED"

Response

Cancelled

Response object representing a scheduled outage at a specific location, including status, duration, fulfillment impact, and auditing information.

​
locationNumber
integer<int32>
required

The unique identifier of the location affected by the outage, as defined by the merchant.

Example:

23

​
disabledFulfillmentMethods
string[]
required

A list of fulfillment methods that are disabled during the outage period (for example, ShipToHome, Pickup).

A fulfillment method that will be unavailable during the outage.

​
schedule
object
required

The date and time range during which the outage is scheduled to occur.

​
reasonCode
string
required

A merchant-defined reason for initiating the outage (for example, maintenance, staffing, system upgrade).

Example:

"maintenance"

​
outageId
string

A system-generated unique identifier for the outage event.

Example:

"9320183a01e214"

​
outageNumber
string

A merchant-defined unique identifier used to reference the outage.

Example:

"OUTAGE1"

​
status
enum<string>

The current status of the outage lifecycle.

Available options:
CREATED,
STARTED,
ENDED,
CANCELLED
Example:

"CREATED"

​
notes
string

Optional notes or additional context related to the outage.

Example:

"Any additional info"

​
createdBy
string

The user or system that originally created the outage record.

Example:

"Carl Doe"

​
createdAt
string<date-time>

The timestamp when the outage was created, in ISO 8601 UTC format.

Example:

"2022-05-12T09:30:31Z"

​
updatedBy
string

The user or system that last modified the outage record.

Example:

"Carl Doe"

​
updatedAt
string<date-time>

The timestamp of the most recent update to the outage record, in ISO 8601 UTC format.

Example:

"2022-05-12T09:30:31Z"

​
auditLogs
object[]

A list of audit log entries capturing changes and actions performed on the outage record.