Find carbon projects by country

Use the Carbonmark API to retrieve available country values and return carbon projects that match a selected country.

This page shows the basic workflow. For full parameter definitions and response schemas, see the API referencearrow-up-right for each endpoint.

Step 1: Retrieve available countries

Call the /countriesarrow-up-right endpoint to return the list of valid country values you can use when filtering carbon projects.

curl --request GET \
  --url https://api.carbonmark.com/countries \
  --header 'Accept: application/json'

Example response (trimmed for readability):

[
  { "id": "Brazil" },
  { "id": "Bulgaria" },
  { "id": "China" },
  { "id": "Congo" },
  { "id": "Ecuador" },
  { "id": "India" }
]

Step 2: Filter projects by country

Once you have a valid country value, pass it to the /carbonProjectsarrow-up-right endpoint.

You can also combine country with other supported filters such as:

  • category

  • vintage

  • project name

  • project description

  • assetPriceType

The assetPriceType filter lets you narrow results to projects with specific pricing sources. Accepted values are listing (seller listings on Carbonmark) and klimaprotocol (Klima protocol pool prices).

The example below returns renewable energy projects in India with a 2012 vintage.

Example response (trimmed for readability):

For many workflows, the key and projectID fields are enough to display results or request full project details.

Step 3: Retrieve a single project by key

If you need the full details for a specific project, call /carbonProjects/{key}arrow-up-right using the project key returned in the search response. You can also filter the returned asset prices by type using the assetPriceType parameter.

Example response (trimmed for readability):

Notes

  • Use /countries first to avoid passing unsupported country values.

  • Use /carbonProjects when you want a filtered list of matching projects.

  • Use /carbonProjects/{key} when you need full details for a specific project.

  • Refer to the API reference for the complete list of supported parameters and response fields.

Last updated