Skip to main content

Developers and Partners

If you are here to integrate with CO2 TRUST systems (APIs, deployment architecture, contract references, subgraph access), use our technical documentation as the primary source:

What this site covers​

This public documentation site focuses on:

  • Mission and environmental outcomes
  • Partner collaboration and impact workflows
  • Plain-language product and marketplace concepts

What api-docs.co2trust.earth covers​

The technical documentation site is where we maintain implementation details for engineers and technical partners, including:

  • Architecture and service boundaries
  • Deployment and infrastructure notes
  • API references and integration patterns
  • Smart contract and subgraph references

Integration readiness notes​

Some integration documents are currently being upgraded from internal-operator guidance to external partner guidance. During that transition:

  • Treat API details as subject to environment-specific validation.
  • Use published status labels (Planned, In progress, Shipped) when evaluating features.
  • Contact the CO2 TRUST team for partner onboarding requirements.

Account setup and handoff (partner summary)​

Current account bootstrap and API session behavior are implemented in CO2 TRUST backend services and documented in the technical docs.

High-level model:

  • CO2 TRUST currently uses one backend endpoint to create-or-authenticate an account.

  • That endpoint is called from trusted server infrastructure, not directly from browser clients.

  • The response includes a bearer token used for user-scoped API routes.

  • For implementation details, start with:

  • Browser integrations should not handle privileged backend-secret headers directly.

  • Partner account handoff patterns (redirect, popup session, future federation) are being documented as phased integration options.