Volume Pricing with other API methods
Retrieve or delete a single Volume Pricing record by ID using the Public API.
This document explains how to retrieve and delete Volume Pricing records using the Public API.
Get a Volume Pricing record
Section titled “Get a Volume Pricing record”1. Endpoint
Section titled “1. Endpoint”To retrieve a specific Volume Pricing record:
GET https://wholesale.samita.io/api/v1/volume-pricings/{id}{id}is the ID of the Volume Pricing record

- The ID can be obtained from the app interface
- Do not include the “#” symbol when using the ID
Example:
GET https://wholesale.samita.io/api/v1/volume-pricings/12. Request Headers
Section titled “2. Request Headers”All GET requests must include the following required headers:
| Header | Description | Required |
|---|---|---|
X-SAMITA-API-KEY |
API key provided in the Wholesale app | Yes |
X-SAMITA-SHOP-URL |
Shopify shop domain in format xxx.myshopify.com | Yes |
CONTENT-TYPE |
Must be application/json |
Yes |
If any of these headers are missing, the request will be rejected.
3. Request Body
Section titled “3. Request Body”- The GET API does not require a request body
- Only the
{id}parameter in the URL is required
4. API Response
Section titled “4. API Response”Error Responses
Section titled “Error Responses”401 – Unauthorized
This error occurs when authentication fails.
Possible reasons:
- Missing shop URL
- Missing API key
- Incorrect shop URL
- Incorrect API key
- API key does not match the provided shop
403 – This action is unauthorized
This error occurs when:
- The API key does not have View permission
- The provided ID does not exist
- Insufficient access rights for the API key
Each API key can be assigned the following permissions:
- View
- Create
- Update
- Delete
The GET API requires View permission.
429 – Too Many Requests
This error occurs when the rate limit is exceeded.
Current limits:
- Maximum 1 request per 5 minutes
- Maximum 50 requests per day
Success Response
Section titled “Success Response”200 – API Success
- The request is valid
- The record is successfully retrieved
- Response is returned in JSON format
Example:
{ "id": 1, "title": "New Volume Pricing", "status": true, "type": "quantity", "apply_customer": { "type": "all", "tags": [] }, "exclude_customer": { "type": "none", "tags": [] }, "apply_product": { "type": "all", "product_ids": [], "product_tags": [], "collection_ids": [], "apply_for_variants": false }, "exclude_product": { "type": "none", "product_ids": [], "collection_ids": [] }, "discount_for_variants": [ { "id": 8516448190631, "duplicated": false, "variant_pricing": true, "from_qty": "0", "from_amount": "0", "to_qty": "10", "to_amount": "0", "discount_groups": [ { "name": "all", "type": "percent", "value": "10" } ], "variants": [ { "id": 46747346763943, "duplicated": false, "from_qty": "0", "from_amount": "0", "to_qty": "10", "to_amount": "0", "discount_groups": [ { "name": "all", "type": "percent", "value": "10" } ] } ] } ], "apply_market": { "type": "all", "handle": [] }, "discount_method": "variant", "discount_groups": [ { "from_qty": "0", "from_amount": "0", "to_qty": "10", "to_amount": "0", "type": "percent", "value": "10" } ], "active_date": { "types": [], "start_at": "", "end_at": "" }, "created_at": "2026-01-15T10:00:00", "updated_at": "2026-01-15T10:00:00"}Delete a Volume Pricing record
Section titled “Delete a Volume Pricing record”1. Endpoint
Section titled “1. Endpoint”To delete one or more existing Volume Pricing records:
DELETE https://wholesale.samita.io/api/v1/volume-pricings/{id}{id}in the URL should be a valid record ID, but the API actually deletes whichever records are listed in theidsparameter (see Request Body below) — not the URL segment.
Example:
DELETE https://wholesale.samita.io/api/v1/volume-pricings/12. Request Headers
Section titled “2. Request Headers”All DELETE requests must include the following required headers:
| Header | Description | Required |
|---|---|---|
X-SAMITA-API-KEY |
API key provided in the Wholesale app | Yes |
X-SAMITA-SHOP-URL |
Shopify shop domain in format xxx.myshopify.com | Yes |
CONTENT-TYPE |
Must be application/json |
Yes |
3. Request Body
Section titled “3. Request Body”- Pass an
idsparameter — a comma-separated list of record IDs to delete (as a query string parameter or a JSON body field). This supports deleting multiple records in one call, e.g.ids=1,2,3. - This
idsparameter is required — without it, no records are deleted.
4. API Response
Section titled “4. API Response”Error Responses
Section titled “Error Responses”401 – Unauthorized
Returned when authentication fails.
Possible reasons:
- Missing shop URL
- Missing API key
- Incorrect shop URL
- Incorrect API key
- API key does not match the shop
403 – This action is unauthorized
This error occurs when:
- The API key does not have Delete permission
- The provided ID does not exist
- The API key does not have sufficient access rights
The DELETE API requires Delete permission.
429 – Too Many Requests
Returned when the request exceeds the allowed rate limit.
Rate limits:
| Limit Type | Value |
|---|---|
| Request frequency | 1 request per 5 minutes |
| Daily limit | 50 requests per day |
Success Response
Section titled “Success Response”200 – API Success
- The Volume Pricing record is successfully deleted
- No content or a confirmation message may be returned
Example:
{ "success": true}