Refurbed
Refurbed is a European online marketplace for professionally refurbished electronics and other sustainable goods, headquartered in Vienna, Austria and operating across Europe. Merchants sell refurbished phones, laptops, tablets, wearables and more to consumers through the refurbed platform, and refurbed exposes public partner APIs so merchants and affiliates can integrate programmatically. The Merchant API lets sellers manage offers, prices, stock, orders, returns, refunds, shipping profiles, tickets and buyback flows, while the Affiliate Partner API exposes the marketplace catalog (markets, products, instances and BuyBox data) for affiliates. Both APIs are offered as gRPC with an equivalent HTTP/JSON transport, defined by published Protobuf and OpenAPI (Swagger 2.0) specifications, and are authenticated with a secret token passed in the Authorization header.
Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.
API Evangelist profiles Refurbed the way a machine reads it — 22 machine-readable artifacts across 18 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Refurbed scores 31.4/100 (thin), with a separate agent-readiness read of 58/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Refurbed
Each block below is one kind of artifact we hold for Refurbed. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 18
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Refurbed BuybackBidService API
The BuybackBidService API from Refurbed — 8 operation(s) for buybackbidservice.
Refurbed BuybackOrderItemService API
The BuybackOrderItemService API from Refurbed — 6 operation(s) for buybackorderitemservice.
Refurbed BuybackOrderService API
The BuybackOrderService API from Refurbed — 1 operation(s) for buybackorderservice.
Refurbed BuybackProductService API
The BuybackProductService API from Refurbed — 1 operation(s) for buybackproductservice.
Refurbed BuybackSupplyboxService API
The BuybackSupplyboxService API from Refurbed — 1 operation(s) for buybacksupplyboxservice.
Refurbed CatalogService API
The CatalogService API from Refurbed — 1 operation(s) for catalogservice.
Refurbed CurrencyService API
The CurrencyService API from Refurbed — 2 operation(s) for currencyservice.
Refurbed InstanceService API
The InstanceService API from Refurbed — 4 operation(s) for instanceservice.
Refurbed MarketOfferService API
The MarketOfferService API from Refurbed — 10 operation(s) for marketofferservice.
Refurbed MarketService API
The MarketService API from Refurbed — 4 operation(s) for marketservice.
Refurbed MerchantService API
The MerchantService API from Refurbed — 4 operation(s) for merchantservice.
Refurbed OfferService API
The OfferService API from Refurbed — 9 operation(s) for offerservice.
Refurbed OrderItemReturnService API
The OrderItemReturnService API from Refurbed — 1 operation(s) for orderitemreturnservice.
Refurbed OrderItemService API
The OrderItemService API from Refurbed — 8 operation(s) for orderitemservice.
Refurbed OrderService API
The OrderService API from Refurbed — 13 operation(s) for orderservice.
Refurbed ProductService API
The ProductService API from Refurbed — 2 operation(s) for productservice.
Refurbed ShippingProfileService API
The ShippingProfileService API from Refurbed — 6 operation(s) for shippingprofileservice.
Refurbed TicketService API
The TicketService API from Refurbed — 10 operation(s) for ticketservice.
Scroll within the panel for all 18 ·
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
refurbed-mcp.yml
MCP SERVERRate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Refurbed Rate Limits
RATE LIMITSSecurity Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Resources
Every other property we hold for Refurbed — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 1
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 3
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 5
Pagination, idempotency, versioning, errors, and events
Build 3
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Company 1
The organization behind the API
Other 3
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/refurbed · machine-readable index on apis.io