Technical Onboarding¶
This guide describes the three integration points you need to implement as a Refurbisher to connect with the iUsed Refurbisher Portal (IRP).
Integration overview¶
Direction: Your system iUsed
You provide an HTTP endpoint that returns your current offer feed as a JSON response body. iUsed will poll this endpoint periodically.
| Method | GET |
| Provided by | You (Refurbisher) |
| Format | JSON |
| Auth | To be agreed during setup |
Minimum required fields per offer:
| Field | Description |
|---|---|
sku |
Your unique product identifier |
name |
Product name |
ean |
EAN/barcode |
stock_available |
Available stock quantity |
price_purchase_amount |
Purchase price (excl. VAT) |
price_consumer_amount |
Consumer price (excl. VAT) |
Alternative: sFTP
If an HTTP endpoint is not feasible, iUsed can provide an sFTP location as an alternative.
Direction: iUsed Your system
You provide an HTTP API endpoint where iUsed submits new orders. When a customer places an order at iUsed, your endpoint is called almost immediately.
| Method | PUT, POST, or PATCH |
| Provided by | You (Refurbisher) |
| Format | JSON in request body |
Expected response:
Your endpoint must return the external Order ID (your own order reference) in the JSON response body. iUsed uses this to link future shipment updates to the correct order.
Direction: Your system iUsed
Once an order is shipped, you send a shipment update to the iUsed webhook endpoint. iUsed will provide you with a unique, secure URL during onboarding.
| Method | POST, PUT, or PATCH |
| Provided by | iUsed |
| URI pattern | /webhook/shipment/{supplier_id}/{secure_token} |
Example endpoint:
POST https://portal.iused.nl/webhook/shipment/18/XXXXXXXXX-SECURE-TOKEN-XXXXXXXXX
Required fields in the JSON body:
| Field | Description |
|---|---|
| Serial number / IMEI | Device identifier |
| Track & trace | Carrier tracking reference |
| External Order ID | Your order reference, as returned when the order was placed |
Secure Token
The secure_token in the URL is unique per Refurbisher and is shared securely via 1Password. Do not share it publicly.
Next steps¶
Once you have reviewed this guide, please share your technical capabilities with the iUsed team so we can align on the implementation details.