> For the complete documentation index, see [llms.txt](https://changelog.shopwaive.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://changelog.shopwaive.com/posts/quickstart-11.md).

# Shopwaive API keys and export updates

October 4, 2026

The Shopwaive Development team has released an update to the Shopwaive app. There is nothing you need to do: every checkout block, POS tile, Flow action and Flow trigger you already use stays in place, there is no new permission to approve, and requests to the Shopwaive API need no change.

{% hint style="info" %}
Questions about this update? Reach out to our team at <support@shopwaive.com>
{% endhint %}

### Shopwaive API keys

Create a key for each developer or integration. Each key can be revoked on its own, without affecting the others.

1. In the Shopwaive app, open <mark style="color:blue;">**Settings**</mark> > <mark style="color:blue;">**Develop**</mark> > <mark style="color:blue;">**Shopwaive API keys**</mark>
2. Type a label, for example `ERP sync`, and click <mark style="color:blue;">**Create key**</mark>
3. Copy the key. It is shown only once

Send the key in the `X-Shopwaive-Access-Token` header, the same header the API has always used. An integration that already sends an access token in that header keeps working, with no change. Use a key for new integrations. [Learn more](https://api.shopwaive.com/quick-start)

### Exports

Both exports are under <mark style="color:blue;">**Customers**</mark> > <mark style="color:blue;">**More actions**</mark>. [Learn more](https://docs.shopwaive.com/shopify/accounts/export-accounts)

* <mark style="color:blue;">**Export all balances**</mark> now returns every account, including on very large stores
* <mark style="color:blue;">**Export all transactions**</mark> now gives every row the same columns in the same order. A column that does not apply to a row is blank
* The transactions file ends with a new `Figures` column. It says where a row's balances come from: `recorded`, `reconstructed`, `derived` or `not recorded`
* An account that holds a balance but has no history is exported as one **Opening balance** row
* Stores with B2B Checkout on also get `Placed By` and `Funded By` after `Email`

### Balance imports

In <mark style="color:blue;">**Customers**</mark> > <mark style="color:blue;">**Import**</mark>, an `Expiry` written as `YYYY-MM-DD` is read as the start of that day in your local time. An `Expiry` that is today or earlier is refused, and nothing is imported until it is corrected. [Learn more](https://docs.shopwaive.com/shopify/accounts/import-accounts)

### Shopify Flow

When Shopify refuses to create the discount or the gift card, the <mark style="color:blue;">**Create discount**</mark> or <mark style="color:blue;">**Create gift code**</mark> step now fails in Flow and shows the reason. The steps after it do not run.

### Shopify POS and gift cards

* The POS tiles now follow the cart's customer. When you change the customer, the tile shows the new customer's balance
* Gift codes no longer need a custom app or a pasted token. The **Gift Cards Access Token** card has been removed from Settings

### For developers

* Merchant-configured webhooks have been retired, and the **Webhooks** section is no longer shown in Settings. To act on a balance change, use the Shopify Flow triggers <mark style="color:blue;">**Balance change**</mark> and <mark style="color:blue;">**Balance changes from order**</mark>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://changelog.shopwaive.com/posts/quickstart-11.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.