Credit actions
All available credit actions.
Last updated
All available credit actions.
Last updated
reason
: Must be one of the following predefined options:
Compliance
Corsia
Voluntary purposes
Overall mitigations of global emissions
Corporate emission compensation
Other
Article 6.2
Testing
For transferring credits this is THE endpoint to use. You can transfer credits from an organization, user or subaccount.
/v1/transfer
The entity that holds the credits - if not a subaccountId the default subaccount will be used.
123e4567-e89b-12d3-a456-426614174000
An optional transaction comment
Transfer 2024
The credits to transfer
An optional list of emails to send the transaction receipt to
["info@carbonregistry.com"]
The receiver's information.
If the entity Id is supplied (user / org / subaccount) then the credits are sent to the corresponding account for that id.
If you want to deliver the credits to some address on Polygon you can use the publicKey address and leave the id undefined.
Finally if you are unsure if the receiver of the credits own's a carbonregistry.com account you can pass in the receiver's email, the credits will be sent to an escrow account that stores the credits until the owner of the email signs in and claims the credits.
For retiring credits this is THE endpoint to use. You can retire credits from an organization, user or subaccount.
/v1/retire
The entity that holds the credits
123e4567-e89b-12d3-a456-426614174000
The reason for retirement. This reason comes from a specified picklist.
Corsia
The beneficiary for the retirement
Beff Jezos
A retirement comment
Retiring for flights 24'
An optional list of emails to send the transaction receipt to
The receiver information
The credits to transfer