Change log

7. september 2026

Samsetningarafslættir (combo discounts): seljandi getur nú skilgreint í stjórnborðinu að vara fái sjálfvirkan afslátt (prósentu eða fasta upphæð) þegar viðskiptavinur er einnig með aðrar tilteknar vörur — hvort sem þær eru keyptar í sömu pöntun eða eru í öðrum virkum samningi. Afslátturinn er reiknaður sjálfkrafa á hverri innheimtu og fellur niður þegar viðskiptavinurinn hættir með skilyrðisvörurnar.
/api/v2/subscription-offer-quotes/, /api/v2/checkouts/ og checkout-sessions tilboð skila nú combo_discounts listanum með þeim samsetningarafsláttum sem gilda; subtotal_amount, tax_amount, total_amount og recurring_* upphæðir innihalda afsláttinn nú þegar. Tilboðsfyrirspurn (subscription-offer-quotes) tekur nú við valkvæðu customer til að taka tillit til annarra samninga viðskiptavinarins, óháð því hvort afsláttarkóði er sendur.

unit_amount_override (a fixed per-unit item price) is now supported in the V2 item operations on an active contract: items/update, items/add and proration-preview on /api/v2/subscription-contracts/{id}/. Previously the field only worked at contract creation. In items/update, omitting the field keeps the item’s current fixed price, while an explicit null removes it so the item reverts to the catalog price. Proration lines resulting from such a change get the new proration_reason value unit_amount_changed.
The item operation endpoints (items/add, items/update, items/remove, proration-preview and related operations) now reject unknown fields, and fields not supported by the selected operation, with a 400 error instead of silently ignoring them. Integrations that sent extra fields to these endpoints need to remove them. items/update now only accepts the operation value update_item.
Swagger and the documentation have been updated accordingly; see Subscription Contracts V2.

New endpopint /api/subscriptions/{subscriptionId}/set_expiry/ which allows setting the expiry date of a subscription (active_until).

Customers (/api/customers/) now accept and return a phone number (phone) when updated through the API and the Swagger documentation has been updated accordingly.

New endpoint for transactions so it is now possible to fetch lists of transactions and filter them.

It is now possible to supply a payment processor id when creating new checkouts. Before, it was only possible to specify a plan to pick a specific payment processor.
Payment processor information is now supplied when fetching plans.

New API endpoint /api/payments/{uuid}/refund/ that allows refunds for single one-off payments

New subscription values that indicate whether a subscription has been canceled, cancelled and cancel_date.
Discrepancies in Swagger documentation has been fixed according to responses from the web service.

New endpoint /api/webhooks/ which allows users to create and work with web-hooks that can send notifications about events that happen within Áskell.

New endpoint /api/hello/ that confirms that the web-service works and can be used for testing.
amount and discount can now be used as optional variables when a subscription is added to a customer within /api/customers/{reference}/subscriptions/add/

Swagger documentation fixed. GET added to individual payments on the URL https://askell.is/api/payments/{uuid}/.

Users can limit the output that the subscription export delivers by adding the variable ?type=light to the URL. By doing this less data is extracted about the customer and transaction history and is better when exporting a large list of subscriptions for handling. More data can then be extracted on individual subscriptions if needed.

New option has been added when a data on subscriptions or customers is exported. Users can now add the variable ?type=light to the URL to get 100 lines at a time. By doing this the output changes from being a list of transactions to being a list of transactions as results, amount of transactions as count and links to the next and previous page as next og previous. The maximum output is 1000 lines per page.