Changelog

  • May 24 2019

    orders-api

    Added the ability for users to specify "fallback bundles" in the product_bundle field using a comma delimited list.

  • May 01 2019

    data-api

    • Exceeding quota when attempting to download will now return with a 403 status code, not 429

    • Authentication should now be properly honored/required on all asset type and item type endpoints, e.g.

      • /data/v1/asset-types
      • /data/v1/asset-types/analytic_range
      • /data/v1/item-types
      • /data/v1/item-types/SkySatScene

  • April 01 2019

    data-api

    • Data API exceptions will now be returned with a 500 status code, not 502

  • September 20 2018

    orders-api

    This is a minor release.

    Notification emails were previously being sent in text/plain format only. They will now be sent in multipart/alternative and include both plaintext and HTML formatting. The original plaintext version of the email is formatted exactly as it was prior to this change.

  • July 16 2018

    orders-api

    This is a minor release with a few user facing changes. Most changes are new and old behavior should not change.

    • Incorrect archive_type results in a validation error. See Zipping Results section of documentation. This is an optional field and if you haven't been setting it, the type will default to zip.
    • You can now specify your webhook callback to be per_order: true. This is an optional parameter and, if omitted, the default behavior will be used whereby you’ll receive a webhook callback per bundle. See the Webhook section of documentation.
    • We have new validation rules on orders to ensure correct type of parameters (you can't use a number in a string field), and cannot specify operations that do not exist.