Data products

Banks, unions, public bodies and large enterprises can take Birlesa's aggregated datasets in bulk, under contract. Every product is built from data the platform already publishes or aggregates under its own rules. Nothing finer or more personal is delivered than what those rules allow.

Product	Records	New records
`price-index`	Monthly prices per HS heading, base unit and currency: median, quartiles, a band for the number of prices, change from the previous month (methodology)	monthly
`demand-forecasts`	Per HS heading and destination: monthly demand counts and backtested three-month forecasts with 80% bands (methodology)	monthly
`b2b-index`	The monthly B2B index: formations, capital increases, liquidations, closures, konkordato, tenders and matches, nationally, per province and per NACE division	monthly
`new-companies`	Companies of corporate forms founded in the last 90 days, from official registry notices	daily

GET /v1/data/products lists them with each record's fields. Fields are only added, never changed or removed, within /v1.

Access

A contract is signed. Birlesa records it as a grant for your organization and one product. A second Birlesa administrator approves it; only then does it open.
Your organization's owners and admins see its grants: GET /v1/orgs/{org_id}/data-grants.
Issue an API key (or OAuth client) with the data:read permission.
Read the product:

GET /v1/data/products/price-index/records?since=2026-01 HTTP/1.1
Host: api.birlesa.com
Authorization: Bearer brl_api_...

The answer is JSON lines (application/x-ndjson), oldest first. When there is more, the Birlesa-Next-Cursor header holds the cursor for the next page (&cursor=...). Feeds allow 6 requests a minute per key; fetch monthly products once after they are published (the 5th and 6th of each month), and the daily one once a day.

Access reviews

Every grant is reviewed at least every 90 days: is the contract still in force, is the data used as agreed, do the right people hold the keys? A grant whose review is overdue stops working on its own until the review is done; requests then get 403 with code no_live_grant. Every read is recorded against the contract.

Errors

Code	Meaning
`no_data_read` (403)	The key lacks the `data:read` permission
`no_live_grant` (403)	No approved, current, reviewed grant for this product
`bad_cursor` (400)	The cursor is not one the feed gave