Skip to content
Changelog

Week of September 28, 2026

10 changes to the Flint API, SDKs, and docs, newest first, from September 28, 2026 to October 4, 2026. The newest changes are on the changelog.
  • API

New in the API: week of September 28, 2026#

102 additions across Gift cards, Customer account, and 18 more areas. These are additions, so nothing you already use needs to change.

Related: Codes for saved details default to the auto channel, Delivery choice groups name their method types, Delivery quotes name required recipient fields before an address, Delivery recipient details are checked at payment, Quotes offer delivery and pickup windows only while they can be chosen, Exact ZIP codes match verified addresses, Pickup search takes the buyer's current choice and lists stores that track no inventory, Request bodies up to 1 MiB, State conditions match the state a buyer sends

Gift cards
22 additions
Customer account
11 additions
Orders
19 additions
Products
7 additions
Refunds
6 additions
Subscriptions
6 additions
Webhooks
6 additions
  • Values

    gift_card_load.createdgift_card_load.updatedgift_card_notification.createdgift_card_notification.updatedgift_card_redemption.createdgift_card_redemption.updated

  • Values

    gift_card_load.createdgift_card_load.updatedgift_card_notification.createdgift_card_notification.updatedgift_card_redemption.createdgift_card_redemption.updated

  • Values

    gift_card_load.createdgift_card_load.updatedgift_card_notification.createdgift_card_notification.updatedgift_card_redemption.createdgift_card_redemption.updated

  • Values

    gift_card_load.createdgift_card_load.updatedgift_card_notification.createdgift_card_notification.updatedgift_card_redemption.createdgift_card_redemption.updated

  • Values

    gift_card_load.createdgift_card_load.updatedgift_card_notification.createdgift_card_notification.updatedgift_card_redemption.createdgift_card_redemption.updated

  • Values

    gift_card_load.createdgift_card_load.updatedgift_card_notification.createdgift_card_notification.updatedgift_card_redemption.createdgift_card_redemption.updated

API keys
3 additions
  • Values

    commerce.gift_cards.adjustments.writecommerce.gift_cards.readcommerce.gift_cards.redemptions.writecommerce.gift_cards.secrets.writecommerce.gift_cards.write

  • Values

    commerce.gift_cards.adjustments.writecommerce.gift_cards.readcommerce.gift_cards.redemptions.writecommerce.gift_cards.secrets.writecommerce.gift_cards.write

  • Values

    commerce.gift_cards.adjustments.writecommerce.gift_cards.readcommerce.gift_cards.redemptions.writecommerce.gift_cards.secrets.writecommerce.gift_cards.write

Checkout sessions
3 additions
Reports
2 additions
Returns
2 additions
Delivery previews
1 addition
Delivery selections
1 addition
  • Field

    Inputs this selection still needs before payment: each destination_address member a chosen shipment or local delivery needs that the stored address lacks (line1, city, and country, plus state and postal_code in the US), and each recipient field a chosen option requires that the selection does not include.

Demo sessions
1 addition
  • Values

    commerce.gift_cards.adjustments.writecommerce.gift_cards.readcommerce.gift_cards.redemptions.writecommerce.gift_cards.secrets.writecommerce.gift_cards.write

Merchants
1 addition
Payment links
1 addition
Return inspections
1 addition
Settings
1 addition
Webhook events
7 additions
Errors
1 addition
  • Breaking change
  • API
  • Checkout

Codes for saved details default to the auto channel#

POST /v1/checkout-sessions/{checkout_session_id}/customer-verifications with purpose set to use_saved_payment_methods and no channel now uses "channel": "auto", which hosted checkout sends as the buyer types their email. Flint sends the code the way the buyer saved their details:

  • Details saved with a mobile phone number: Flint texts the code to that number, and the response has "channel": "sms" and phone_last_digits.
  • Details saved only by email: Flint emails the code, and the response has "channel": "email".
  • No saved details, or a cap reached: Flint sends nothing and returns 409 with CUSTOMER_VERIFICATION_NOT_SENT.

Breaking: until this release, a request without a channel emailed the code and answered the same whether or not the email had saved details. To keep that answer, send "channel": "email". A channel sent as an empty string or null now returns 400; leave the field out to use the default.

