How do I delete a store boundary using the Delivery Solutions API?

Send a DELETE request to https://sandbox.api.deliverysolutions.co/store/boundary/boundaryId with headers accept: application/json, tenantId, x-api-key, and x-compression.

What parameter is required to delete a boundary?

Provide boundaryId (int32), a unique numeric id for the boundary being deleted.

What responses can I expect when deleting a boundary?

200: Success; 400: Bad Request.

Delete Boundary

The "Delete Boundary" API endpoint requires a unique integer boundaryId to delete a specific boundary, responds with a 200 status on success or 400 on bad request, and includes example cURL request headers such as tenantId, x-api-key, and x-compression.

Parameters

boundaryId (int32, required): A unique numeric id for the boundary being deleted.

Responses

200: Success
400: Bad Request

Example Request

Shell (cURL)

curl --request DELETE \
     --url https://sandbox.api.deliverysolutions.co/store/boundary/boundaryId \
     --header 'accept: application/json' \
     --header 'tenantId: YOUR_TENANT_ID' \
     --header 'x-api-key: YOUR_API_KEY' \
     --header 'x-compression: true'

Example Responses

200 - Result
400 - Result

Edit Boundary
The "Edit Boundary" API requires a unique integer boundaryId and an array of boundary objects with a mandatory status field set to either "active" or "inactive" to modify a specified boundary, returning a 200 status code on success or 400 on error.
Check Delivery Assurance
The Delivery Assurance service offers five key checks—Store Boundary, DSP, Store Boundary + DSP, Confidence Score, and Return Confidence Score—to verify delivery coverage and reliability based on store boundaries, provider availability, and confidence metrics, with specific requirements such as providing pickup and dropoff times for time-window checks, restrictions on provider configurations, caching options to reduce latency, and current availability of confidence scores only in the U.S., while excluding business rules and orchestration engine usage.
Delivery Solutions API Doc - Premium
The Delivery Solutions API documentation provides sandbox and production base URLs and portals, instructions for importing and running a Postman collection including a pre-script request, and specifies that authentication requires passing a generated API key and tenantId in request headers while keeping the key secure.
Get Order by External ID
The "Get Order by External ID" API allows retrieval of an order using a unique external ID, optionally forcing an update to fetch the latest order details from the provider (if supported), returning the order data with possible error information, and uses HTTP status codes 200, 400, or 404 to indicate success or failure.
How to Strengthen Retail Deliveries with Delivery Assurance Technology
The article discusses how retail businesses face challenges like late deliveries, lost packages, and scaling coverage due to increased e-commerce demand, and emphasizes that implementing delivery assurance technology—such as geofencing and real-time tracking—can help overcome these hurdles by ensuring timely, secure, and reliable parcel deliveries that meet customer expectations and protect business credibility.
Create Batch
The "Create Batch" API endpoint requires a unique batchExternalId, dispatch details specifying scheduling and reference times, sorting parameters to prioritize order dispatch by fields like deliveryDistance, and optionally order details, with example usage shown via a POST request including headers and JSON body, returning status codes such as 201 for success or 400 for errors.