27 posts tagged with "release"

Initial release​

The MyPuro API provides a machine-to-machine interface for credit management use cases in the MyPuro Portal.

• Account Holders: Access account holder information
• Accounts: Retrieve account details and CORC inventory of the accounts
• Transactions: Create retirements, transfers, and view transaction history
• Access Management: Granular control over API access to resources (feature available in the MyPuro Portal)
• Access Sharing: Granular control over sharing API access to your resources for other organizations (feature available in the MyPuro Portal)

Please refer to the MyPuro API documentation for more details on how to use the API.

First release​

The Registry API provides a machine-to-machine interface for data synchronization from the Puro.earth Registry. It enables programmatic access to carbon removal certificates, transactions, and related data.

• Production Facilities: Access data on Puro.earth certified carbon removal facilities
• Transactions: Retrieve issuances, transfers, and retirements
• Certificates: Fetch information about currently active CORCs in the Puro Registry which have not yet been retired
• Methodologies: Access carbon removal methodologies data
• Documents: Retrieve facility and issuance documentation
• Labels: Access additional accreditation information (e.g., ICVCM CCP, CORSIA)

Please refer to the Registry API documentation for more details on how to use the API.

Features​

• Retirements: show the Public Retirement Statement URL in retirementDetails in completed retirements. Please note that there can be a delay of up to 30 minutes when the public retirement statement becomes available in the given URL.
• Transactions: expose the ID of the underlying transaction in the registry as transactionId.

Fixes​

• The service doesn't list a Transaction unless the request goes through to the Registry.
• Improves error message specifity on 400 status codes. The message now includes issues reported by the registry about the request.
• Retirements: fixes an issue on returning a 409 status code when the user retries with the same payload and idempotency key.

Features​

• Create retirements: Adds new field beneficiaryHiddenUntil, which can be used to define when the beneficiary information should become visible in the public registry. By default the value will be set to null, which means that the beneficiary information will be visible publicly at the time the retirement gets registered.

Features​

• Shows all Transactions requested by the Sales Channel in the GET transactions endpoint.

Fixes​

• Improves bundle range validation when creating trades and retirements, and returns a 400 instead a 500 error if the bundle range is invalid.