@zippendo/sdk 1.0.3 → 1.1.0

package/docs/CheckBrandSlug200Response.md

@@ -0,0 +1,36 @@
+
+# CheckBrandSlug200Response
+
+
+## Properties
+
+Name | Type
+------------ | -------------
+`slug` | string
+`available` | boolean
+
+## Example
+
+```typescript
+import type { CheckBrandSlug200Response } from '@zippendo/sdk'
+
+// TODO: Update the object below with actual values
+const example = {
+  "slug": acme,
+  "available": true,
+} satisfies CheckBrandSlug200Response
+
+console.log(example)
+
+// Convert the instance to a JSON string
+const exampleJSON: string = JSON.stringify(example)
+console.log(exampleJSON)
+
+// Parse the JSON string back to an object
+const exampleParsed = JSON.parse(exampleJSON) as CheckBrandSlug200Response
+console.log(exampleParsed)
+```
+
+[[Back to top]](#) [[Back to API list]](../README.md#api-endpoints) [[Back to Model list]](../README.md#models) [[Back to README]](../README.md)
+
+

package/docs/CreateOrgBrandRequest.md

@@ -0,0 +1,58 @@
+
+# CreateOrgBrandRequest
+
+
+## Properties
+
+Name | Type
+------------ | -------------
+`companyName` | string
+`vatNumber` | string
+`customs` | { [key: string]: string; }
+`addressLine1` | string
+`addressLine2` | string
+`city` | string
+`postalCode` | string
+`country` | string
+`primaryColor` | string
+`secondaryColor` | string
+`name` | string
+`slug` | string
+`useOrgCustoms` | boolean
+
+## Example
+
+```typescript
+import type { CreateOrgBrandRequest } from '@zippendo/sdk'
+
+// TODO: Update the object below with actual values
+const example = {
+  "companyName": Acme ApS,
+  "vatNumber": DK12345678,
+  "customs": {"eori":"DK12345678"},
+  "addressLine1": Vestergade 12,
+  "addressLine2": 3. sal,
+  "city": København,
+  "postalCode": 1456,
+  "country": DK,
+  "primaryColor": #1D4ED8,
+  "secondaryColor": #F59E0B,
+  "name": Acme,
+  "slug": acme,
+  "useOrgCustoms": true,
+} satisfies CreateOrgBrandRequest
+
+console.log(example)
+
+// Convert the instance to a JSON string
+const exampleJSON: string = JSON.stringify(example)
+console.log(exampleJSON)
+
+// Parse the JSON string back to an object
+const exampleParsed = JSON.parse(exampleJSON) as CreateOrgBrandRequest
+console.log(exampleParsed)
+```
+
+[[Back to top]](#) [[Back to API list]](../README.md#api-endpoints) [[Back to Model list]](../README.md#models) [[Back to README]](../README.md)
+
+

package/docs/ListOrgBrands200Response.md

@@ -0,0 +1,34 @@
+
+# ListOrgBrands200Response
+
+
+## Properties
+
+Name | Type
+------------ | -------------
+`data` | [Array<ListOrgBrands200ResponseDataInner>](ListOrgBrands200ResponseDataInner.md)
+
+## Example
+
+```typescript
+import type { ListOrgBrands200Response } from '@zippendo/sdk'
+
+// TODO: Update the object below with actual values
+const example = {
+  "data": null,
+} satisfies ListOrgBrands200Response
+
+console.log(example)
+
+// Convert the instance to a JSON string
+const exampleJSON: string = JSON.stringify(example)
+console.log(exampleJSON)
+
+// Parse the JSON string back to an object
+const exampleParsed = JSON.parse(exampleJSON) as ListOrgBrands200Response
+console.log(exampleParsed)
+```
+
+[[Back to top]](#) [[Back to API list]](../README.md#api-endpoints) [[Back to Model list]](../README.md#models) [[Back to README]](../README.md)
+
+

package/docs/ListOrgBrands200ResponseDataInner.md

@@ -0,0 +1,70 @@
+
+# ListOrgBrands200ResponseDataInner
+
+
+## Properties
+
+Name | Type
+------------ | -------------
+`companyName` | string
+`vatNumber` | string
+`customs` | { [key: string]: string; }
+`addressLine1` | string
+`addressLine2` | string
+`city` | string
+`postalCode` | string
+`country` | string
+`primaryColor` | string
+`secondaryColor` | string
+`id` | string
+`orgId` | string
+`name` | string
+`slug` | string
+`useOrgCustoms` | boolean
+`logoUrl` | string
+`archivedAt` | string
+`createdAt` | string
+`updatedAt` | string
+
+## Example
+
+```typescript
+import type { ListOrgBrands200ResponseDataInner } from '@zippendo/sdk'
+
+// TODO: Update the object below with actual values
+const example = {
+  "companyName": Acme ApS,
+  "vatNumber": DK12345678,
+  "customs": {"eori":"DK12345678"},
+  "addressLine1": Vestergade 12,
+  "addressLine2": 3. sal,
+  "city": København,
+  "postalCode": 1456,
+  "country": DK,
+  "primaryColor": #1D4ED8,
+  "secondaryColor": #F59E0B,
+  "id": brnd_8f3kd92ld0,
+  "orgId": org_8f3kd92ld0,
+  "name": Acme,
+  "slug": acme,
+  "useOrgCustoms": true,
+  "logoUrl": /orgs/org_1/brands/brnd_1/logo,
+  "archivedAt": 2026-08-05T10:00:00.000Z,
+  "createdAt": 2026-06-22T14:30:00.000Z,
+  "updatedAt": 2026-06-22T14:30:00.000Z,
+} satisfies ListOrgBrands200ResponseDataInner
+
+console.log(example)
+
+// Convert the instance to a JSON string
+const exampleJSON: string = JSON.stringify(example)
+console.log(exampleJSON)
+
+// Parse the JSON string back to an object
+const exampleParsed = JSON.parse(exampleJSON) as ListOrgBrands200ResponseDataInner
+console.log(exampleParsed)
+```
+
+[[Back to top]](#) [[Back to API list]](../README.md#api-endpoints) [[Back to Model list]](../README.md#models) [[Back to README]](../README.md)
+
+

package/docs/UpdateOrgBrandRequest.md

@@ -0,0 +1,58 @@
+
+# UpdateOrgBrandRequest
+
+
+## Properties
+
+Name | Type
+------------ | -------------
+`companyName` | string
+`vatNumber` | string
+`customs` | { [key: string]: string; }
+`addressLine1` | string
+`addressLine2` | string
+`city` | string
+`postalCode` | string
+`country` | string
+`primaryColor` | string
+`secondaryColor` | string
+`name` | string
+`slug` | string
+`useOrgCustoms` | boolean
+
+## Example
+
+```typescript
+import type { UpdateOrgBrandRequest } from '@zippendo/sdk'
+
+// TODO: Update the object below with actual values
+const example = {
+  "companyName": Acme ApS,
+  "vatNumber": DK12345678,
+  "customs": {"eori":"DK12345678"},
+  "addressLine1": Vestergade 12,
+  "addressLine2": 3. sal,
+  "city": København,
+  "postalCode": 1456,
+  "country": DK,
+  "primaryColor": #1D4ED8,
+  "secondaryColor": #F59E0B,
+  "name": Acme,
+  "slug": acme,
+  "useOrgCustoms": true,
+} satisfies UpdateOrgBrandRequest
+
+console.log(example)
+
+// Convert the instance to a JSON string
+const exampleJSON: string = JSON.stringify(example)
+console.log(exampleJSON)
+
+// Parse the JSON string back to an object
+const exampleParsed = JSON.parse(exampleJSON) as UpdateOrgBrandRequest
+console.log(exampleParsed)
+```
+
+[[Back to top]](#) [[Back to API list]](../README.md#api-endpoints) [[Back to Model list]](../README.md#models) [[Back to README]](../README.md)
+
+

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@zippendo/sdk",
-  "version": "1.0.3",
+  "version": "1.1.0",
   "description": "OpenAPI client for @zippendo/sdk",
   "author": "OpenAPI-Generator",
   "repository": {

package/src/apis/AddressesApi.ts

@@ -2,7 +2,7 @@
 /* eslint-disable */
 /**
  * Zippendo Public API
- * Public API documentation for Zippendo. Authenticate using your API token (Bearer token prefixed with zipp_).  **Brands (sub-accounts).** An organization can be split into brands, each keeping its own orders, shipments and configuration separate. There are two ways to scope requests to one brand, and NEITHER changes any request body:  1. **Bind the token.** Create an API token with a `brandId` and every request it makes is confined    to that brand — reads filtered, writes stamped. This is the recommended way to give a single    brand\'s team its own credential. 2. **Send the `X-Zippendo-Brand` header.** An organization-wide token can scope an individual    request by sending the brand\'s id or slug in this header. Most SDKs let you set it once on the    client so every call inherits it.  A brand-bound token that receives an `X-Zippendo-Brand` header naming a different brand is rejected with `403 BRAND_ACCESS_DENIED` — the binding is never widened. Omit both and requests cover the whole organization, which is the behaviour of every existing token.  Records that belong to no brand carry `brandId: null`. Configuration (carriers, shipping rules, addresses) with a null brand is organization-wide and remains visible inside every brand; orders and shipments with a null brand are only visible organization-wide.
+ * Public API documentation for Zippendo. Authenticate using your API token (Bearer token prefixed with zipp_).  **Brands (sub-accounts).** An organization can be split into brands, each keeping its own orders, shipments and configuration separate. There are two ways to scope requests to one brand, and NEITHER changes any request body:  1. **Bind the token.** Create an API token with a `brandId` and every request it makes is confined    to that brand — reads filtered, writes stamped. This is the recommended way to give a single    brand\'s team its own credential. 2. **Send the `X-Zippendo-Brand` header.** An organization-wide token can scope an individual    request by sending the brand\'s id or slug in this header. Most SDKs let you set it once on the    client so every call inherits it.  A brand-bound token that receives an `X-Zippendo-Brand` header naming a different brand is rejected with `403 BRAND_ACCESS_DENIED` — the binding is never widened. Omit both and requests cover the whole organization, which is the behaviour of every existing token.  Records that belong to no brand carry `brandId: null`. Configuration (carriers, shipping rules, addresses) with a null brand is organization-wide and remains visible inside every brand; orders and shipments with a null brand are only visible organization-wide.  Brands themselves are managed under the **Brands** tag. Retiring a brand is done with `POST /orgs/{orgId}/brands/{brandId}/archive` — permanent deletion is a dashboard-only action, since it is refused while any order, shipment, member or token still references the brand. Brands require a plan that includes them; creating one beyond your plan\'s limit returns `403`.
  *
  * The version of the OpenAPI document: 1.0.0
  * Contact: support@zippendo.com

package/src/apis/BillingApi.ts

@@ -2,7 +2,7 @@
 /* eslint-disable */
 /**
  * Zippendo Public API
- * Public API documentation for Zippendo. Authenticate using your API token (Bearer token prefixed with zipp_).  **Brands (sub-accounts).** An organization can be split into brands, each keeping its own orders, shipments and configuration separate. There are two ways to scope requests to one brand, and NEITHER changes any request body:  1. **Bind the token.** Create an API token with a `brandId` and every request it makes is confined    to that brand — reads filtered, writes stamped. This is the recommended way to give a single    brand\'s team its own credential. 2. **Send the `X-Zippendo-Brand` header.** An organization-wide token can scope an individual    request by sending the brand\'s id or slug in this header. Most SDKs let you set it once on the    client so every call inherits it.  A brand-bound token that receives an `X-Zippendo-Brand` header naming a different brand is rejected with `403 BRAND_ACCESS_DENIED` — the binding is never widened. Omit both and requests cover the whole organization, which is the behaviour of every existing token.  Records that belong to no brand carry `brandId: null`. Configuration (carriers, shipping rules, addresses) with a null brand is organization-wide and remains visible inside every brand; orders and shipments with a null brand are only visible organization-wide.
+ * Public API documentation for Zippendo. Authenticate using your API token (Bearer token prefixed with zipp_).  **Brands (sub-accounts).** An organization can be split into brands, each keeping its own orders, shipments and configuration separate. There are two ways to scope requests to one brand, and NEITHER changes any request body:  1. **Bind the token.** Create an API token with a `brandId` and every request it makes is confined    to that brand — reads filtered, writes stamped. This is the recommended way to give a single    brand\'s team its own credential. 2. **Send the `X-Zippendo-Brand` header.** An organization-wide token can scope an individual    request by sending the brand\'s id or slug in this header. Most SDKs let you set it once on the    client so every call inherits it.  A brand-bound token that receives an `X-Zippendo-Brand` header naming a different brand is rejected with `403 BRAND_ACCESS_DENIED` — the binding is never widened. Omit both and requests cover the whole organization, which is the behaviour of every existing token.  Records that belong to no brand carry `brandId: null`. Configuration (carriers, shipping rules, addresses) with a null brand is organization-wide and remains visible inside every brand; orders and shipments with a null brand are only visible organization-wide.  Brands themselves are managed under the **Brands** tag. Retiring a brand is done with `POST /orgs/{orgId}/brands/{brandId}/archive` — permanent deletion is a dashboard-only action, since it is refused while any order, shipment, member or token still references the brand. Brands require a plan that includes them; creating one beyond your plan\'s limit returns `403`.
  *
  * The version of the OpenAPI document: 1.0.0
  * Contact: support@zippendo.com