Skip to content Docs index for AI agents (llms.txt)

DevelopersAPI

API

Browse the device catalog and create and update customers with the Repender API.

Updated 2 min read

Connect your own software to Repender. The API gives access to the device catalog on the Plus and Pro plans, and to your customers on the Pro plan.

All endpoints start with:

text
https://repender.nl/api/v1

Authentication

Every request needs an API token. Open Settings, then API access, to create a token, and revoke it when you no longer need it. The page also lists the AI tools that connected with OAuth.

With Plus, the API gives access to the device catalog: brands, device types and devices. With Pro, you can also read, add and change customers.

Send the token in the Authorization header, and ask for JSON:

bash
curl https://repender.nl/api/v1/device-types \
  -H "Authorization: Bearer YOUR_API_TOKEN" \
  -H "Accept: application/json"

Responses are always in English.

Shop context

Every request works on one shop. If your organization has one shop, Repender uses it. With more than one shop, send shop_id with every request: as a query parameter for GET, or in the request body for POST and PUT.

Rate limit

You can send 60 requests per minute. Above that, the API answers with 429 Too Many Requests.

Pagination

List endpoints marked as paginated return 25 items per page by default. Use page and per_page (up to 100) to page through the results. The response contains the items in data, plus current_page, last_page, per_page, total, next_page_url and prev_page_url.

Endpoints

Endpoint What it does Plan
GET /device-types List device types. Plus and Pro
GET /brands List brands. Plus and Pro
GET /devices List devices. Plus and Pro
GET /customers List customers. Pro
POST /customers Create a customer. Pro
PUT /customers/{id} Update a customer. Pro

Errors

Status Meaning
401 The token is missing or not valid.
403 The token is not an API token, your plan does not include this endpoint, or the shop_id is not one of your shops.
404 The customer does not exist.
422 The request is not valid, for example an unknown device_type or brand slug, or a missing shop_id when your organization has more than one shop. The response contains a message, and for invalid fields an errors object per field.
429 Too many requests. See rate limit.