@zippendo/sdk 1.1.0 → 1.1.1

package/dist/models/ListShipments200ResponseDataInnerCarrierSettingsAdditionalParametersValue.d.ts

@@ -1,51 +0,0 @@
-/**
- * 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.  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
- *
- * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
- * https://openapi-generator.tech
- * Do not edit the class manually.
- */
-import type { CreateShippingRuleRequestAdditionalParametersAnyOfValueAnyOfCoordinatesInner } from './CreateShippingRuleRequestAdditionalParametersAnyOfValueAnyOfCoordinatesInner';
-/**
- *
- * @export
- * @interface ListShipments200ResponseDataInnerCarrierSettingsAdditionalParametersValue
- */
-export interface ListShipments200ResponseDataInnerCarrierSettingsAdditionalParametersValue {
-    /**
-     * Identifier of the selected service point.
-     * @type {string}
-     * @memberof ListShipments200ResponseDataInnerCarrierSettingsAdditionalParametersValue
-     */
-    id: string;
-    /**
-     * Display name of the service point.
-     * @type {string}
-     * @memberof ListShipments200ResponseDataInnerCarrierSettingsAdditionalParametersValue
-     */
-    name: string;
-    /**
-     * Formatted address of the service point.
-     * @type {string}
-     * @memberof ListShipments200ResponseDataInnerCarrierSettingsAdditionalParametersValue
-     */
-    address: string;
-    /**
-     * Latitude/longitude of the service point.
-     * @type {Array<CreateShippingRuleRequestAdditionalParametersAnyOfValueAnyOfCoordinatesInner>}
-     * @memberof ListShipments200ResponseDataInnerCarrierSettingsAdditionalParametersValue
-     */
-    coordinates?: Array<CreateShippingRuleRequestAdditionalParametersAnyOfValueAnyOfCoordinatesInner>;
-}
-/**
- * Check if a given object implements the ListShipments200ResponseDataInnerCarrierSettingsAdditionalParametersValue interface.
- */
-export declare function instanceOfListShipments200ResponseDataInnerCarrierSettingsAdditionalParametersValue(value: object): value is ListShipments200ResponseDataInnerCarrierSettingsAdditionalParametersValue;
-export declare function ListShipments200ResponseDataInnerCarrierSettingsAdditionalParametersValueFromJSON(json: any): ListShipments200ResponseDataInnerCarrierSettingsAdditionalParametersValue;
-export declare function ListShipments200ResponseDataInnerCarrierSettingsAdditionalParametersValueFromJSONTyped(json: any, ignoreDiscriminator: boolean): ListShipments200ResponseDataInnerCarrierSettingsAdditionalParametersValue;
-export declare function ListShipments200ResponseDataInnerCarrierSettingsAdditionalParametersValueToJSON(json: any): ListShipments200ResponseDataInnerCarrierSettingsAdditionalParametersValue;
-export declare function ListShipments200ResponseDataInnerCarrierSettingsAdditionalParametersValueToJSONTyped(value?: ListShipments200ResponseDataInnerCarrierSettingsAdditionalParametersValue | null, ignoreDiscriminator?: boolean): any;

package/dist/models/ListShipments200ResponseDataInnerCarrierSettingsAdditionalParametersValueAnyOf.d.ts

