# Reebelo

> Reebelo is a marketplace for certified refurbished consumer technology — smartphones,
> laptops, tablets, smartwatches, gaming and home electronics — sold by a vetted network
> of third-party refurbishers at up to 70% below new, with a 12-month warranty and a
> 30-day trial. Founded in 2019, it operates in the United States, Australia, New
> Zealand and Singapore.

Reebelo's developer surface is SELLER-FACING, not buyer-facing. There is no public
product, search, or catalogue API for the Reebelo storefront. The only API Reebelo
publishes is the vendor integration API behind its Cobalt back-office, used by
refurbishers who sell on the marketplace to sync offers, pull orders, and return
carrier tracking and IMEI data.

Generated by API Evangelist from Reebelo's public developer surface on 2026-08-26.
This file is an independent third-party summary; it is not published by Reebelo.

## API

- [Reebelo Vendor Integration API (Cobalt)](https://cobalt.reebelo.com/documentation/custom-api):
  REST over JSON. Production base URL https://a.reebelo.com, staging https://a.reebelo.blue.
  Authenticated with a Reebelo-issued static `x-api-key` request header.

### Operations

- `GET sockets/offers` — list the vendor's offers. Query: `page` (default 1),
  `pageSize` (default 20, max 50).
- `GET sockets/offers?search={sku}` — retrieve one offer by the vendor's SKU.
- `POST sockets/offers/update` — create or update offers. Body
  `{"data":[{"name","sku","price","stock","minPrice"}]}`. `sku` required always;
  `name` required on create; `price`/`stock`/`minPrice` optional. Response partitions
  every submitted SKU into `updatedOffers`, `skippedOffers` (reason `unchanged` or
  `vendor_deactivated`) and `failedOffers` (reason `internal_error`), plus a
  `requestId` for support escalation.
- `GET sockets/orders` — list orders. Query: `page`, `pageSize`, `sortBy`
  (`orderDate-desc` default, `orderDate-asc`, `fulfillmentDate-desc`,
  `fulfillmentDate-asc`, `dispatchDate-desc`, `dispatchDate-asc`), `from`, `until`.
- `GET sockets/orders?search={orderNumber}` — retrieve one order.
- `PUT sockets/orders/track` — attach carrier and tracking number to an order. Body
  `{"orderNumber","carrier","trackingNumber","lineItems":[{"id","quantity","imeiNumbers"}]}`.
- `PUT sockets/orders/imei` — record IMEI numbers per line item. Body
  `{"orderNumber","lineItems":[{"id","imeiNumbers"}]}`.
- `POST cobalt/orders/{orderNumber}/invoices/upload-url` — mint a presigned URL for a
  seller invoice PDF. Uses `Authorization: Bearer` rather than `x-api-key`. Returns
  `{"signedUrl":"https://..."}`; the caller then `PUT`s the raw PDF bytes to that URL
  with `Content-Type: application/pdf`.

### Events

- Reebelo POSTs each new order to a vendor-hosted HTTP endpoint. The URL is supplied to
  Reebelo out of band — there is no subscription API. The payload is a Shopify Admin
  REST Order document; Reebelo documents it by JSONPath (`$.name`, `$.line_items[]`,
  `$.line_items[].sku`, `$.total_price`, `$.shipping_address`). No signature or
  verification mechanism is published.

### Non-API integration paths

- [Hosted CSV feeds](https://cobalt.reebelo.com/documentation/csv-feed): a vendor hosts
  a product CSV (`sku`, `name`, `stock`, `price`), crawled by Reebelo every 30 minutes,
  and a tracking CSV (order id, carrier, tracking number), crawled daily at 6pm local time.
- Platform connectors with Reebelo-published setup guides:
  [Shopify](https://cobalt.reebelo.com/documentation/shopify),
  [Linnworks](https://cobalt.reebelo.com/documentation/linnworks),
  [Magento](https://cobalt.reebelo.com/documentation/magento),
  [Neto](https://cobalt.reebelo.com/documentation/neto).

## Docs

- [Integration Documentation home](https://cobalt.reebelo.com/documentation/home)
- [Custom API reference](https://cobalt.reebelo.com/documentation/custom-api)
- [Cobalt vendor back-office](https://cobalt.reebelo.com/)
- [Help centre](https://help.reebelo.com/hc/en-us)
- [Terms of Service](https://reebelo.com/policies/terms-of-service)
- [Privacy Policy](https://reebelo.com/policies/privacy-policy)

## Access

- Not self-service. Prospective vendors email support@reebelo.com; an accepted vendor
  receives an `x-api-key` from their Reebelo account manager. There is no free tier, no
  published API pricing, and no developer signup form.

## What Reebelo does NOT publish

An agent should not expect to find these — they were probed and are absent:

- No OpenAPI, Swagger, GraphQL or AsyncAPI document on any Reebelo host.
- No MCP server, and no A2A agent card at `/.well-known/agent-card.json` or
  `/.well-known/agent.json`.
- No `/.well-known/` document of any kind. `cobalt.reebelo.com` answers HTTP 200 with an
  application HTML shell for every `/.well-known/*` path — these are single-page-app
  catch-alls, not documents.
- No SDK or client library on npm, PyPI or RubyGems, and no GitHub organization.
- No rate limits, no rate-limit response headers, and no documented 429 behaviour.
- No changelog, no API version scheme, no deprecation policy and no status page.
- No cancellation or replacement API. Reebelo states plainly: "There is not yet a
  general API integration for cancelations or replacements" — these are resolved by
  direct contact between vendor and Reebelo, and an agent must treat them as
  out of scope.