How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Wren Offset Orders API

Create and list carbon offset orders by tonnage

Wren Offset Orders API is one of 7 APIs that Wren publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Offset Orders. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 4 operations across 3 paths, and defines 6 schemas. It is described by OpenAPI 3.2.0, at version 2026-07-21.

Requests are made against a single base URL, https://www.wren.co.

4 operations 3 paths 6 schemas 3 GET1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2026-07-21
Server
https://www.wren.co
Authentication
HTTP Basic, HTTP Bearer
Terms of Service
Resource Areas
1

Authentication & Security 2

Wren Offset Orders API declares 2 security schemes for authenticating requests. It accepts HTTP basic authentication (basicAuth). It accepts HTTP bearer tokens (bearerAuth). By default, every request must be authenticated.

  • basicAuth — Recommended for curl: pass the API token as the username with an empty password (-u [apitoken]:). Token types: team live token (UUID), team test token (wrentes…
  • bearerAuth — Authorization: Bearer [apitoken] with the same token types as Basic auth.

Paths & Operations 4

Across 3 paths, the API surfaces 4 operations — 3 GET, 1 POST. Each is listed below with its method, path, parameters, and response codes.

Offset Orders 4

Create and list carbon offset orders by tonnage

POST
/api/offset-orders
Create offset orders
createOffsetOrder body → 200400402403
GET
/api/offset-orders
List your offset orders
listOffsetOrders → 200403
GET
/api/offset-orders/public
List public offset orders
listPublicOffsetOrders → 200403
GET
/api/offset-orders/certificate/by-group/{id}
Get the impact certificate for an order group
getOffsetCertificateByGroup 1 param → 200403

Schemas 6

The contract defines 6 schemas that model the data the API accepts and returns. The most detailed are OffsetOrderResponse (8 properties), OffsetOrderRequest (8 properties), Project (7 properties), Portfolio (6 properties). Each schema is shown below with its type and property counts.

OffsetOrder
object
4 properties
Project
object
7 properties
Error
object
1 property
OffsetOrderRequest
object
8 properties 1 required
Portfolio
object
6 properties
OffsetOrderResponse
object
8 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

wren-offset-orders-api-openapi.yml Raw ↑

Other APIs Wren publishes across the network.

Wren Credits API
Wren Portfolios API
Wren Project Donations API
Wren Project Orders API
Wren Purchases API
Wren Tree Orders API
Where this information came from

This is an independent, third-party profile of Wren Offset Orders API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.