@@ -1,51 +0,0 @@
-/**
- * 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.  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
- *
- * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
- * https://openapi-generator.tech
- * Do not edit the class manually.
- */
-import type { CreateShippingRuleRequestAdditionalParametersAnyOfValueAnyOfCoordinatesInner } from './CreateShippingRuleRequestAdditionalParametersAnyOfValueAnyOfCoordinatesInner';
-/**
- *
- * @export
- * @interface ListShipments200ResponseDataInnerCarrierSettingsAdditionalParametersValueAnyOf
- */
-export interface ListShipments200ResponseDataInnerCarrierSettingsAdditionalParametersValueAnyOf {
-    /**
-     * Identifier of the selected service point.
-     * @type {string}
-     * @memberof ListShipments200ResponseDataInnerCarrierSettingsAdditionalParametersValueAnyOf
-     */
-    id: string;
-    /**
-     * Display name of the service point.
-     * @type {string}
-     * @memberof ListShipments200ResponseDataInnerCarrierSettingsAdditionalParametersValueAnyOf
-     */
-    name: string;
-    /**
-     * Formatted address of the service point.
-     * @type {string}
-     * @memberof ListShipments200ResponseDataInnerCarrierSettingsAdditionalParametersValueAnyOf
-     */
-    address: string;
-    /**
-     * Latitude/longitude of the service point.
-     * @type {Array<CreateShippingRuleRequestAdditionalParametersAnyOfValueAnyOfCoordinatesInner>}
-     * @memberof ListShipments200ResponseDataInnerCarrierSettingsAdditionalParametersValueAnyOf
-     */
-    coordinates?: Array<CreateShippingRuleRequestAdditionalParametersAnyOfValueAnyOfCoordinatesInner>;
-}
-/**
- * Check if a given object implements the ListShipments200ResponseDataInnerCarrierSettingsAdditionalParametersValueAnyOf interface.
- */
-export declare function instanceOfListShipments200ResponseDataInnerCarrierSettingsAdditionalParametersValueAnyOf(value: object): value is ListShipments200ResponseDataInnerCarrierSettingsAdditionalParametersValueAnyOf;
-export declare function ListShipments200ResponseDataInnerCarrierSettingsAdditionalParametersValueAnyOfFromJSON(json: any): ListShipments200ResponseDataInnerCarrierSettingsAdditionalParametersValueAnyOf;
-export declare function ListShipments200ResponseDataInnerCarrierSettingsAdditionalParametersValueAnyOfFromJSONTyped(json: any, ignoreDiscriminator: boolean): ListShipments200ResponseDataInnerCarrierSettingsAdditionalParametersValueAnyOf;
-export declare function ListShipments200ResponseDataInnerCarrierSettingsAdditionalParametersValueAnyOfToJSON(json: any): ListShipments200ResponseDataInnerCarrierSettingsAdditionalParametersValueAnyOf;
-export declare function ListShipments200ResponseDataInnerCarrierSettingsAdditionalParametersValueAnyOfToJSONTyped(value?: ListShipments200ResponseDataInnerCarrierSettingsAdditionalParametersValueAnyOf | null, ignoreDiscriminator?: boolean): any;

package/dist/models/ListShipments200ResponseDataInnerCarrierSettingsAdditionalParametersValueAnyOf.js

