Skip to main content

27 posts tagged with "release"

View All Tags

Sales Channel Services API v1.65.0

· One min read
Puro.earth Releases
Puro.earth Releases
The Puro.earth Release Team

Bug Fixes

  • Fixes a bug in the GET /saleschannel-services/production-facilities/{productionFacilityId}-endpoint, which would return an HTTP 500 response when no Production Facility with the given ID would exist. Now instead, the endpoint will return an HTTP 404 response.

Sales Channel Services API v1.63.0

· One min read
Puro.earth Releases
Puro.earth Releases
The Puro.earth Release Team

Features

  • Adds an endpoint, GET /saleschannel-services/production-facilities/{productionFacilityId}, which lists information for a given production facility.
  • Adds an endpoint, GET /saleschannel-services/suppliers/{supplierId}, which lists information for a given supplier.

Sales Channel Services API v1.62.0

· One min read
Puro.earth Releases
Puro.earth Releases
The Puro.earth Release Team

Features

  • Adds the createdAt field to transactions, which contains the date when the transaction has been registered.
  • Adds the completedAt field to transactions, which will contain the date when the transaction has been completed when the transaction is successfully processed.
  • Adds the publicRetirementStatementUrl field to transactions of type retirement, which contains a link to the publicly available retirement statement when it becomes availabe.

Sales Channel Services API v1.60.0

· One min read
Puro.earth Releases
Puro.earth Releases
The Puro.earth Release Team

Features

Bug fixes

  • Prevents the Trader Onboarding Proposals (TOP) listing endpoint GET /saleschannel-services/trader-onboarding-proposals from erroring when the account-holder information of one of the TOPs is not available. Instead, we will filter out the TOPs for which the account-holder information is not available.
  • Fixes a bug where the GET /saleschannel-services/transactions endpoint would return 0 instead of null as the unitPrice for transactions which do not have a monetary value. Now, if no monetary value is involved in this transaction, we will always return null as the unitPrice.