save_payment_method still defaults to email, and confirm_saved_payment_method still requires a channel. See Recognize a returning buyer.

  • API
  • Delivery
  • Checkout

Delivery choice groups name their method types#

A buyer-authenticated delivery quote showed how a choice group could be delivered only through its options, and a group has no options until the buyer gives what its methods need, such as an address. A checkout that offers only local delivery could not tell that from a shipping checkout until then.

  • Choice groups list method_types. The values are shipment, pickup, and local_delivery, each listed once, in the order the methods display. The field is on quotes, on the session's fulfillment, and in merchant-authenticated responses.
  • A type stays listed while its methods need input or cannot serve the current input, so a page can name what does not reach the buyer. options lists what the buyer can choose now.
  • A method whose type the group's items do not allow is left out. The list is [] when no method can serve the group.

See Build your own checkout.

  • API
  • Delivery
  • Checkout

Delivery quotes name required recipient fields before an address#

A quote listed a method's required recipient fields in input_requirements only once the method had an option. Before the buyer gave an address, a local delivery that needs the recipient's phone listed only the address, although the checkout session named recipient.phone before any quote existed. An Apple Pay or Google Pay sheet opened from that quote did not ask for a phone, so payment then failed with DELIVERY_RECIPIENT_REQUIRED.

  • A method waiting on the buyer's address or store lists the recipient fields it requires, with purpose selection, next to the quote requirement for the address. The same applies while the buyer must correct an address Flint could not use.
  • Those requirements name the method's choice group and have no delivery_option_ids. A quote that prices the method lists the requirement for its option instead, as before.
  • A method that cannot serve a usable address lists none. A choice group's own input_requirements still lists only what the group needs before it can be priced.

The change applies to delivery quotes, the checkout session's fulfillment, and delivery previews. See Delivery quotes.

  • API
  • Delivery
  • Checkout

Delivery recipient details are checked at payment#

Selecting a delivery option no longer fails when the recipient is missing a field the option requires, such as a phone for local delivery. Apple Pay and Google Pay reveal the buyer's name and phone only after the buyer approves the payment sheet, so a wallet flow can now select delivery from the partial address first and add the recipient afterwards.

  • Delivery selections carry input_requirements. Each entry is a required recipient field the selection is still missing, with the same delivery_input_requirement_id the quote gave that option. It is [] when nothing is missing.
  • Paying the order returns 400 DELIVERY_RECIPIENT_REQUIRED while a required field is missing, before any payment is attempted. param names the first field, such as delivery_selection.recipient.phone, and remediation.missing_or_invalid_fields lists all of them.
  • To add the fields, select the same choices from the same quote with the full recipient, and send the current selection's ID as expected_delivery_selection_id. The price does not change.

A malformed email or phone you do send is still rejected when you select, with DELIVERY_REQUEST_INVALID. An integration that sends the required fields when it selects sees no difference. If yours counted on the selection rejecting a missing field, read input_requirements after selecting, or handle DELIVERY_RECIPIENT_REQUIRED from POST /v1/orders/{order_id}/pay. See Delivery selections.

  • API
  • Delivery
  • Checkout

Quotes offer delivery and pickup windows only while they can be chosen#

A schedule_window method offers its windows in each option's offered_windows. Until this release a quote also offered the part of a window already under way, starting and expiring at the moment of the quote, so choosing it failed with DELIVERY_WINDOW_EXPIRED. A window could also be chosen until it started, whatever the method's preparation_lead_time_seconds.

  • Every offered window can be chosen. A window's expires_at is preparation_lead_time_seconds before it starts, or the same-day cutoff when that is earlier, and a quote offers only windows whose expires_at is still ahead. With no lead time, a window can be chosen until it starts.
  • A window already under way is not offered. The first window is the next one the lead time allows, so start_at and end_at are always the times you configured.
  • A chosen window ends the selection at its expires_at. Pay before then, or quote and select again.

A method with one long window a day, such as store hours, now offers the next day's window once the day's window has started. To keep taking orders through the day, split it into shorter windows. See Delivery options.

  • API
  • Delivery

