As Blackhawk Network continues to develop the current version of our APIs, we will announce changes on this page. Unless stated otherwise, all changes are backwards compatible (e.g. new endpoint, new optional request parameter). We avoid making backwards incompatible changes whenever possible and make every effort to communicate these changes to our customers and partners before they are released.
There are currently no feature releases scheduled.
- Support for specifying which financial account should be used when placing an order by sending the financialAccountId (FAID).
The following items were added with the February deploy:
- Support for Additional Shipping Methods
- New Closed Loop Activation API
eGiftBulkCodeRetrievalInfo/byKeys API now returns the eGift card number when the original order was made with
Blackhawk Network has removed support for TLS 1.1.
Read the full announcement for more information
The OrderInfo API will no longer respond with an
order.not.found error when the order request is processing but an order has not yet been created in Hawk Marketplace. It will now correctly respond with an "In Process" response.
deliveryAddress object will be modified to add following two mandatory attributes:
This will affect calls to the following endpoints:
Requests made to these endpoints after this date that do not include
lastName will fail.
Additional Performance Improvements for Real-time Ordering to further reduce the response times when ordering digital content through the real-time API endpoints.
We will be moving some internal processes to be asynchronous in order to reduce the response times when ordering digital content through the real-time API endpoints.
We have made some updates to the error messaging returned for real-time orders that fail fraud checks to allow internal resources to more quickly identify the failure reason.
Updated about 1 year ago