JSON contracts
Consistent responses and machine-readable schemas.
Enterprise API · OpenAPI 3.1
Travel data, built to verify.
Review the prepared, versioned contract for source-backed emission factors, aggregate planning metrics and signed Trip Carbon Passports before the API launch.
Editorial review
OPENAPI 3.1Download OpenAPI
The API is not publicly reachable during the website-first launch. Its contract and endpoints are documented; the download and live explorer will activate with the API launch.
01
01 · Quickstart
Prepare an integration.
Public v1 is intentionally simple: HTTPS, JSON, no SDK dependency and no credentials for open-data operations.
No public API key
Read-only data and verification operations are credential-free.
Signed evidence
HMAC integrity checking of a calculation record, not evidence of completed travel.
cURL
curl https://farleda.eu/api/public/v1/modes.json02
02 · API explorer
Review the prepared contract.
Choose a documented operation and inspect its request and cURL example. Live requests and demo passports will activate with the API launch.
Public v1 endpoints
GET/api/public/v1
API index
Capabilities, licence and operating policy.
cURL
curl https://farleda.eu/api/public/v1Response
After API release, a submitted request’s response appears here.03
03 · Operations
Predictable by design.
The public contract is built for integration governance, edge caching and deterministic verification.
Authentication
Public v1 data and passport verification require no credentials. Private enterprise access and tenant isolation need separate agreement and review before integration.
Rate limits
Cached GET data has no application-level limit. Demo issuance and verification are limited to 60 requests per IP per hour.
Caching
Data endpoints publish explicit shared-cache directives. Passport endpoints use no-store.
Errors
Transport errors use HTTP status codes. A valid verification request returns HTTP 200 and communicates signature validity through valid.
04 · Governance
A contract your review team can inspect.
- Breaking changes require a new major API path.
- Every factor response carries source and methodology context.
- The OpenAPI file is the canonical machine-readable contract.
- Aggregate counters are not demonstrated environmental impact. Small groups and possible inference need a separate privacy review before publication.
