Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Headers
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.
Unique request ID
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.
Body
Request payload used to create a new outage for a specific location. The outage defines when and how fulfillment operations should be paused.
The unique identifier of the location where the outage will take effect, as specified by the merchant.
23
A list of fulfillment methods that will be temporarily disabled during the outage (for example, ShipToHome, Pickup).
A fulfillment method that will be disabled during the outage window.
The specific time range (start and end) during which the outage is active.
A merchant-defined reason for the outage, useful for internal reporting or auditing (for example, maintenance, system upgrade).
"maintenance"
A merchant-defined unique identifier used to reference the outage.
"OUTAGE1"
Optional free-text field for including additional information or context about the outage.
"Any additional info"
Identifier or name of the user or system that created the outage request.
"Carl Doe"
Identifier or name of the user or system that last updated the outage request.
"Carl Doe"
Response
Created
Response object representing a scheduled outage at a specific location, including status, duration, fulfillment impact, and auditing information.
The unique identifier of the location affected by the outage, as defined by the merchant.
23
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.
The date and time range during which the outage is scheduled to occur.
A merchant-defined reason for initiating the outage (for example, maintenance, staffing, system upgrade).
"maintenance"
A system-generated unique identifier for the outage event.
"9320183a01e214"
A merchant-defined unique identifier used to reference the outage.
"OUTAGE1"
The current status of the outage lifecycle.
CREATED, STARTED, ENDED, CANCELLED "CREATED"
Optional notes or additional context related to the outage.
"Any additional info"
The user or system that originally created the outage record.
"Carl Doe"
The timestamp when the outage was created, in ISO 8601 UTC format.
"2022-05-12T09:30:31Z"
The user or system that last modified the outage record.
"Carl Doe"
The timestamp of the most recent update to the outage record, in ISO 8601 UTC format.
"2022-05-12T09:30:31Z"
A list of audit log entries capturing changes and actions performed on the outage record.
