Developers
The Qurate Receiver API
Interior designers run their projects in Qurate: every ordered piece, where it is going, and when it is due. A receiving warehouse that integrates reports arrivals, condition, photos and deliveries straight into the designer's project, so the project holds the record instead of an inbox.
For receiving warehouses
There is no sign-up for a key. Each designer you work with issues one from their Qurate account and sends it to you, one key per designer. Integrate once and every designer who hands you a key is covered.
Warehouses that report through the API carry the Integrated Partner badge in designer searches. Not ready to integrate? Qurate Connector does the same job from a browser. Not listed yet? List your warehouse free.
For designers
Create a key under Settings > Developers, named after the receiver, and send it to them with a link to this page. Every change they report lands on the item and on your activity feed the moment it happens.
Reference
v1Basics
https://decorvault-api.onrender.com/api/receiver-api/v1AuthAuthorization: Bearer qrk_… on every request. X-Api-Key: qrk_… also works.FormatJSON in and out. Send Content-Type: application/json on writes. Dates are ISO 8601 in UTC.TransportHTTPS only. Requests over plain HTTP are refused.Rate limit600 requests per 15 minutes per key. Over the limit you get 429 with a Retry-After header.Scopesitems:read lists and reads items; items:write reports receipts, updates, photos and deliveries. A key has one or both, chosen when it is created.A key belongs to one Qurate account and sees only that account's ordered items: products on a concept that carries a purchase order number. It never sees prices, vendors or source links.
Quick start
1. Check the key works and see which account it belongs to.
curl https://decorvault-api.onrender.com/api/receiver-api/v1/me \
-H "Authorization: Bearer qrk_your_key_here"2. List what is expected to arrive, soonest first.
curl "https://decorvault-api.onrender.com/api/receiver-api/v1/items?status=EXPECTED" \
-H "Authorization: Bearer qrk_your_key_here"3. When a piece lands, report it. Only condition is needed; everything else is optional.
curl -X POST https://decorvault-api.onrender.com/api/receiver-api/v1/items/ITEM_ID/receive \
-H "Authorization: Bearer qrk_your_key_here" \
-H "Content-Type: application/json" \
-d '{
"condition": "DAMAGED",
"quantity": 1,
"location": "Bay 4, rack C",
"notes": "Cracked drawer front on arrival.",
"dimensions": { "heightIn": 34, "widthIn": 110, "lengthIn": 40, "weightLb": 210 }
}'4. When it goes out to the client, mark it delivered.
curl -X POST https://decorvault-api.onrender.com/api/receiver-api/v1/items/ITEM_ID/deliver \
-H "Authorization: Bearer qrk_your_key_here" \
-H "Content-Type: application/json" \
-d '{ "signedBy": "M. Henderson", "notes": "Placed in the living room." }'The same calls in JavaScript:
const BASE = "https://decorvault-api.onrender.com/api/receiver-api/v1";
const headers = { Authorization: "Bearer " + process.env.QURATE_KEY, "Content-Type": "application/json" };
const { items } = await fetch(BASE + "/items?status=EXPECTED", { headers }).then((r) => r.json());
await fetch(BASE + "/items/" + items[0].id + "/receive", {
method: "POST",
headers,
body: JSON.stringify({ condition: "GOOD", quantity: 2, location: "Bay 4" }),
});The item object
Every endpoint returns items in this shape. status moves from EXPECTED to RECEIVED to DELIVERED.
{
"id": "clx8f2a1b0003abcd",
"status": "EXPECTED",
"product": {
"id": "clx7...",
"name": "Katrina Sectional",
"sku": "KS-110-GRY",
"dimensions": "110\"W x 40\"D x 34\"H",
"image": "https://…/uploads/products/katrina.jpg"
},
"purchaseOrder": { "number": "PO-1001" },
"project": { "id": "clx6...", "name": "Lake House" },
"client": { "name": "The Hendersons" },
"concept": "Living Room",
"expectedAt": "2026-11-10T00:00:00.000Z",
"receivedAt": null,
"condition": null,
"quantityReceived": null,
"location": null,
"notes": null,
"dimensions": { "heightIn": null, "widthIn": null, "lengthIn": null, "weightLb": null },
"photos": [],
"deliveredAt": null,
"deliveryNotes": null,
"deliverySignedBy": null,
"reportedBy": null,
"updatedAt": "2026-10-30T18:02:11.000Z"
}| Field | Type | Meaning |
|---|---|---|
| id | string | Stable identifier. Use it in every item endpoint. |
| status | enum | EXPECTED, RECEIVED or DELIVERED. |
| product | object | name, sku, the listed dimensions as text, and an image URL. For identifying the box. |
| purchaseOrder.number | string | The PO the item was ordered under. Filter the list by it. |
| project / client | object | null | Where the piece is going. Present when the concept is attached to a client project. |
| expectedAt | date | null | When the designer expects it. |
| receivedAt | date | null | Set by /receive. Kept on later updates unless you send a new value. |
| condition | enum | null | GOOD, DAMAGED or WRONG_ITEM. |
| quantityReceived | int | null | Units that arrived, for partial shipments. |
| location | string | null | Free text: where it sits at your facility. |
| notes | string | null | Receiving notes, up to 4000 characters. |
| dimensions | object | Measured on arrival: heightIn, widthIn, lengthIn, weightLb. |
| photos | string[] | URLs of photos you uploaded, in order. |
| deliveredAt / deliverySignedBy / deliveryNotes | mixed | Set by /deliver. |
| reportedBy | string | null | Name of the key that last reported. |
| updatedAt | date | Last change from any source. Use with updatedSince to poll. |
Endpoints
/meThe key's name, scopes and expiry, and the designer it belongs to. Returns { key, designer }.
/itemsOrdered items, soonest expected first. Returns { items, total, limit, offset, hasMore }.
| Field | Type | Meaning |
|---|---|---|
| status | query | EXPECTED, RECEIVED or DELIVERED. |
| po | query | Exact purchase order number. |
| updatedSince | query | ISO date. Only items changed since then; the cheapest way to poll. |
| limit / offset | query | Page size up to 200 (default 50) and start position. |
/items/{id}One item. 404 if it is not on this account.
/items/{id}/receiveMarks the item received. Returns 201 the first time, 200 on a repeat call, which updates the details and keeps the original receivedAt. Refused with 409 ALREADY_DELIVERED once delivered.
| Field | Type | Meaning |
|---|---|---|
| condition | enum | GOOD (default), DAMAGED or WRONG_ITEM. |
| receivedAt | date | When it landed. Defaults to now. |
| quantity | int | Units received. |
| location | string ≤ 200 | Bay, rack, bin at your facility. |
| notes | string ≤ 4000 | Anything the designer should know. |
| dimensions | object | heightIn, widthIn, lengthIn, weightLb as numbers. |
| photos | string[] ≤ 5 | Data URLs; see Photos below. |
/items/{id}Corrects a received item: a crack found while unpacking, a recount, a move to another bay. Same fields as receive minus receivedAt and photos. Refused with 409 NOT_RECEIVED before receipt.
/items/{id}/photosAppends photos. Body { "photos": [dataUrl, …] }, up to 5 per call and 10 per item. Returns 201 with the item.
/items/{id}/deliverMarks a received item delivered to the client. 201 the first time, 200 after, keeping the original deliveredAt. Refused with 409 NOT_RECEIVED before receipt.
| Field | Type | Meaning |
|---|---|---|
| deliveredAt | date | Defaults to now. |
| signedBy | string ≤ 200 | Who accepted it. |
| notes | string ≤ 4000 | Where it was placed, anything left to do. |
| photos | string[] ≤ 5 | Proof-of-delivery photos. |
Photos
Photos travel inside the JSON body as base64 data URLs: data:image/jpeg;base64,…. PNG, JPEG and WebP are accepted, 4 MB each after decoding, 5 per request, 10 per item. The bytes are checked, not just the declared type. A request body can be up to 25 MB.
import { readFile } from "node:fs/promises";
const bytes = await readFile("dock-photo.jpg");
const dataUrl = "data:image/jpeg;base64," + bytes.toString("base64");
await fetch(BASE + "/items/" + id + "/photos", {
method: "POST",
headers,
body: JSON.stringify({ photos: [dataUrl] }),
});Errors
Errors are JSON: { "error": "message", "code": "CODE" }. Validation failures add a details array naming the field.
| Field | Type | Meaning |
|---|---|---|
| 401 UNAUTHENTICATED | No key, or a key that does not exist. | |
| 401 KEY_REVOKED / KEY_EXPIRED | The designer revoked the key, or it passed its expiry. | |
| 403 INSUFFICIENT_SCOPE | A read-only key tried to write. | |
| 403 HTTPS_REQUIRED | Plain HTTP request. | |
| 404 ITEM_NOT_FOUND | Not an item on this account. | |
| 400 Validation failed | Unknown field, bad enum value, string too long, bad date. | |
| 400 BAD_IMAGE / 415 UNSUPPORTED_TYPE / 413 TOO_LARGE | A photo was not a real image, not PNG/JPEG/WebP, or over 4 MB. | |
| 409 NOT_RECEIVED / ALREADY_DELIVERED / TOO_MANY_PHOTOS | The call does not fit the item’s current state. | |
| 429 RATE_LIMITED | Slow down; wait for Retry-After. |
Security
- One key per receiver, named after them, so a revocation affects only that receiver and the activity log says who did what.
- Secrets are random, 40 characters, shown once, and stored only as a SHA-256 hash. Qurate staff cannot recover a lost key.
- A receiver that only needs the expected list can be given a read-only key.
- Keys can carry an expiry for a short engagement; for a standing partner, the designer revokes and reissues when staff change.
- Every change made through the API is logged with the key, the time and the caller's address, and appears on the designer's activity feed.
- The API exposes product names, images, PO numbers and the project and client names needed for delivery. It never exposes prices, vendors, source links or client contact details.
Building something the API does not cover yet? Write to support@quratedesigns.com.