Exact ZIP codes match verified addresses#

Address verification returns a full US address with its ZIP+4, such as 07030-5788. Until this release a postal_code condition with an exact value such as 07030 compared the whole code, so it never matched a verified address: a method limited to exact ZIP codes read as outside the delivery area everywhere, while the same codes as prefix values worked. That applied to zones, method eligibility, rate-table when conditions, and pickup searches by buyer_location.

  • A five-digit ZIP code matches the ZIP+4 codes within it. 07030 matches 07030, 07030-5788, and 070305788. This applies to ZIP codes in the US and in US territories, such as Puerto Rico.
  • A ZIP+4 value matches only that ZIP+4. 07030-5788 does not match 07030 or 07030-5789.
  • Prefixes and other countries are unchanged. A prefix value still matches every code that starts with it, and codes outside the US compare whole, in uppercase without spaces or hyphens.

Check any method that excludes ZIP codes with not. An address in an excluded five-digit ZIP was not excluded before when verification returned its ZIP+4. It is now. See Delivery configuration.

  • API
  • Delivery
  • Checkout

Pickup search takes the buyer's current choice and lists stores that track no inventory#

Superseded by Delivery inputs use request paths and pickup uses inventory_unavailable.

POST /v1/checkout-sessions/{checkout_session_id}/query-pickup-availability had two problems that left buyers without stores to choose from.

  • The search takes the current delivery selection. A search that sent the checkout's current expected_delivery_selection_id returned 409 DELIVERY_PICKUP_AVAILABILITY_CHANGED, and only a search that named no selection answered, so a buyer who had chosen a store could not look for another. The search now compares the ID with the selection GET .../delivery-selections/current returns, like quote creation does, and does not change the choice. Send null only when the checkout has no selection: naming none while one is current now returns the same 409.
  • Stores without inventory allocation are listed. The search left out every store whose inventory.allocation_status was not active, although quote creation priced pickup at those stores for items without tracked inventory. A store now needs allocation only to supply items with tracked inventory. For those items, a store without it is listed with an unavailable outcome and inventory_insufficient, and merchant-authenticated searches name it in merchant_diagnostics with PICKUP_LOCATION_INVENTORY_UNAVAILABLE.

See Delivery configuration.

  • API
  • Errors

Request bodies up to 1 MiB#

Until this release a request body over 8 KB was refused before it reached the API. The response was an HTML 403 Forbidden page with no request_id, so an order with a few dozen line items or a delivery method with a week of hourly windows could not be created.

  • Bodies up to 1 MiB (1,048,576 bytes) are accepted. This is the limit on every endpoint unless its reference names a lower one.
  • A larger body returns 413 in the standard error envelope, with type set to invalid_request_error, code set to REQUEST_BODY_TOO_LARGE, and a message that states the limit. REQUEST_BODY_TOO_LARGE replaces RESOURCE_LIMIT_EXCEEDED as the code for an oversized body.
  • Split a larger write into several requests. For example, create an order with its first line items and add the rest with POST /v1/orders/{order_id}/line-items.

See Error handling.

  • API
  • Delivery

State conditions match the state a buyer sends#

state conditions store ISO 3166-2 codes such as US-NY, while buyers, address forms, Apple Pay, Google Pay, and address validation send the state as NY. Until this release Flint compared the two as written, so a state condition matched only a state sent as US-NY, and address validation rewrites that to NY for a full address. That applied to zones, to method eligibility, to rate-table when conditions, and to pickup searches by buyer_location.

  • Matching reads the address's state as a subdivision of its country. NY, ny, US-NY, and New York in a US address all match US-NY. Outside the US and Canada, send the subdivision code, with or without the country prefix. A state that names no subdivision of the address's country matches no state condition.
  • Conditions accept two-letter US and Canadian codes. Send NY or ON and Flint stores US-NY or CA-ON, so reads return the ISO 3166-2 code. NY and US-NY in the same list are rejected as duplicates. Other countries still need the full code, such as DE-BY.

Check any method that excludes states with not. A zone such as "the US but not US-AK or US-HI" excluded no one before, so its methods were offered in Alaska and Hawaii. They no longer are. See Delivery configuration.