@@ -1,61 +0,0 @@
-"use strict";
-/* tslint:disable */
-/* 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.  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
- *
- * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
- * https://openapi-generator.tech
- * Do not edit the class manually.
- */
-Object.defineProperty(exports, "__esModule", { value: true });
-exports.instanceOfListShipments200ResponseDataInnerCarrierSettingsAdditionalParametersValueAnyOf = instanceOfListShipments200ResponseDataInnerCarrierSettingsAdditionalParametersValueAnyOf;
-exports.ListShipments200ResponseDataInnerCarrierSettingsAdditionalParametersValueAnyOfFromJSON = ListShipments200ResponseDataInnerCarrierSettingsAdditionalParametersValueAnyOfFromJSON;
-exports.ListShipments200ResponseDataInnerCarrierSettingsAdditionalParametersValueAnyOfFromJSONTyped = ListShipments200ResponseDataInnerCarrierSettingsAdditionalParametersValueAnyOfFromJSONTyped;
-exports.ListShipments200ResponseDataInnerCarrierSettingsAdditionalParametersValueAnyOfToJSON = ListShipments200ResponseDataInnerCarrierSettingsAdditionalParametersValueAnyOfToJSON;
-exports.ListShipments200ResponseDataInnerCarrierSettingsAdditionalParametersValueAnyOfToJSONTyped = ListShipments200ResponseDataInnerCarrierSettingsAdditionalParametersValueAnyOfToJSONTyped;
-const CreateShippingRuleRequestAdditionalParametersAnyOfValueAnyOfCoordinatesInner_1 = require("./CreateShippingRuleRequestAdditionalParametersAnyOfValueAnyOfCoordinatesInner");
-/**
- * Check if a given object implements the ListShipments200ResponseDataInnerCarrierSettingsAdditionalParametersValueAnyOf interface.
- */
-function instanceOfListShipments200ResponseDataInnerCarrierSettingsAdditionalParametersValueAnyOf(value) {
-    if (!('id' in value) || value['id'] === undefined)
-        return false;
-    if (!('name' in value) || value['name'] === undefined)
-        return false;
-    if (!('address' in value) || value['address'] === undefined)
-        return false;
-    return true;
-}
-function ListShipments200ResponseDataInnerCarrierSettingsAdditionalParametersValueAnyOfFromJSON(json) {
-    return ListShipments200ResponseDataInnerCarrierSettingsAdditionalParametersValueAnyOfFromJSONTyped(json, false);
-}
-function ListShipments200ResponseDataInnerCarrierSettingsAdditionalParametersValueAnyOfFromJSONTyped(json, ignoreDiscriminator) {
-    if (json == null) {
-        return json;
-    }
-    return {
-        'id': json['id'],
-        'name': json['name'],
-        'address': json['address'],
-        'coordinates': json['coordinates'] == null ? undefined : (json['coordinates'].map(CreateShippingRuleRequestAdditionalParametersAnyOfValueAnyOfCoordinatesInner_1.CreateShippingRuleRequestAdditionalParametersAnyOfValueAnyOfCoordinatesInnerFromJSON)),
-    };
-}
-function ListShipments200ResponseDataInnerCarrierSettingsAdditionalParametersValueAnyOfToJSON(json) {
-    return ListShipments200ResponseDataInnerCarrierSettingsAdditionalParametersValueAnyOfToJSONTyped(json, false);
-}
-function ListShipments200ResponseDataInnerCarrierSettingsAdditionalParametersValueAnyOfToJSONTyped(value, ignoreDiscriminator = false) {
-    if (value == null) {
-        return value;
-    }
-    return {
-        'id': value['id'],
-        'name': value['name'],
-        'address': value['address'],
-        'coordinates': value['coordinates'] == null ? undefined : (value['coordinates'].map(CreateShippingRuleRequestAdditionalParametersAnyOfValueAnyOfCoordinatesInner_1.CreateShippingRuleRequestAdditionalParametersAnyOfValueAnyOfCoordinatesInnerToJSON)),
-    };
-}

package/docs/CreateShippingRuleRequestAdditionalParameters.md

@@ -1,33 +0,0 @@
-
-# CreateShippingRuleRequestAdditionalParameters
-
-Carrier-specific extra parameters. Accepts EITHER the `{ key: value }` object (preferred) OR the legacy `[{ name, val }]` array, so you can migrate on your own schedule. Each key / `name` is the carrier parameter `key` from the product\'s `additionalParameters[].key` (e.g. `returnFunctionality`).
-
-## Properties
-
-Name | Type
------------- | -------------
-
-## Example
-
-```typescript
-import type { CreateShippingRuleRequestAdditionalParameters } from '@zippendo/sdk'
-
-// TODO: Update the object below with actual values
-const example = {
-} satisfies CreateShippingRuleRequestAdditionalParameters
-
-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 CreateShippingRuleRequestAdditionalParameters
-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/CreateShippingRuleRequestAdditionalParametersAnyOfInner.md

@@ -1,36 +0,0 @@
-
-# CreateShippingRuleRequestAdditionalParametersAnyOfInner
-
-
-## Properties
-
-Name | Type
------------- | -------------
-`name` | string
-`val` | string
-
-## Example
-
-```typescript
-import type { CreateShippingRuleRequestAdditionalParametersAnyOfInner } from '@zippendo/sdk'
-
-// TODO: Update the object below with actual values
-const example = {
-  "name": returnFunctionality,
-  "val": LABELLESS,
-} satisfies CreateShippingRuleRequestAdditionalParametersAnyOfInner
-
-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 CreateShippingRuleRequestAdditionalParametersAnyOfInner
-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/CreateShippingRuleRequestAdditionalParametersAnyOfValueAnyOfCoordinatesInner.md

