{
  "aid": "ducky.eco:ducky-3.0.0",
  "name": "Ducky Data V3 - climate data APIs",
  "type": "Index",
  "description": "Ducky Data's APIs provide footprint data for a wide variety of products and circular services, as well as individuals, and consumption-based emissions for municipalities and other administrative units.\n\nThe endpoints are divided by functionality. \nThe Calculate endpoints compute the footprint of an individual based on their habits and other lifestyle data. \nThe Change endpoint generates climate friendly tips based on the user's habits, and can be used to nudge the user towards sutainable behavioral change.\nThe Compare endpoints return the average footprint of a citizen in a given area (municipality or BSU).\nThe Convert endpoints turn physical data like energy use or transaction amount into climate footprint.\nReporting endpoints are for calculating scope 1 & 2 emissions according to the GHG protocol.\nThe Track endpoints returns the values of indicators (drivers of footprint) for a given area (municipality or BSU).\nThe Translate endpoints contextualize a given quantity of CO2e by expressing them in something more tangible, like a flight trip.\n\nIn the description of each endpoint, you will find the link to a user documentation page detailing the sources and calculation principles.\nAll of our user documentation pages can be found [here](https://support.ducky.eco/en/ducky-insights#introduction-to-ducky-insights).\n\n### Base URL\nThe API is served over HTTPS.\nThe section [API Servers](https://storage.googleapis.com) indicates the base URLs for all requests in the documentation.\n\n### Authentication\nThe API requires [authentication](https://storage.googleapis.com). You have to negotiate an `access_token` and send it with every request, in the `authorization` header.\n\nStep-by-step:\n1. [Email Ducky to request](mailto:api@ducky.eco) a `CLIENT_ID` and a `CLIENT_SECRET`\n2. Negotiate an `access_token` with Auth0\n3. Send authenticated requests to Ducky API\n\nLearn in detail how to negotiate and use an `access_token` in the [Authentication section](https://storage.googleapis.com).\n",
  "url": "https://raw.githubusercontent.com/jentic/jentic-public-apis/refs/heads/main/apis/openapi/ducky.eco/ducky/3.0.0/apis.json",
  "tags": [
    "ducky.eco",
    "ducky"
  ],
  "created": "2026-04-08",
  "modified": "2026-04-08",
  "specificationVersion": "0.19",
  "access": "3rd-Party",
  "maintainers": [
    {
      "FN": "Jentic",
      "X-github": "jentic",
      "url": "https://github.com/jentic"
    }
  ],
  "apis": [
    {
      "aid": "ducky.eco:ducky-3.0.0",
      "name": "Ducky Data V3 - climate data APIs",
      "description": "Ducky Data's APIs provide footprint data for a wide variety of products and circular services, as well as individuals, and consumption-based emissions for municipalities and other administrative units.\n\nThe endpoints are divided by functionality. \nThe Calculate endpoints compute the footprint of an individual based on their habits and other lifestyle data. \nThe Change endpoint generates climate friendly tips based on the user's habits, and can be used to nudge the user towards sutainable behavioral change.\nThe Compare endpoints return the average footprint of a citizen in a given area (municipality or BSU).\nThe Convert endpoints turn physical data like energy use or transaction amount into climate footprint.\nReporting endpoints are for calculating scope 1 & 2 emissions according to the GHG protocol.\nThe Track endpoints returns the values of indicators (drivers of footprint) for a given area (municipality or BSU).\nThe Translate endpoints contextualize a given quantity of CO2e by expressing them in something more tangible, like a flight trip.\n\nIn the description of each endpoint, you will find the link to a user documentation page detailing the sources and calculation principles.\nAll of our user documentation pages can be found [here](https://support.ducky.eco/en/ducky-insights#introduction-to-ducky-insights).\n\n### Base URL\nThe API is served over HTTPS.\nThe section [API Servers](https://storage.googleapis.com) indicates the base URLs for all requests in the documentation.\n\n### Authentication\nThe API requires [authentication](https://storage.googleapis.com). You have to negotiate an `access_token` and send it with every request, in the `authorization` header.\n\nStep-by-step:\n1. [Email Ducky to request](mailto:api@ducky.eco) a `CLIENT_ID` and a `CLIENT_SECRET`\n2. Negotiate an `access_token` with Auth0\n3. Send authenticated requests to Ducky API\n\nLearn in detail how to negotiate and use an `access_token` in the [Authentication section](https://storage.googleapis.com).\n",
      "image": "",
      "baseURL": "https://api.ducky.eco/v3",
      "humanURL": "https://github.com/jentic/jentic-public-apis/tree/main/apis/openapi/ducky.eco/ducky/3.0.0",
      "version": "3.0.0",
      "tags": [
        "ducky.eco",
        "ducky"
      ],
      "properties": [
        {
          "type": "OpenAPI",
          "name": "OpenAPI definition",
          "url": "https://raw.githubusercontent.com/jentic/jentic-public-apis/refs/heads/main/apis/openapi/ducky.eco/ducky/3.0.0/openapi.json",
          "mediaType": "application/openapi+json"
        },
        {
          "type": "GitHubRepo",
          "url": "https://github.com/jentic/jentic-public-apis/tree/main/apis/openapi/ducky.eco/ducky/3.0.0"
        }
      ]
    }
  ]
}