BeCause API
The BeCause API moves sustainability data between your systems and ours. Certification bodies use it to push certification data in. Marketplaces, OTAs and property management systems use it to map their own property records onto BeCause companies and retrieve the sustainability data attached to them.
Both directions run over the same endpoints. There is no separate API per partner type — what you can read and write is decided by your API key, not by which endpoints you are allowed to call.
Base URL
https://api.because.eco/api/v1/
Requests and responses are JSON over HTTPS.
How the API is shaped
Most of the surface is bulk and asynchronous. It is built for partners sending tens of thousands of properties at a time, so a write does not block until the work is finished — you submit a request, receive a correlation id, and poll for the outcome. Asynchronous processing explains the loop, and it is worth reading before you write any integration code.
A smaller set of endpoints is synchronous and answers immediately. These are the reference-data lookups — frameworks, groups, unit types and custom identifiers — that you need in order to construct a bulk request in the first place.
Where to start
- Getting started — your first successful call, end to end.
- Authentication — how API keys work and what they scope you to.
- Asynchronous processing — the submit-and-poll loop.
- API Reference — every endpoint, grouped by mode and resource.
Getting help
Questions about anything here go to support@because.eco.