Skip to main content

BIDEX product feed

The BIDEX API exposes Belgian Cycling Factory bicycle product data in the BIDEX BikeData V1.6 structure. It is a read-only product feed: one request returns the bicycle variants that are linked to your customer-specific price list.

BIDEX (Bike Data Exchange) is a product data standard for the European bicycle industry. It defines a fixed set of field names, code systems (bidex-* fields) and a fixed CSV column order, so that different suppliers and trade platforms can exchange bicycle data in a uniform way.

The endpoint​

There is one BIDEX endpoint:

GET https://connections.cyclingfactory.be/api/v1/bidex/products
  • GET means the feed only downloads information. It never changes products, prices or stock.
  • One record normally represents one sellable variant: a particular model, colour and frame size.
  • The result only contains bicycles that have an applicable customer price for your account.

What you need​

Ask your Belgian Cycling Factory contact for:

  1. An API key — a private access code. Keep it secret.
  2. Your BuyersID — the unique ID of your customer account, formatted as a UUID, for example 123e4567-e89b-12d3-a456-426614174000.

See Authentication for how to send the key, or go straight to Getting started for a step-by-step first request.

Response formats​

You can download the feed in two formats:

FormatBest forWhat you receive
json (default)Automated integrationsA catalog metadata block plus a paginated list of product records using BIDEX field names
csvExcel, manual review, imports into business softwareA semicolon-separated file with the fixed 153-column BIDEX BikeData column order. A CSV download is always the complete catalog; pagination parameters are ignored

Details: Response formats and the full field list in Data fields.

Reference documentation​

Support​

For credentials, access or persistent errors, contact your Belgian Cycling Factory representative or ict@cyclingfactory.be. When reporting a problem, share the date and time, the request address with the BuyersID removed, the HTTP status code and the request ID — but never the API key.

Keeping this page accurate

This documentation describes the endpoint implemented in connections-backend. It was last verified against the implementation on 1 October 2026.