@@ -1,32 +0,0 @@
-
-# CreateShippingRuleRequestAdditionalParametersAnyOfValueAnyOfCoordinatesInner
-
-
-## Properties
-
-Name | Type
------------- | -------------
-
-## Example
-
-```typescript
-import type { CreateShippingRuleRequestAdditionalParametersAnyOfValueAnyOfCoordinatesInner } from '@zippendo/sdk'
-
-// TODO: Update the object below with actual values
-const example = {
-} satisfies CreateShippingRuleRequestAdditionalParametersAnyOfValueAnyOfCoordinatesInner
-
-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 CreateShippingRuleRequestAdditionalParametersAnyOfValueAnyOfCoordinatesInner
-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/src/models/CreateShippingRuleRequestAdditionalParameters.ts

@@ -1,61 +0,0 @@
-/* tslint:disable */
-/* 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.  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
- *
- * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
- * https://openapi-generator.tech
- * Do not edit the class manually.
- */
-
-import { mapValues } from '../runtime';
-import type { CreateShippingRuleRequestAdditionalParametersAnyOfValue } from './CreateShippingRuleRequestAdditionalParametersAnyOfValue';
-import {
-    CreateShippingRuleRequestAdditionalParametersAnyOfValueFromJSON,
-    CreateShippingRuleRequestAdditionalParametersAnyOfValueFromJSONTyped,
-    CreateShippingRuleRequestAdditionalParametersAnyOfValueToJSON,
-    CreateShippingRuleRequestAdditionalParametersAnyOfValueToJSONTyped,
-} from './CreateShippingRuleRequestAdditionalParametersAnyOfValue';
-import type { CreateShippingRuleRequestAdditionalParametersAnyOfInner } from './CreateShippingRuleRequestAdditionalParametersAnyOfInner';
-import {
-    CreateShippingRuleRequestAdditionalParametersAnyOfInnerFromJSON,
-    CreateShippingRuleRequestAdditionalParametersAnyOfInnerFromJSONTyped,
-    CreateShippingRuleRequestAdditionalParametersAnyOfInnerToJSON,
-    CreateShippingRuleRequestAdditionalParametersAnyOfInnerToJSONTyped,
-} from './CreateShippingRuleRequestAdditionalParametersAnyOfInner';
-
-/**
- * Carrier-specific extra parameters. Accepts EITHER the `{ key: value }` object (preferred) OR the legacy `[{ name, val }]` array, so you can migrate on your own schedule. Each key / `name` is the carrier parameter `key` from the product's `additionalParameters[].key` (e.g. `returnFunctionality`).
- * @export
- * @interface CreateShippingRuleRequestAdditionalParameters
- */
-export interface CreateShippingRuleRequestAdditionalParameters {
-}
-
-/**
- * Check if a given object implements the CreateShippingRuleRequestAdditionalParameters interface.
- */
-export function instanceOfCreateShippingRuleRequestAdditionalParameters(value: object): value is CreateShippingRuleRequestAdditionalParameters {
-    return true;
-}
-
-export function CreateShippingRuleRequestAdditionalParametersFromJSON(json: any): CreateShippingRuleRequestAdditionalParameters {
-    return CreateShippingRuleRequestAdditionalParametersFromJSONTyped(json, false);
-}
-
-export function CreateShippingRuleRequestAdditionalParametersFromJSONTyped(json: any, ignoreDiscriminator: boolean): CreateShippingRuleRequestAdditionalParameters {
-    return json;
-}
-
-export function CreateShippingRuleRequestAdditionalParametersToJSON(json: any): CreateShippingRuleRequestAdditionalParameters {
-    return CreateShippingRuleRequestAdditionalParametersToJSONTyped(json, false);
-}
-
-export function CreateShippingRuleRequestAdditionalParametersToJSONTyped(value?: CreateShippingRuleRequestAdditionalParameters | null, ignoreDiscriminator: boolean = false): any {
-    return value;
-}
-

package/src/models/CreateShippingRuleRequestAdditionalParametersAnyOfInner.ts

@@ -1,75 +0,0 @@
-/* tslint:disable */
-/* 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.  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
- *
- * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
- * https://openapi-generator.tech
- * Do not edit the class manually.
- */
-
-import { mapValues } from '../runtime';
-/**
- * 
- * @export
- * @interface CreateShippingRuleRequestAdditionalParametersAnyOfInner
- */
-export interface CreateShippingRuleRequestAdditionalParametersAnyOfInner {
-    /**
-     * Carrier parameter key
-     * @type {string}
-     * @memberof CreateShippingRuleRequestAdditionalParametersAnyOfInner
-     */
-    name: string;
-    /**
-     * Parameter value (stringified)
-     * @type {string}
-     * @memberof CreateShippingRuleRequestAdditionalParametersAnyOfInner
-     */
-    val: string;
-}
-
-/**
- * Check if a given object implements the CreateShippingRuleRequestAdditionalParametersAnyOfInner interface.
- */
-export function instanceOfCreateShippingRuleRequestAdditionalParametersAnyOfInner(value: object): value is CreateShippingRuleRequestAdditionalParametersAnyOfInner {
-    if (!('name' in value) || value['name'] === undefined) return false;
-    if (!('val' in value) || value['val'] === undefined) return false;
-    return true;
-}
-
-export function CreateShippingRuleRequestAdditionalParametersAnyOfInnerFromJSON(json: any): CreateShippingRuleRequestAdditionalParametersAnyOfInner {
-    return CreateShippingRuleRequestAdditionalParametersAnyOfInnerFromJSONTyped(json, false);
-}
-
-export function CreateShippingRuleRequestAdditionalParametersAnyOfInnerFromJSONTyped(json: any, ignoreDiscriminator: boolean): CreateShippingRuleRequestAdditionalParametersAnyOfInner {
-    if (json == null) {
-        return json;
-    }
-    return {
-        
-        'name': json['name'],
-        'val': json['val'],
-    };
-}
-
-export function CreateShippingRuleRequestAdditionalParametersAnyOfInnerToJSON(json: any): CreateShippingRuleRequestAdditionalParametersAnyOfInner {
-    return CreateShippingRuleRequestAdditionalParametersAnyOfInnerToJSONTyped(json, false);
-}
-
-export function CreateShippingRuleRequestAdditionalParametersAnyOfInnerToJSONTyped(value?: CreateShippingRuleRequestAdditionalParametersAnyOfInner | null, ignoreDiscriminator: boolean = false): any {
-    if (value == null) {
-        return value;
-    }
-
-    return {
-        
-        'name': value['name'],
-        'val': value['val'],
-    };
-}
-

package/src/models/CreateShippingRuleRequestAdditionalParametersAnyOfValueAnyOfCoordinatesInner.ts

@@ -1,46 +0,0 @@
-/* tslint:disable */
-/* 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.  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
- *
- * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
- * https://openapi-generator.tech
- * Do not edit the class manually.
- */
-
-import { mapValues } from '../runtime';
-/**
- * 
- * @export
- * @interface CreateShippingRuleRequestAdditionalParametersAnyOfValueAnyOfCoordinatesInner
- */
-export interface CreateShippingRuleRequestAdditionalParametersAnyOfValueAnyOfCoordinatesInner {
-}
-
-/**
- * Check if a given object implements the CreateShippingRuleRequestAdditionalParametersAnyOfValueAnyOfCoordinatesInner interface.
- */
-export function instanceOfCreateShippingRuleRequestAdditionalParametersAnyOfValueAnyOfCoordinatesInner(value: object): value is CreateShippingRuleRequestAdditionalParametersAnyOfValueAnyOfCoordinatesInner {
-    return true;
-}
-
-export function CreateShippingRuleRequestAdditionalParametersAnyOfValueAnyOfCoordinatesInnerFromJSON(json: any): CreateShippingRuleRequestAdditionalParametersAnyOfValueAnyOfCoordinatesInner {
-    return CreateShippingRuleRequestAdditionalParametersAnyOfValueAnyOfCoordinatesInnerFromJSONTyped(json, false);
-}
-
-export function CreateShippingRuleRequestAdditionalParametersAnyOfValueAnyOfCoordinatesInnerFromJSONTyped(json: any, ignoreDiscriminator: boolean): CreateShippingRuleRequestAdditionalParametersAnyOfValueAnyOfCoordinatesInner {
-    return json;
-}
-
-export function CreateShippingRuleRequestAdditionalParametersAnyOfValueAnyOfCoordinatesInnerToJSON(json: any): CreateShippingRuleRequestAdditionalParametersAnyOfValueAnyOfCoordinatesInner {
-    return CreateShippingRuleRequestAdditionalParametersAnyOfValueAnyOfCoordinatesInnerToJSONTyped(json, false);
-}
-
-export function CreateShippingRuleRequestAdditionalParametersAnyOfValueAnyOfCoordinatesInnerToJSONTyped(value?: CreateShippingRuleRequestAdditionalParametersAnyOfValueAnyOfCoordinatesInner | null, ignoreDiscriminator: boolean = false): any {
-    return value;
-}
-

package/src/models/ListShipments200ResponseDataInnerCarrierSettingsAdditionalParametersValue.ts

@@ -1,107 +0,0 @@
-/* tslint:disable */
-/* 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.  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
- *
- * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
- * https://openapi-generator.tech
- * Do not edit the class manually.
- */
-
-import { mapValues } from '../runtime';
-import type { ListShipments200ResponseDataInnerCarrierSettingsAdditionalParametersValueAnyOf } from './ListShipments200ResponseDataInnerCarrierSettingsAdditionalParametersValueAnyOf';
-import {
-    ListShipments200ResponseDataInnerCarrierSettingsAdditionalParametersValueAnyOfFromJSON,
-    ListShipments200ResponseDataInnerCarrierSettingsAdditionalParametersValueAnyOfFromJSONTyped,
-    ListShipments200ResponseDataInnerCarrierSettingsAdditionalParametersValueAnyOfToJSON,
-    ListShipments200ResponseDataInnerCarrierSettingsAdditionalParametersValueAnyOfToJSONTyped,
-} from './ListShipments200ResponseDataInnerCarrierSettingsAdditionalParametersValueAnyOf';
-import type { CreateShippingRuleRequestAdditionalParametersAnyOfValueAnyOfCoordinatesInner } from './CreateShippingRuleRequestAdditionalParametersAnyOfValueAnyOfCoordinatesInner';
-import {
-    CreateShippingRuleRequestAdditionalParametersAnyOfValueAnyOfCoordinatesInnerFromJSON,
-    CreateShippingRuleRequestAdditionalParametersAnyOfValueAnyOfCoordinatesInnerFromJSONTyped,
-    CreateShippingRuleRequestAdditionalParametersAnyOfValueAnyOfCoordinatesInnerToJSON,
-    CreateShippingRuleRequestAdditionalParametersAnyOfValueAnyOfCoordinatesInnerToJSONTyped,
-} from './CreateShippingRuleRequestAdditionalParametersAnyOfValueAnyOfCoordinatesInner';
-
-/**
- * 
- * @export
- * @interface ListShipments200ResponseDataInnerCarrierSettingsAdditionalParametersValue
- */
-export interface ListShipments200ResponseDataInnerCarrierSettingsAdditionalParametersValue {
-    /**
-     * Identifier of the selected service point.
-     * @type {string}
-     * @memberof ListShipments200ResponseDataInnerCarrierSettingsAdditionalParametersValue
-     */
-    id: string;
-    /**
-     * Display name of the service point.
-     * @type {string}
-     * @memberof ListShipments200ResponseDataInnerCarrierSettingsAdditionalParametersValue
-     */
-    name: string;
-    /**
-     * Formatted address of the service point.
-     * @type {string}
-     * @memberof ListShipments200ResponseDataInnerCarrierSettingsAdditionalParametersValue
-     */
-    address: string;
-    /**
-     * Latitude/longitude of the service point.
-     * @type {Array<CreateShippingRuleRequestAdditionalParametersAnyOfValueAnyOfCoordinatesInner>}
-     * @memberof ListShipments200ResponseDataInnerCarrierSettingsAdditionalParametersValue
-     */
-    coordinates?: Array<CreateShippingRuleRequestAdditionalParametersAnyOfValueAnyOfCoordinatesInner>;
-}
-
-/**
- * Check if a given object implements the ListShipments200ResponseDataInnerCarrierSettingsAdditionalParametersValue interface.
- */
-export function instanceOfListShipments200ResponseDataInnerCarrierSettingsAdditionalParametersValue(value: object): value is ListShipments200ResponseDataInnerCarrierSettingsAdditionalParametersValue {
-    if (!('id' in value) || value['id'] === undefined) return false;
-    if (!('name' in value) || value['name'] === undefined) return false;
-    if (!('address' in value) || value['address'] === undefined) return false;
-    return true;
-}
-
-export function ListShipments200ResponseDataInnerCarrierSettingsAdditionalParametersValueFromJSON(json: any): ListShipments200ResponseDataInnerCarrierSettingsAdditionalParametersValue {
-    return ListShipments200ResponseDataInnerCarrierSettingsAdditionalParametersValueFromJSONTyped(json, false);
-}
-
-export function ListShipments200ResponseDataInnerCarrierSettingsAdditionalParametersValueFromJSONTyped(json: any, ignoreDiscriminator: boolean): ListShipments200ResponseDataInnerCarrierSettingsAdditionalParametersValue {
-    if (json == null) {
-        return json;
-    }
-    return {
-        
-        'id': json['id'],
-        'name': json['name'],
-        'address': json['address'],
-        'coordinates': json['coordinates'] == null ? undefined : ((json['coordinates'] as Array<any>).map(CreateShippingRuleRequestAdditionalParametersAnyOfValueAnyOfCoordinatesInnerFromJSON)),
-    };
-}
-
-export function ListShipments200ResponseDataInnerCarrierSettingsAdditionalParametersValueToJSON(json: any): ListShipments200ResponseDataInnerCarrierSettingsAdditionalParametersValue {
-    return ListShipments200ResponseDataInnerCarrierSettingsAdditionalParametersValueToJSONTyped(json, false);
-}
-
-export function ListShipments200ResponseDataInnerCarrierSettingsAdditionalParametersValueToJSONTyped(value?: ListShipments200ResponseDataInnerCarrierSettingsAdditionalParametersValue | null, ignoreDiscriminator: boolean = false): any {
-    if (value == null) {
-        return value;
-    }
-
-    return {
-        
-        'id': value['id'],
-        'name': value['name'],
-        'address': value['address'],
-        'coordinates': value['coordinates'] == null ? undefined : ((value['coordinates'] as Array<any>).map(CreateShippingRuleRequestAdditionalParametersAnyOfValueAnyOfCoordinatesInnerToJSON)),
-    };
-}
-