sellapp-sdk 0.1.1__tar.gz

sellapp_sdk-0.1.1/LICENSE.txt

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 WorkOS
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in
+all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

sellapp_sdk-0.1.1/NOTICE.txt

@@ -0,0 +1,9 @@
+SellApp SDK
+
+Maintained by SellApp.
+
+This SDK contains software derived from WorkOS oagen and oagen-emitters,
+licensed under the MIT License reproduced in LICENSE.txt.
+
+Upstream source: https://github.com/workos/oagen
+Upstream emitters: https://github.com/workos/oagen-emitters

sellapp_sdk-0.1.1/PKG-INFO

@@ -0,0 +1,178 @@
+Metadata-Version: 2.5
+Name: sellapp-sdk
+Version: 0.1.1
+Summary: Official Python SDK for the SellApp API
+Project-URL: Documentation, https://sell.app/docs/api
+Project-URL: Repository, https://github.com/sellapp/sellapp-python
+Project-URL: Issues, https://github.com/sellapp/sellapp-python/issues
+License: MIT
+License-File: LICENSE.txt
+License-File: NOTICE.txt
+Requires-Python: >=3.10
+Requires-Dist: anyio<5,>=4.14.2
+Requires-Dist: httpx<1,>=0.27
+Provides-Extra: test
+Requires-Dist: pytest-asyncio<2,>=0.24; extra == 'test'
+Requires-Dist: pytest-httpx<1,>=0.35; extra == 'test'
+Requires-Dist: pytest<9,>=8; extra == 'test'
+Description-Content-Type: text/markdown
+
+# SellApp Python SDK
+
+Put your SellApp store to work from Python. Read your catalog, work with orders,
+or connect customers to your own tools. The SDK turns Python method calls into
+API requests and returns objects whose fields you can use straight away.
+
+We'll start with one product and print its title. A small script is enough to
+find out whether your store and your code are on speaking terms.
+Already building an integration? Jump to [configuration](https://github.com/sellapp/sellapp-python/blob/main/docs/usage.md#client-configuration),
+[async](#prefer-async), or the [method index](https://github.com/sellapp/sellapp-python/blob/main/docs/methods.md).
+
+## Installation
+
+Requires Python 3.10 or newer. Use a currently supported Python release for new
+integrations. Create a virtual environment to keep this project's packages together:
+
+```sh
+python -m venv .venv
+. .venv/bin/activate
+python -m pip install sellapp-sdk
+```
+
+On Windows, activate with `.venv\Scripts\Activate.ps1`. The distribution name
+is `sellapp-sdk`; the import is `sellapp_sdk`.
+Find releases on [PyPI](https://pypi.org/project/sellapp-sdk/) and the
+[source repository](https://github.com/sellapp/sellapp-python). If you are working from an unpublished
+checkout, install that local copy with `python -m pip install .` instead.
+
+## First request
+
+Your API key identifies your account; the store slug selects the store. For
+`launch-lab.sell.app`, the slug is `launch-lab`. This request needs the key's
+`listing` ability, which grants catalog access. Follow the
+[authentication guide](https://sell.app/docs/api/authentication) for key setup and
+permissions, and keep the secret key on your server.
+
+Set these environment variables in a Bash-compatible terminal, replacing both placeholders.
+Your script can read these settings without keeping credentials in its source:
+
+```sh
+export SELLAPP_API_KEY="your-api-key"
+export SELLAPP_STORE="your-store"
+export SELLAPP_API_BASE_URL="https://sell.app/api"
+```
+
+The address above connects to your real store. This first request only reads data.
+The SDK sends the key as `Authorization: Bearer` and the slug as `X-STORE`.
+The API site's curl examples use `SELLAPP_STORE`; the Python SDK reads
+`SELLAPP_STORE`.
+
+The examples require an explicit base URL: you choose where they connect.
+`SELLAPP_API_BASE_URL` is an example convention,
+read by the scripts and passed to `base_url`; the SDK itself does not read it.
+
+Save this as `first_request.py` and run `python first_request.py`, or use the
+copy in the checkout with `python examples/first_request.py`:
+
+```python
+import os
+
+from sellapp_sdk import SellAppClient
+
+base_url = os.environ["SELLAPP_API_BASE_URL"]
+if not base_url.strip():
+    raise ValueError("Set a nonempty SELLAPP_API_BASE_URL before running this example")
+
+with SellAppClient(base_url=base_url) as client:
+    page = client.products.list(limit=1)
+    for product in page.data:
+        print(product.id, product.title)
+    if not page.data:
+        print("No products yet. Your connection is ready.")
+```
+
+The result is a page, or one batch of products. `limit=1` asks for at most one;
+`page.data` holds the returned product objects. The script prints each product's
+ID and title. An empty store still proves the connection works, and the script
+says so. The `with` block closes the client's HTTP connections when it finishes.
+
+### Prefer async?
+
+If your app already uses `asyncio`, use `AsyncSellAppClient`
+and `await` each request. It comes in the same package; there's nothing extra to
+install. For a simple script, the synchronous example above is all you need.
+Run `python examples/async_first_request.py`:
+
+```python
+import asyncio
+import os
+
+from sellapp_sdk import AsyncSellAppClient
+
+base_url = os.environ["SELLAPP_API_BASE_URL"]
+if not base_url.strip():
+    raise ValueError("Set a nonempty SELLAPP_API_BASE_URL before running this example")
+
+
+async def main():
+    async with AsyncSellAppClient(base_url=base_url) as client:
+        page = await client.products.list(limit=1)
+        for product in page.data:
+            print(product.id, product.title)
+        if not page.data:
+            print("No products yet. Your connection is ready.")
+
+
+asyncio.run(main())
+```
+
+## Account access and first-store setup
+
+Create a user-owned key in [API keys](https://sell.app/user/api-tokens), even
+before you have a store. Enable `account:read` for identity, store discovery and
+permission inspection, and `stores:create` separately for store creation.
+Identity, discovery, store detail by ID and creation omit `X-STORE`; permission
+inspection and business requests select a store explicitly.
+
+An unrestricted key covers current and future accessible stores. A selected-store
+key covers only its fixed list; an empty list covers none. Membership and role
+changes still apply. Selected-store keys cannot create stores. Existing keys do
+not gain abilities automatically; `*` satisfies the new abilities while retaining
+membership, role and restriction checks.
+
+The [account guide](https://sell.app/docs/api/authentication#discover-your-account-before-selecting-a-store)
+shows first-store creation, required idempotency keys, and bounded reads across
+several stores with partial failures. Creation returns an ID and slug; use the
+slug for subsequent product requests. Find your language's methods in the
+[resource reference](https://github.com/sellapp/sellapp-python/blob/main/docs/methods.md). CLI and MCP connections retain browser OAuth.
+
+## If the request fails
+
+| Result | Next step |
+| --- | --- |
+| Empty product list | The read succeeded. Create a product when you are ready. |
+| 401 | Check the selected credential and whether it has expired or been revoked. |
+| 403 | Check the key's listing ability, selected-store restrictions and the account's current store permissions. Official CLI OAuth also requires its active grant. |
+| 400 with a missing-store message | Set SELLAPP_STORE to an authorized store slug. |
+| 429 | Follow Retry-After and the SDK's documented retry behavior. |
+
+Keep the request ID when reporting an API failure. Never include credentials.
+
+## Three useful next actions
+
+1. [Create and edit a product](https://github.com/sellapp/sellapp-python/blob/main/docs/resources/products.md): exact signatures and complete examples.
+2. [Read orders or create a checkout](https://github.com/sellapp/sellapp-python/blob/main/docs/resources/orders.md): inspect permissions and effects before changing a purchase.
+3. [Read more than one page](https://github.com/sellapp/sellapp-python/blob/main/docs/usage.md): pagination, request controls, errors, and retry behavior.
+
+## Reference and examples
+
+- [Resource reference](https://github.com/sellapp/sellapp-python/blob/main/docs/methods.md)
+- [Runnable examples](https://github.com/sellapp/sellapp-python/blob/main/examples/README.md)
+- [API documentation](https://sell.app/docs/api)
+
+## Support and releases
+
+Find available packages and installation instructions in the [SDK guide](https://sell.app/docs/api/sdks).
+[Report an SDK issue](https://github.com/sellapp/sellapp-python/issues).
+Include the SDK version, runtime version, and a redacted reproduction.
+Licensed under [MIT](https://github.com/sellapp/sellapp-python/blob/main/LICENSE.txt); see [third-party notices](https://github.com/sellapp/sellapp-python/blob/main/NOTICE.txt).

sellapp_sdk-0.1.1/README.md

@@ -0,0 +1,159 @@
+# SellApp Python SDK
+
+Put your SellApp store to work from Python. Read your catalog, work with orders,
+or connect customers to your own tools. The SDK turns Python method calls into
+API requests and returns objects whose fields you can use straight away.
+
+We'll start with one product and print its title. A small script is enough to
+find out whether your store and your code are on speaking terms.
+Already building an integration? Jump to [configuration](https://github.com/sellapp/sellapp-python/blob/main/docs/usage.md#client-configuration),
+[async](#prefer-async), or the [method index](https://github.com/sellapp/sellapp-python/blob/main/docs/methods.md).
+
+## Installation
+
+Requires Python 3.10 or newer. Use a currently supported Python release for new
+integrations. Create a virtual environment to keep this project's packages together:
+
+```sh
+python -m venv .venv
+. .venv/bin/activate
+python -m pip install sellapp-sdk
+```
+
+On Windows, activate with `.venv\Scripts\Activate.ps1`. The distribution name
+is `sellapp-sdk`; the import is `sellapp_sdk`.
+Find releases on [PyPI](https://pypi.org/project/sellapp-sdk/) and the
+[source repository](https://github.com/sellapp/sellapp-python). If you are working from an unpublished
+checkout, install that local copy with `python -m pip install .` instead.
+
+## First request
+
+Your API key identifies your account; the store slug selects the store. For
+`launch-lab.sell.app`, the slug is `launch-lab`. This request needs the key's
+`listing` ability, which grants catalog access. Follow the
+[authentication guide](https://sell.app/docs/api/authentication) for key setup and
+permissions, and keep the secret key on your server.
+
+Set these environment variables in a Bash-compatible terminal, replacing both placeholders.
+Your script can read these settings without keeping credentials in its source:
+
+```sh
+export SELLAPP_API_KEY="your-api-key"
+export SELLAPP_STORE="your-store"
+export SELLAPP_API_BASE_URL="https://sell.app/api"
+```
+
+The address above connects to your real store. This first request only reads data.
+The SDK sends the key as `Authorization: Bearer` and the slug as `X-STORE`.
+The API site's curl examples use `SELLAPP_STORE`; the Python SDK reads
+`SELLAPP_STORE`.
+
+The examples require an explicit base URL: you choose where they connect.
+`SELLAPP_API_BASE_URL` is an example convention,
+read by the scripts and passed to `base_url`; the SDK itself does not read it.
+
+Save this as `first_request.py` and run `python first_request.py`, or use the
+copy in the checkout with `python examples/first_request.py`:
+
+```python
+import os
+
+from sellapp_sdk import SellAppClient
+
+base_url = os.environ["SELLAPP_API_BASE_URL"]
+if not base_url.strip():
+    raise ValueError("Set a nonempty SELLAPP_API_BASE_URL before running this example")
+
+with SellAppClient(base_url=base_url) as client:
+    page = client.products.list(limit=1)
+    for product in page.data:
+        print(product.id, product.title)
+    if not page.data:
+        print("No products yet. Your connection is ready.")
+```
+
+The result is a page, or one batch of products. `limit=1` asks for at most one;
+`page.data` holds the returned product objects. The script prints each product's
+ID and title. An empty store still proves the connection works, and the script
+says so. The `with` block closes the client's HTTP connections when it finishes.
+
+### Prefer async?
+
+If your app already uses `asyncio`, use `AsyncSellAppClient`
+and `await` each request. It comes in the same package; there's nothing extra to
+install. For a simple script, the synchronous example above is all you need.
+Run `python examples/async_first_request.py`:
+
+```python
+import asyncio
+import os
+
+from sellapp_sdk import AsyncSellAppClient
+
+base_url = os.environ["SELLAPP_API_BASE_URL"]
+if not base_url.strip():
+    raise ValueError("Set a nonempty SELLAPP_API_BASE_URL before running this example")
+
+
+async def main():
+    async with AsyncSellAppClient(base_url=base_url) as client:
+        page = await client.products.list(limit=1)
+        for product in page.data:
+            print(product.id, product.title)
+        if not page.data:
+            print("No products yet. Your connection is ready.")
+
+
+asyncio.run(main())
+```
+
+## Account access and first-store setup
+
+Create a user-owned key in [API keys](https://sell.app/user/api-tokens), even
+before you have a store. Enable `account:read` for identity, store discovery and
+permission inspection, and `stores:create` separately for store creation.
+Identity, discovery, store detail by ID and creation omit `X-STORE`; permission
+inspection and business requests select a store explicitly.
+
+An unrestricted key covers current and future accessible stores. A selected-store
+key covers only its fixed list; an empty list covers none. Membership and role
+changes still apply. Selected-store keys cannot create stores. Existing keys do
+not gain abilities automatically; `*` satisfies the new abilities while retaining
+membership, role and restriction checks.
+
+The [account guide](https://sell.app/docs/api/authentication#discover-your-account-before-selecting-a-store)
+shows first-store creation, required idempotency keys, and bounded reads across
+several stores with partial failures. Creation returns an ID and slug; use the
+slug for subsequent product requests. Find your language's methods in the
+[resource reference](https://github.com/sellapp/sellapp-python/blob/main/docs/methods.md). CLI and MCP connections retain browser OAuth.
+
+## If the request fails
+
+| Result | Next step |
+| --- | --- |
+| Empty product list | The read succeeded. Create a product when you are ready. |
+| 401 | Check the selected credential and whether it has expired or been revoked. |
+| 403 | Check the key's listing ability, selected-store restrictions and the account's current store permissions. Official CLI OAuth also requires its active grant. |
+| 400 with a missing-store message | Set SELLAPP_STORE to an authorized store slug. |
+| 429 | Follow Retry-After and the SDK's documented retry behavior. |
+
+Keep the request ID when reporting an API failure. Never include credentials.
+
+## Three useful next actions
+
+1. [Create and edit a product](https://github.com/sellapp/sellapp-python/blob/main/docs/resources/products.md): exact signatures and complete examples.
+2. [Read orders or create a checkout](https://github.com/sellapp/sellapp-python/blob/main/docs/resources/orders.md): inspect permissions and effects before changing a purchase.
+3. [Read more than one page](https://github.com/sellapp/sellapp-python/blob/main/docs/usage.md): pagination, request controls, errors, and retry behavior.
+
+## Reference and examples
+
+- [Resource reference](https://github.com/sellapp/sellapp-python/blob/main/docs/methods.md)
+- [Runnable examples](https://github.com/sellapp/sellapp-python/blob/main/examples/README.md)
+- [API documentation](https://sell.app/docs/api)
+
+## Support and releases
+
+Find available packages and installation instructions in the [SDK guide](https://sell.app/docs/api/sdks).
+[Report an SDK issue](https://github.com/sellapp/sellapp-python/issues).
+Include the SDK version, runtime version, and a redacted reproduction.
+Licensed under [MIT](https://github.com/sellapp/sellapp-python/blob/main/LICENSE.txt); see [third-party notices](https://github.com/sellapp/sellapp-python/blob/main/NOTICE.txt).

sellapp_sdk-0.1.1/docs/methods.md

@@ -0,0 +1,84 @@
+# Resource reference
+
+[Back to onboarding](../README.md)
+
+Choose a resource for native signatures, complete examples, permissions, errors, and API links.
+
+| Resource | Methods |
+| --- | --- |
+| [account](resources/account.md) | 5 |
+| [add_ons](resources/add_ons.md) | 7 |
+| [add_ons_parent_products](resources/add_ons_parent_products.md) | 2 |
+| [affiliate_payouts](resources/affiliate_payouts.md) | 4 |
+| [affiliate_program](resources/affiliate_program.md) | 4 |
+| [affiliate_referral_sessions](resources/affiliate_referral_sessions.md) | 2 |
+| [affiliate_referrals](resources/affiliate_referrals.md) | 3 |
+| [affiliates](resources/affiliates.md) | 3 |
+| [blacklists](resources/blacklists.md) | 11 |
+| [bookings](resources/bookings.md) | 5 |
+| [bookings_calendar_events](resources/bookings_calendar_events.md) | 2 |
+| [bundle_items](resources/bundle_items.md) | 4 |
+| [cashback_rules](resources/cashback_rules.md) | 6 |
+| [charges](resources/charges.md) | 5 |
+| [community_connections](resources/community_connections.md) | 6 |
+| [coupons](resources/coupons.md) | 20 |
+| [courses](resources/courses.md) | 5 |
+| [courses_lessons](resources/courses_lessons.md) | 5 |
+| [courses_sections](resources/courses_sections.md) | 5 |
+| [credits](resources/credits.md) | 1 |
+| [credits_balances](resources/credits_balances.md) | 2 |
+| [credits_balances_transactions](resources/credits_balances_transactions.md) | 1 |
+| [credits_products](resources/credits_products.md) | 7 |
+| [customer_portal](resources/customer_portal.md) | 17 |
+| [customer_sessions](resources/customer_sessions.md) | 2 |
+| [customers](resources/customers.md) | 8 |
+| [disputes](resources/disputes.md) | 2 |
+| [entitlements](resources/entitlements.md) | 2 |
+| [events](resources/events.md) | 2 |
+| [exports](resources/exports.md) | 4 |
+| [feedback](resources/feedback.md) | 9 |
+| [groups](resources/groups.md) | 6 |
+| [groups_products](resources/groups_products.md) | 6 |
+| [highlights](resources/highlights.md) | 8 |
+| [highlights_media](resources/highlights_media.md) | 7 |
+| [invoices](resources/invoices.md) | 14 |
+| [license_instances](resources/license_instances.md) | 1 |
+| [licenses](resources/licenses.md) | 6 |
+| [licenses_instances](resources/licenses_instances.md) | 2 |
+| [line_items](resources/line_items.md) | 3 |
+| [oauth](resources/oauth.md) | 6 |
+| [oauth_management](resources/oauth_management.md) | 2 |
+| [orders](resources/orders.md) | 14 |
+| [orders_line_items](resources/orders_line_items.md) | 3 |
+| [payment_methods](resources/payment_methods.md) | 5 |
+| [payment_methods_custom](resources/payment_methods_custom.md) | 6 |
+| [product_variants](resources/product_variants.md) | 10 |
+| [product_variants_booking](resources/product_variants_booking.md) | 6 |
+| [product_variants_pricing](resources/product_variants_pricing.md) | 2 |
+| [products](resources/products.md) | 10 |
+| [products_addons](resources/products_addons.md) | 2 |
+| [promotions](resources/promotions.md) | 8 |
+| [promotions_phases](resources/promotions_phases.md) | 2 |
+| [refunds](resources/refunds.md) | 2 |
+| [reward_coupon_templates](resources/reward_coupon_templates.md) | 6 |
+| [reward_grants](resources/reward_grants.md) | 4 |
+| [reward_rules](resources/reward_rules.md) | 6 |
+| [sections](resources/sections.md) | 26 |
+| [store_custom_domains](resources/store_custom_domains.md) | 5 |
+| [store_notification_channels](resources/store_notification_channels.md) | 6 |
+| [store_settings](resources/store_settings.md) | 7 |
+| [subscriptions](resources/subscriptions.md) | 14 |
+| [tickets](resources/tickets.md) | 7 |
+| [tickets_messages](resources/tickets_messages.md) | 8 |
+| [upsell_offers](resources/upsell_offers.md) | 7 |
+| [variant_deliverable_files](resources/variant_deliverable_files.md) | 6 |
+| [variant_deliverable_folders](resources/variant_deliverable_folders.md) | 6 |
+| [variant_deliverables](resources/variant_deliverables.md) | 2 |
+| [variant_serials](resources/variant_serials.md) | 5 |
+| [wallet](resources/wallet.md) | 4 |
+| [wallet_bonus_tiers](resources/wallet_bonus_tiers.md) | 6 |
+| [wallet_settings](resources/wallet_settings.md) | 2 |
+| [wallet_topups](resources/wallet_topups.md) | 1 |
+| [wallet_transactions](resources/wallet_transactions.md) | 1 |
+| [webhook_channels](resources/webhook_channels.md) | 9 |
+| [webhook_platform](resources/webhook_platform.md) | 4 |

sellapp_sdk-0.1.1/docs/migration.md

@@ -0,0 +1,127 @@
+# Move to the current SellApp API contract
+
+This update covers 433 SDK operations. Existing API-key constructors remain available. Review the changes below before rebuilding your integration.
+
+## Convenience operations and atomic creation
+
+Seven additional operations retain these language-neutral identities. Check the generated method index for your language's native spelling.
+
+| Operation ID                    | CLI command                          |
+| ------------------------------- | ------------------------------------ |
+| `listWalletTransactions`        | `wallet transactions list`           |
+| `listCreditBalanceTransactions` | `credits balances transactions list` |
+| `upsertCustomerByExternalId`    | `customers upsert-by-external-id`    |
+| `syncGroupProducts`             | `groups products replace`            |
+| `updateTicket`                  | `tickets update`                     |
+| `createWalletOrder`             | `orders create-from-wallet`          |
+| `payOrderFromWallet`            | `orders pay-from-wallet`             |
+
+Product creation accepts initial variants and bundle contents atomically. Add-on creation accepts its initial variant; the existing `createAddOnDraft` identity is retained even when that request publishes the add-on. These creation fields are absent from update and batch requests. Group updates can change section and ordered membership; the dedicated membership replacement accepts `product_ids`, including `[]` to clear membership. Group updates and replacement require the CLI/MCP consequential-action confirmation.
+
+Wallet history is paginated. Wallet spending requires both invoice and wallet-write abilities, full available funds, and a stable idempotency key. A paid order may still await fulfillment. Customer upsert requires email; omitted fields stay unchanged, while supplied metadata replaces the complete metadata object.
+
+Custom-payment modifiers now have typed nullable object models. Omit `modifier` to preserve it on update; send `null` or `{}` to clear it. Go callers use `NullFields: []string{"modifier"}` for explicit null. Named nullable objects now retain their declared fields and nullability across all languages instead of falling back to empty model shapes. Recompile integrations that constructed those models directly; component identities remain stable, but declared required fields and value types are now enforced. Decimal modifier inputs remain strings or numbers. Custom wallet top-ups do not apply these adjustments.
+
+The hosted MCP runtime remains the business executor. Compact mode is the default; catalog mode is optional. Resource and discovery cache hints do not authorize caching REST business data in an SDK. Selected REST reads are cached by the server; send the standard `Cache-Control: no-cache` or `no-store` header when a bypass is needed.
+
+## Shared account operations
+
+User-owned API keys now support identity, store discovery and permission inspection
+with `account:read`, and store creation with `stores:create`. Existing keys are
+unchanged; a `*` key satisfies the new abilities subject to the same membership,
+role and optional selected-store restrictions. Selected-store keys cannot create
+stores. Account identity, discovery, detail by ID and creation omit `X-STORE`;
+permission inspection and store business calls select a store explicitly.
+
+These operation identities and resource groups changed together. Use your SDK's
+generated method index for its language-specific spelling; no legacy aliases are
+provided in this source candidate.
+
+| Previous operation ID  | Current operation ID  | Resource |
+| ---------------------- | --------------------- | -------- |
+| `getOAuthUser`         | `getAccount`          | Account  |
+| `listOAuthStores`      | `listStores`          | Account  |
+| `getOAuthStore`        | `getStore`            | Account  |
+| `listOAuthPermissions` | `getStorePermissions` | Account  |
+
+`createStore` also belongs to Account. It requires an `Idempotency-Key`; repeat
+the same key and body after a lost response within the 24-hour retention period.
+Authorized retries share the same user and operation identity across credential
+rotation and supported credential types. Current authorization is checked before
+replay. Creation returns the ID and slug without changing dashboard selection.
+New creation is limited to one store per user every 60 seconds across credentials.
+On `429`, honor `Retry-After` and retain the original key and body.
+
+Permission inspection identifies `credential_type`. API-key responses include
+`key_abilities`, `store_access` (`all` or `selected`), `store_permissions` and
+`effective_abilities`. OAuth responses retain `approved_scopes`, `token_scopes`,
+`store_permissions` and `effective_scopes`. These describe authorization; they do
+not establish whether a record, provider or payment is eligible for an action.
+
+## Orders method names
+
+This source candidate also carries the existing Orders resource naming update.
+Where a language previously repeated `Order` in a method name, use its generated
+method index to update these calls. The operation IDs and routes stay the same.
+
+| Previous method name (camel case)   | Current method name (camel case) |
+| ----------------------------------- | -------------------------------- |
+| `createOrder`                       | `create`                         |
+| `createOrderCheckout`               | `createCheckout`                 |
+| `createOrderRefund`                 | `createRefund`                   |
+| `createOrderReplacement`            | `createReplacement`              |
+| `updateOrderStatus`                 | `updateStatus`                   |
+| `listOrderDeliverables`             | `listDeliverables`               |
+| `retryOrderFulfillment`             | `retryFulfillment`               |
+| `retryOrderDynamicDelivery`         | `retryDynamicDelivery`           |
+| `sendOrderFulfillmentNotifications` | `sendFulfillmentNotifications`   |
+
+## Removed methods
+
+Remove calls to these routes. They have no replacement SDK method:
+
+- `GET /v2/analytics`
+- `GET /v2/seller-balance`
+- `GET /v2/seller-payouts` and `POST /v2/seller-payouts`
+- `GET /v2/seller-payouts/configuration` and `PUT /v2/seller-payouts/configuration`
+- `GET /v2/seller-payouts/{sellerPayout}`
+- `PATCH /v2/seller-payouts/{sellerPayout}/status`
+
+The CLI analytics-snapshot workflow is removed. Affiliate payout records remain supported; creating a record does not transfer seller funds. Customer credits, refunds and disputes remain available under their documented contracts.
+
+Catalog plan/create/read/apply routes are absent. Use the individual catalog APIs and check each result. Separate catalog requests are not an atomic transaction; the creation and membership operations above document their own atomic behavior.
+
+## Rebuild model references
+
+The canonical schema names no longer contain repeated `SdkSdk...` prefixes. Regenerate imports and let your compiler identify old model references. For example, the OpenAPI component `SdkSdkActivateLicenseKeyResponseValue200ApplicationJsonPropertyData` is now `ActivateLicenseKeyResponseValue200ApplicationJsonPropertyData`. Each language applies its normal naming rules to these component names.
+
+Retained operation IDs outside the account renames above, including Invoice operation IDs, are unchanged. Retained v2 Invoice request and success-response wire schemas are unchanged after resolving component references; their generated model names can still change.
+
+The new v2 feedback and ticket APIs differ from v1. Existing v1 feedback still uses integer `listing_id` and `invoice_id`; new v2 feedback uses `product_id` and `order_id`. Existing v1 tickets keep string-array references and integer `read_by`; the new v2 ticket types and boolean read status have their own contract. Customer sessions and OAuth permissions are new surfaces. Do not substitute v1 models when calling these v2 methods.
+
+| Resource | Retained v1 fields                           | New v2 fields                                                                                                                |
+| -------- | -------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------- |
+| Feedback | `listing_id: integer`, `invoice_id: integer` | `product_id: integer\|null`, `order_id: integer\|null`                                                                       |
+| Tickets  | `reference: string[]`, `read_by: integer`    | `reference: {type: "product"\|"order"\|null, id: integer\|string\|null}`, `read_status: {customer: boolean, store: boolean}` |
+
+Ticket `archived` remains an integer. Customer-session creation returns a UUID string in `data.id`; pass that returned ID to `DELETE /v2/customer-sessions/{session}`. OAuth permission inspection returns four required string arrays: `store_permissions`, `approved_scopes`, `token_scopes`, and `effective_scopes`.
+
+## Choose credentials for each operation
+
+Supported v2 business operations accept an API key or an OAuth access token. OAuth business calls require `X-STORE`; API-key calls may omit it where the operation permits. Legacy operations retain their own requirements. Customer portal calls require a separate customer-session token and must not receive seller credentials.
+
+OAuth installation management continues to require official CLI OAuth. Ordinary SDK and REST integrations use API keys. Retained OAuth protocol interfaces are official CLI infrastructure, not general-purpose OAuth application onboarding. Protocol requests use the SellApp origin, while business requests use `/api`. Token and revoke requests are form encoded. Protocol discovery and authorization-start requests require no seller credential.
+
+The CLI manages its standard `admin` scope request through `sellapp login` and browser consent. Direct MCP uses its own browser OAuth connection, and the CLI bridge retains its saved OAuth profile. Current membership, role permissions, reviewed operations, token purpose and active installation constrain access. API-key restrictions do not change OAuth consent.
+
+## Handle retries and follow-up work
+
+Customer-session creation returns credentials once, with a 15-minute lifetime. Do not retry it as a way to recover a lost token. An OAuth refresh token rotates when used: serialize refreshes, replace the complete token pair together, and reauthorize after an uncertain exchange instead of replaying a possibly consumed refresh token.
+
+For a business request whose contract supports an idempotency key, keep the same key and body across a retry, including after refreshing the access token. Retain the request ID when investigating an error.
+
+Events use ordinary cursor polling and `meta.next_cursor`. Empty pages are normal. Save your checkpoint only after processing the page successfully. Cursors are bound to the store and filters; `410 cursor_expired` requires a recovery decision. Events are retained for 30 days. Only `order.completed` guarantees detailed event data; other events can require retrieving the referenced resource.
+
+Exports support sales, tax, customers and affiliate payouts in CSV or JSON. Date ranges cover at most 366 inclusive days, defaulting to today and the previous 365 days. One job per store and two per account may be queued or running. Limits are 10,000 source rows, 5 MiB serialized source data, and 10 MiB output; use a smaller date range after a size-limit failure. Follow `poll_after_seconds` and inspect the current state before downloading or retrying a failed export. The authenticated download returns a redirect to short-lived storage. Never send SellApp credentials or `X-STORE` to that storage URL.
+
+Webhook replay creates a new delivery ID for the same integration event. It does not repeat the business mutation and accepts no caller URL, payload or query override. Keep the required idempotency key.