From c65d4207f1197f3821b179c57948421e825de1a4 Mon Sep 17 00:00:00 2001 From: Daniel K Date: Mon, 26 Feb 2024 00:55:07 -0800 Subject: [PATCH] release: 2024.2.rc7 --- apps/api/karrio/server/VERSION | 2 +- bin/deploy-hobby | 4 +- bin/upgrade-hobby | 2 +- docker/docker-compose.yml | 6 +- packages/hooks/carrier-connections.ts | 4 +- packages/types/rest/api.ts | 4 +- packages/types/rest/base.ts | 4 +- packages/types/rest/common.ts | 4 +- packages/types/rest/configuration.ts | 4 +- packages/types/rest/index.ts | 4 +- requirements.build.txt | 2 + requirements.txt | 131 +++++++------- schemas/graphql-admin.json | 20 +-- schemas/graphql.json | 20 +-- schemas/openapi.yml | 238 ++++++++++++++++---------- source.requirements.txt | 57 +++--- 16 files changed, 273 insertions(+), 233 deletions(-) diff --git a/apps/api/karrio/server/VERSION b/apps/api/karrio/server/VERSION index 500e109833..912e609f0a 100644 --- a/apps/api/karrio/server/VERSION +++ b/apps/api/karrio/server/VERSION @@ -1 +1 @@ -2024.2.rc6 +2024.2.rc7 diff --git a/bin/deploy-hobby b/bin/deploy-hobby index be618b7ac9..f49e6bbc8b 100755 --- a/bin/deploy-hobby +++ b/bin/deploy-hobby @@ -2,7 +2,7 @@ set -e -export KARRIO_TAG="${KARRIO_TAG:-2024.2.rc4}" +export KARRIO_TAG="${KARRIO_TAG:-2024.2.rc7}" export SENTRY_DSN="${SENTRY_DSN:-'https://public@sentry.example.com/1'}" SECRET_KEY=$(head -c 28 /dev/urandom | sha224sum -b | head -c 56) @@ -23,7 +23,7 @@ if ! [ -z "$1" ] then export KARRIO_TAG=$1 else -echo "What version of Karrio would you like to install? (We default to '2024.2.rc4')" +echo "What version of Karrio would you like to install? (We default to '2024.2.rc7')" echo "You can check out available versions here: https://hub.docker.com/r/karrio/server/tags" read -r KARRIO_TAG_READ if [ -z "$KARRIO_TAG_READ" ] diff --git a/bin/upgrade-hobby b/bin/upgrade-hobby index d2cc6a301f..672b662b90 100755 --- a/bin/upgrade-hobby +++ b/bin/upgrade-hobby @@ -44,7 +44,7 @@ else fi [[ -f ".env" ]] && export $(cat .env | xargs) || ( echo "No .env file found. Please create it with SECRET_KEY and DOMAIN set." && exit 1) -export KARRIO_TAG="${KARRIO_TAG:-2024.2.rc4}" +export KARRIO_TAG="${KARRIO_TAG:-2024.2.rc7}" # get karrio scripts mkdir -p ./karrio diff --git a/docker/docker-compose.yml b/docker/docker-compose.yml index 6f3498d1c8..5c838a7dfb 100644 --- a/docker/docker-compose.yml +++ b/docker/docker-compose.yml @@ -3,7 +3,7 @@ version: "3" services: api: container_name: karrio.api - image: karrio.docker.scarf.sh/karrio/server:2024.2.rc4 + image: karrio.docker.scarf.sh/karrio/server:2024.2.rc7 restart: unless-stopped ports: - ${KARRIO_HTTP_PORT}:${KARRIO_HTTP_PORT} @@ -25,7 +25,7 @@ services: worker: container_name: karrio.worker - image: karrio.docker.scarf.sh/karrio/server:2024.2.rc4 + image: karrio.docker.scarf.sh/karrio/server:2024.2.rc7 restart: unless-stopped depends_on: - db @@ -46,7 +46,7 @@ services: dashboard: container_name: karrio.dashboard - image: karrio.docker.scarf.sh/karrio/dashboard:2024.2.rc4 + image: karrio.docker.scarf.sh/karrio/dashboard:2024.2.rc7 restart: unless-stopped ports: - ${DASHBOARD_PORT}:3000/tcp diff --git a/packages/hooks/carrier-connections.ts b/packages/hooks/carrier-connections.ts index 5b265d56d5..c5202f7a5e 100644 --- a/packages/hooks/carrier-connections.ts +++ b/packages/hooks/carrier-connections.ts @@ -14,10 +14,10 @@ export function useConnections() { .reduce( (acc, _) => ({ ...acc, - [_.carrier_name]: [...new Set([ + [_.carrier_name]: [...(new Set([ ...(acc[_.carrier_name] as string[] || []), ...(_.config?.shipping_options || []) - ])] + ])) as any] }), {} as Record, ) diff --git a/packages/types/rest/api.ts b/packages/types/rest/api.ts index 7f13b4768c..d2b7b6847d 100644 --- a/packages/types/rest/api.ts +++ b/packages/types/rest/api.ts @@ -2,9 +2,9 @@ /* eslint-disable */ /** * Karrio API - * ## API Reference Karrio is an open source multi-carrier shipping API that simplifies the integration of logistics carrier services. The Karrio API is organized around REST. Our API has predictable resource-oriented URLs, accepts JSON-encoded request bodies, returns JSON-encoded responses, and uses standard HTTP response codes, authentication, and verbs. The Karrio API differs for every account as we release new versions. These docs are customized to your version of the API. ## Versioning When backwards-incompatible changes are made to the API, a new, dated version is released. The current version is `2024.2.rc6`. Read our API changelog to learn more about backwards compatibility. As a precaution, use API versioning to check a new API version before committing to an upgrade. ## Environments The Karrio API offer the possibility to create and retrieve certain objects in `test_mode`. In development, it is therefore possible to add carrier connections, get live rates, buy labels, create trackers and schedule pickups in `test_mode`. ## Pagination All top-level API resources have support for bulk fetches via \"list\" API methods. For instance, you can list addresses, list shipments, and list trackers. These list API methods share a common structure, taking at least these two parameters: limit, and offset. Karrio utilizes offset-based pagination via the offset and limit parameters. Both parameters take a number as value (see below) and return objects in reverse chronological order. The offset parameter returns objects listed after an index. The limit parameter take a limit on the number of objects to be returned from 1 to 100. ```json { \"count\": 100, \"next\": \"/v1/shipments?limit=25&offset=50\", \"previous\": \"/v1/shipments?limit=25&offset=25\", \"results\": [ { ... }, ] } ``` ## Metadata Updateable Karrio objects—including Shipment and Order have a metadata parameter. You can use this parameter to attach key-value data to these Karrio objects. Metadata is useful for storing additional, structured information on an object. As an example, you could store your user\'s full name and corresponding unique identifier from your system on a Karrio Order object. Do not store any sensitive information as metadata. ## Authentication API keys are used to authenticate requests. You can view and manage your API keys in the Dashboard. Your API keys carry many privileges, so be sure to keep them secure! Do not share your secret API keys in publicly accessible areas such as GitHub, client-side code, and so forth. Authentication to the API is performed via HTTP Basic Auth. Provide your API token as the basic auth username value. You do not need to provide a password. ```shell $ curl https://instance.api.com/v1/shipments \\ -u key_xxxxxx: # The colon prevents curl from asking for a password. ``` If you need to authenticate via bearer auth (e.g., for a cross-origin request), use `-H \"Authorization: Token key_xxxxxx\"` instead of `-u key_xxxxxx`. All API requests must be made over [HTTPS](http://en.wikipedia.org/wiki/HTTP_Secure). API requests without authentication will also fail. + * ## API Reference Karrio is an open source multi-carrier shipping API that simplifies the integration of logistics carrier services. The Karrio API is organized around REST. Our API has predictable resource-oriented URLs, accepts JSON-encoded request bodies, returns JSON-encoded responses, and uses standard HTTP response codes, authentication, and verbs. The Karrio API differs for every account as we release new versions. These docs are customized to your version of the API. ## Versioning When backwards-incompatible changes are made to the API, a new, dated version is released. The current version is `2024.2.rc7`. Read our API changelog to learn more about backwards compatibility. As a precaution, use API versioning to check a new API version before committing to an upgrade. ## Environments The Karrio API offer the possibility to create and retrieve certain objects in `test_mode`. In development, it is therefore possible to add carrier connections, get live rates, buy labels, create trackers and schedule pickups in `test_mode`. ## Pagination All top-level API resources have support for bulk fetches via \"list\" API methods. For instance, you can list addresses, list shipments, and list trackers. These list API methods share a common structure, taking at least these two parameters: limit, and offset. Karrio utilizes offset-based pagination via the offset and limit parameters. Both parameters take a number as value (see below) and return objects in reverse chronological order. The offset parameter returns objects listed after an index. The limit parameter take a limit on the number of objects to be returned from 1 to 100. ```json { \"count\": 100, \"next\": \"/v1/shipments?limit=25&offset=50\", \"previous\": \"/v1/shipments?limit=25&offset=25\", \"results\": [ { ... }, ] } ``` ## Metadata Updateable Karrio objects—including Shipment and Order have a metadata parameter. You can use this parameter to attach key-value data to these Karrio objects. Metadata is useful for storing additional, structured information on an object. As an example, you could store your user\'s full name and corresponding unique identifier from your system on a Karrio Order object. Do not store any sensitive information as metadata. ## Authentication API keys are used to authenticate requests. You can view and manage your API keys in the Dashboard. Your API keys carry many privileges, so be sure to keep them secure! Do not share your secret API keys in publicly accessible areas such as GitHub, client-side code, and so forth. Authentication to the API is performed via HTTP Basic Auth. Provide your API token as the basic auth username value. You do not need to provide a password. ```shell $ curl https://instance.api.com/v1/shipments \\ -u key_xxxxxx: # The colon prevents curl from asking for a password. ``` If you need to authenticate via bearer auth (e.g., for a cross-origin request), use `-H \"Authorization: Token key_xxxxxx\"` instead of `-u key_xxxxxx`. All API requests must be made over [HTTPS](http://en.wikipedia.org/wiki/HTTP_Secure). API requests without authentication will also fail. * - * The version of the OpenAPI document: 2024.2.rc6 + * The version of the OpenAPI document: 2024.2.rc7 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/packages/types/rest/base.ts b/packages/types/rest/base.ts index 613ac8e74e..d19f68f5ae 100644 --- a/packages/types/rest/base.ts +++ b/packages/types/rest/base.ts @@ -2,9 +2,9 @@ /* eslint-disable */ /** * Karrio API - * ## API Reference Karrio is an open source multi-carrier shipping API that simplifies the integration of logistics carrier services. The Karrio API is organized around REST. Our API has predictable resource-oriented URLs, accepts JSON-encoded request bodies, returns JSON-encoded responses, and uses standard HTTP response codes, authentication, and verbs. The Karrio API differs for every account as we release new versions. These docs are customized to your version of the API. ## Versioning When backwards-incompatible changes are made to the API, a new, dated version is released. The current version is `2024.2.rc6`. Read our API changelog to learn more about backwards compatibility. As a precaution, use API versioning to check a new API version before committing to an upgrade. ## Environments The Karrio API offer the possibility to create and retrieve certain objects in `test_mode`. In development, it is therefore possible to add carrier connections, get live rates, buy labels, create trackers and schedule pickups in `test_mode`. ## Pagination All top-level API resources have support for bulk fetches via \"list\" API methods. For instance, you can list addresses, list shipments, and list trackers. These list API methods share a common structure, taking at least these two parameters: limit, and offset. Karrio utilizes offset-based pagination via the offset and limit parameters. Both parameters take a number as value (see below) and return objects in reverse chronological order. The offset parameter returns objects listed after an index. The limit parameter take a limit on the number of objects to be returned from 1 to 100. ```json { \"count\": 100, \"next\": \"/v1/shipments?limit=25&offset=50\", \"previous\": \"/v1/shipments?limit=25&offset=25\", \"results\": [ { ... }, ] } ``` ## Metadata Updateable Karrio objects—including Shipment and Order have a metadata parameter. You can use this parameter to attach key-value data to these Karrio objects. Metadata is useful for storing additional, structured information on an object. As an example, you could store your user\'s full name and corresponding unique identifier from your system on a Karrio Order object. Do not store any sensitive information as metadata. ## Authentication API keys are used to authenticate requests. You can view and manage your API keys in the Dashboard. Your API keys carry many privileges, so be sure to keep them secure! Do not share your secret API keys in publicly accessible areas such as GitHub, client-side code, and so forth. Authentication to the API is performed via HTTP Basic Auth. Provide your API token as the basic auth username value. You do not need to provide a password. ```shell $ curl https://instance.api.com/v1/shipments \\ -u key_xxxxxx: # The colon prevents curl from asking for a password. ``` If you need to authenticate via bearer auth (e.g., for a cross-origin request), use `-H \"Authorization: Token key_xxxxxx\"` instead of `-u key_xxxxxx`. All API requests must be made over [HTTPS](http://en.wikipedia.org/wiki/HTTP_Secure). API requests without authentication will also fail. + * ## API Reference Karrio is an open source multi-carrier shipping API that simplifies the integration of logistics carrier services. The Karrio API is organized around REST. Our API has predictable resource-oriented URLs, accepts JSON-encoded request bodies, returns JSON-encoded responses, and uses standard HTTP response codes, authentication, and verbs. The Karrio API differs for every account as we release new versions. These docs are customized to your version of the API. ## Versioning When backwards-incompatible changes are made to the API, a new, dated version is released. The current version is `2024.2.rc7`. Read our API changelog to learn more about backwards compatibility. As a precaution, use API versioning to check a new API version before committing to an upgrade. ## Environments The Karrio API offer the possibility to create and retrieve certain objects in `test_mode`. In development, it is therefore possible to add carrier connections, get live rates, buy labels, create trackers and schedule pickups in `test_mode`. ## Pagination All top-level API resources have support for bulk fetches via \"list\" API methods. For instance, you can list addresses, list shipments, and list trackers. These list API methods share a common structure, taking at least these two parameters: limit, and offset. Karrio utilizes offset-based pagination via the offset and limit parameters. Both parameters take a number as value (see below) and return objects in reverse chronological order. The offset parameter returns objects listed after an index. The limit parameter take a limit on the number of objects to be returned from 1 to 100. ```json { \"count\": 100, \"next\": \"/v1/shipments?limit=25&offset=50\", \"previous\": \"/v1/shipments?limit=25&offset=25\", \"results\": [ { ... }, ] } ``` ## Metadata Updateable Karrio objects—including Shipment and Order have a metadata parameter. You can use this parameter to attach key-value data to these Karrio objects. Metadata is useful for storing additional, structured information on an object. As an example, you could store your user\'s full name and corresponding unique identifier from your system on a Karrio Order object. Do not store any sensitive information as metadata. ## Authentication API keys are used to authenticate requests. You can view and manage your API keys in the Dashboard. Your API keys carry many privileges, so be sure to keep them secure! Do not share your secret API keys in publicly accessible areas such as GitHub, client-side code, and so forth. Authentication to the API is performed via HTTP Basic Auth. Provide your API token as the basic auth username value. You do not need to provide a password. ```shell $ curl https://instance.api.com/v1/shipments \\ -u key_xxxxxx: # The colon prevents curl from asking for a password. ``` If you need to authenticate via bearer auth (e.g., for a cross-origin request), use `-H \"Authorization: Token key_xxxxxx\"` instead of `-u key_xxxxxx`. All API requests must be made over [HTTPS](http://en.wikipedia.org/wiki/HTTP_Secure). API requests without authentication will also fail. * - * The version of the OpenAPI document: 2024.2.rc6 + * The version of the OpenAPI document: 2024.2.rc7 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/packages/types/rest/common.ts b/packages/types/rest/common.ts index a915e033e2..d588b04196 100644 --- a/packages/types/rest/common.ts +++ b/packages/types/rest/common.ts @@ -2,9 +2,9 @@ /* eslint-disable */ /** * Karrio API - * ## API Reference Karrio is an open source multi-carrier shipping API that simplifies the integration of logistics carrier services. The Karrio API is organized around REST. Our API has predictable resource-oriented URLs, accepts JSON-encoded request bodies, returns JSON-encoded responses, and uses standard HTTP response codes, authentication, and verbs. The Karrio API differs for every account as we release new versions. These docs are customized to your version of the API. ## Versioning When backwards-incompatible changes are made to the API, a new, dated version is released. The current version is `2024.2.rc6`. Read our API changelog to learn more about backwards compatibility. As a precaution, use API versioning to check a new API version before committing to an upgrade. ## Environments The Karrio API offer the possibility to create and retrieve certain objects in `test_mode`. In development, it is therefore possible to add carrier connections, get live rates, buy labels, create trackers and schedule pickups in `test_mode`. ## Pagination All top-level API resources have support for bulk fetches via \"list\" API methods. For instance, you can list addresses, list shipments, and list trackers. These list API methods share a common structure, taking at least these two parameters: limit, and offset. Karrio utilizes offset-based pagination via the offset and limit parameters. Both parameters take a number as value (see below) and return objects in reverse chronological order. The offset parameter returns objects listed after an index. The limit parameter take a limit on the number of objects to be returned from 1 to 100. ```json { \"count\": 100, \"next\": \"/v1/shipments?limit=25&offset=50\", \"previous\": \"/v1/shipments?limit=25&offset=25\", \"results\": [ { ... }, ] } ``` ## Metadata Updateable Karrio objects—including Shipment and Order have a metadata parameter. You can use this parameter to attach key-value data to these Karrio objects. Metadata is useful for storing additional, structured information on an object. As an example, you could store your user\'s full name and corresponding unique identifier from your system on a Karrio Order object. Do not store any sensitive information as metadata. ## Authentication API keys are used to authenticate requests. You can view and manage your API keys in the Dashboard. Your API keys carry many privileges, so be sure to keep them secure! Do not share your secret API keys in publicly accessible areas such as GitHub, client-side code, and so forth. Authentication to the API is performed via HTTP Basic Auth. Provide your API token as the basic auth username value. You do not need to provide a password. ```shell $ curl https://instance.api.com/v1/shipments \\ -u key_xxxxxx: # The colon prevents curl from asking for a password. ``` If you need to authenticate via bearer auth (e.g., for a cross-origin request), use `-H \"Authorization: Token key_xxxxxx\"` instead of `-u key_xxxxxx`. All API requests must be made over [HTTPS](http://en.wikipedia.org/wiki/HTTP_Secure). API requests without authentication will also fail. + * ## API Reference Karrio is an open source multi-carrier shipping API that simplifies the integration of logistics carrier services. The Karrio API is organized around REST. Our API has predictable resource-oriented URLs, accepts JSON-encoded request bodies, returns JSON-encoded responses, and uses standard HTTP response codes, authentication, and verbs. The Karrio API differs for every account as we release new versions. These docs are customized to your version of the API. ## Versioning When backwards-incompatible changes are made to the API, a new, dated version is released. The current version is `2024.2.rc7`. Read our API changelog to learn more about backwards compatibility. As a precaution, use API versioning to check a new API version before committing to an upgrade. ## Environments The Karrio API offer the possibility to create and retrieve certain objects in `test_mode`. In development, it is therefore possible to add carrier connections, get live rates, buy labels, create trackers and schedule pickups in `test_mode`. ## Pagination All top-level API resources have support for bulk fetches via \"list\" API methods. For instance, you can list addresses, list shipments, and list trackers. These list API methods share a common structure, taking at least these two parameters: limit, and offset. Karrio utilizes offset-based pagination via the offset and limit parameters. Both parameters take a number as value (see below) and return objects in reverse chronological order. The offset parameter returns objects listed after an index. The limit parameter take a limit on the number of objects to be returned from 1 to 100. ```json { \"count\": 100, \"next\": \"/v1/shipments?limit=25&offset=50\", \"previous\": \"/v1/shipments?limit=25&offset=25\", \"results\": [ { ... }, ] } ``` ## Metadata Updateable Karrio objects—including Shipment and Order have a metadata parameter. You can use this parameter to attach key-value data to these Karrio objects. Metadata is useful for storing additional, structured information on an object. As an example, you could store your user\'s full name and corresponding unique identifier from your system on a Karrio Order object. Do not store any sensitive information as metadata. ## Authentication API keys are used to authenticate requests. You can view and manage your API keys in the Dashboard. Your API keys carry many privileges, so be sure to keep them secure! Do not share your secret API keys in publicly accessible areas such as GitHub, client-side code, and so forth. Authentication to the API is performed via HTTP Basic Auth. Provide your API token as the basic auth username value. You do not need to provide a password. ```shell $ curl https://instance.api.com/v1/shipments \\ -u key_xxxxxx: # The colon prevents curl from asking for a password. ``` If you need to authenticate via bearer auth (e.g., for a cross-origin request), use `-H \"Authorization: Token key_xxxxxx\"` instead of `-u key_xxxxxx`. All API requests must be made over [HTTPS](http://en.wikipedia.org/wiki/HTTP_Secure). API requests without authentication will also fail. * - * The version of the OpenAPI document: 2024.2.rc6 + * The version of the OpenAPI document: 2024.2.rc7 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/packages/types/rest/configuration.ts b/packages/types/rest/configuration.ts index 0d7082c66d..5a20b0b711 100644 --- a/packages/types/rest/configuration.ts +++ b/packages/types/rest/configuration.ts @@ -2,9 +2,9 @@ /* eslint-disable */ /** * Karrio API - * ## API Reference Karrio is an open source multi-carrier shipping API that simplifies the integration of logistics carrier services. The Karrio API is organized around REST. Our API has predictable resource-oriented URLs, accepts JSON-encoded request bodies, returns JSON-encoded responses, and uses standard HTTP response codes, authentication, and verbs. The Karrio API differs for every account as we release new versions. These docs are customized to your version of the API. ## Versioning When backwards-incompatible changes are made to the API, a new, dated version is released. The current version is `2024.2.rc6`. Read our API changelog to learn more about backwards compatibility. As a precaution, use API versioning to check a new API version before committing to an upgrade. ## Environments The Karrio API offer the possibility to create and retrieve certain objects in `test_mode`. In development, it is therefore possible to add carrier connections, get live rates, buy labels, create trackers and schedule pickups in `test_mode`. ## Pagination All top-level API resources have support for bulk fetches via \"list\" API methods. For instance, you can list addresses, list shipments, and list trackers. These list API methods share a common structure, taking at least these two parameters: limit, and offset. Karrio utilizes offset-based pagination via the offset and limit parameters. Both parameters take a number as value (see below) and return objects in reverse chronological order. The offset parameter returns objects listed after an index. The limit parameter take a limit on the number of objects to be returned from 1 to 100. ```json { \"count\": 100, \"next\": \"/v1/shipments?limit=25&offset=50\", \"previous\": \"/v1/shipments?limit=25&offset=25\", \"results\": [ { ... }, ] } ``` ## Metadata Updateable Karrio objects—including Shipment and Order have a metadata parameter. You can use this parameter to attach key-value data to these Karrio objects. Metadata is useful for storing additional, structured information on an object. As an example, you could store your user\'s full name and corresponding unique identifier from your system on a Karrio Order object. Do not store any sensitive information as metadata. ## Authentication API keys are used to authenticate requests. You can view and manage your API keys in the Dashboard. Your API keys carry many privileges, so be sure to keep them secure! Do not share your secret API keys in publicly accessible areas such as GitHub, client-side code, and so forth. Authentication to the API is performed via HTTP Basic Auth. Provide your API token as the basic auth username value. You do not need to provide a password. ```shell $ curl https://instance.api.com/v1/shipments \\ -u key_xxxxxx: # The colon prevents curl from asking for a password. ``` If you need to authenticate via bearer auth (e.g., for a cross-origin request), use `-H \"Authorization: Token key_xxxxxx\"` instead of `-u key_xxxxxx`. All API requests must be made over [HTTPS](http://en.wikipedia.org/wiki/HTTP_Secure). API requests without authentication will also fail. + * ## API Reference Karrio is an open source multi-carrier shipping API that simplifies the integration of logistics carrier services. The Karrio API is organized around REST. Our API has predictable resource-oriented URLs, accepts JSON-encoded request bodies, returns JSON-encoded responses, and uses standard HTTP response codes, authentication, and verbs. The Karrio API differs for every account as we release new versions. These docs are customized to your version of the API. ## Versioning When backwards-incompatible changes are made to the API, a new, dated version is released. The current version is `2024.2.rc7`. Read our API changelog to learn more about backwards compatibility. As a precaution, use API versioning to check a new API version before committing to an upgrade. ## Environments The Karrio API offer the possibility to create and retrieve certain objects in `test_mode`. In development, it is therefore possible to add carrier connections, get live rates, buy labels, create trackers and schedule pickups in `test_mode`. ## Pagination All top-level API resources have support for bulk fetches via \"list\" API methods. For instance, you can list addresses, list shipments, and list trackers. These list API methods share a common structure, taking at least these two parameters: limit, and offset. Karrio utilizes offset-based pagination via the offset and limit parameters. Both parameters take a number as value (see below) and return objects in reverse chronological order. The offset parameter returns objects listed after an index. The limit parameter take a limit on the number of objects to be returned from 1 to 100. ```json { \"count\": 100, \"next\": \"/v1/shipments?limit=25&offset=50\", \"previous\": \"/v1/shipments?limit=25&offset=25\", \"results\": [ { ... }, ] } ``` ## Metadata Updateable Karrio objects—including Shipment and Order have a metadata parameter. You can use this parameter to attach key-value data to these Karrio objects. Metadata is useful for storing additional, structured information on an object. As an example, you could store your user\'s full name and corresponding unique identifier from your system on a Karrio Order object. Do not store any sensitive information as metadata. ## Authentication API keys are used to authenticate requests. You can view and manage your API keys in the Dashboard. Your API keys carry many privileges, so be sure to keep them secure! Do not share your secret API keys in publicly accessible areas such as GitHub, client-side code, and so forth. Authentication to the API is performed via HTTP Basic Auth. Provide your API token as the basic auth username value. You do not need to provide a password. ```shell $ curl https://instance.api.com/v1/shipments \\ -u key_xxxxxx: # The colon prevents curl from asking for a password. ``` If you need to authenticate via bearer auth (e.g., for a cross-origin request), use `-H \"Authorization: Token key_xxxxxx\"` instead of `-u key_xxxxxx`. All API requests must be made over [HTTPS](http://en.wikipedia.org/wiki/HTTP_Secure). API requests without authentication will also fail. * - * The version of the OpenAPI document: 2024.2.rc6 + * The version of the OpenAPI document: 2024.2.rc7 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/packages/types/rest/index.ts b/packages/types/rest/index.ts index 0e05fa541c..f544cfcb09 100644 --- a/packages/types/rest/index.ts +++ b/packages/types/rest/index.ts @@ -2,9 +2,9 @@ /* eslint-disable */ /** * Karrio API - * ## API Reference Karrio is an open source multi-carrier shipping API that simplifies the integration of logistics carrier services. The Karrio API is organized around REST. Our API has predictable resource-oriented URLs, accepts JSON-encoded request bodies, returns JSON-encoded responses, and uses standard HTTP response codes, authentication, and verbs. The Karrio API differs for every account as we release new versions. These docs are customized to your version of the API. ## Versioning When backwards-incompatible changes are made to the API, a new, dated version is released. The current version is `2024.2.rc6`. Read our API changelog to learn more about backwards compatibility. As a precaution, use API versioning to check a new API version before committing to an upgrade. ## Environments The Karrio API offer the possibility to create and retrieve certain objects in `test_mode`. In development, it is therefore possible to add carrier connections, get live rates, buy labels, create trackers and schedule pickups in `test_mode`. ## Pagination All top-level API resources have support for bulk fetches via \"list\" API methods. For instance, you can list addresses, list shipments, and list trackers. These list API methods share a common structure, taking at least these two parameters: limit, and offset. Karrio utilizes offset-based pagination via the offset and limit parameters. Both parameters take a number as value (see below) and return objects in reverse chronological order. The offset parameter returns objects listed after an index. The limit parameter take a limit on the number of objects to be returned from 1 to 100. ```json { \"count\": 100, \"next\": \"/v1/shipments?limit=25&offset=50\", \"previous\": \"/v1/shipments?limit=25&offset=25\", \"results\": [ { ... }, ] } ``` ## Metadata Updateable Karrio objects—including Shipment and Order have a metadata parameter. You can use this parameter to attach key-value data to these Karrio objects. Metadata is useful for storing additional, structured information on an object. As an example, you could store your user\'s full name and corresponding unique identifier from your system on a Karrio Order object. Do not store any sensitive information as metadata. ## Authentication API keys are used to authenticate requests. You can view and manage your API keys in the Dashboard. Your API keys carry many privileges, so be sure to keep them secure! Do not share your secret API keys in publicly accessible areas such as GitHub, client-side code, and so forth. Authentication to the API is performed via HTTP Basic Auth. Provide your API token as the basic auth username value. You do not need to provide a password. ```shell $ curl https://instance.api.com/v1/shipments \\ -u key_xxxxxx: # The colon prevents curl from asking for a password. ``` If you need to authenticate via bearer auth (e.g., for a cross-origin request), use `-H \"Authorization: Token key_xxxxxx\"` instead of `-u key_xxxxxx`. All API requests must be made over [HTTPS](http://en.wikipedia.org/wiki/HTTP_Secure). API requests without authentication will also fail. + * ## API Reference Karrio is an open source multi-carrier shipping API that simplifies the integration of logistics carrier services. The Karrio API is organized around REST. Our API has predictable resource-oriented URLs, accepts JSON-encoded request bodies, returns JSON-encoded responses, and uses standard HTTP response codes, authentication, and verbs. The Karrio API differs for every account as we release new versions. These docs are customized to your version of the API. ## Versioning When backwards-incompatible changes are made to the API, a new, dated version is released. The current version is `2024.2.rc7`. Read our API changelog to learn more about backwards compatibility. As a precaution, use API versioning to check a new API version before committing to an upgrade. ## Environments The Karrio API offer the possibility to create and retrieve certain objects in `test_mode`. In development, it is therefore possible to add carrier connections, get live rates, buy labels, create trackers and schedule pickups in `test_mode`. ## Pagination All top-level API resources have support for bulk fetches via \"list\" API methods. For instance, you can list addresses, list shipments, and list trackers. These list API methods share a common structure, taking at least these two parameters: limit, and offset. Karrio utilizes offset-based pagination via the offset and limit parameters. Both parameters take a number as value (see below) and return objects in reverse chronological order. The offset parameter returns objects listed after an index. The limit parameter take a limit on the number of objects to be returned from 1 to 100. ```json { \"count\": 100, \"next\": \"/v1/shipments?limit=25&offset=50\", \"previous\": \"/v1/shipments?limit=25&offset=25\", \"results\": [ { ... }, ] } ``` ## Metadata Updateable Karrio objects—including Shipment and Order have a metadata parameter. You can use this parameter to attach key-value data to these Karrio objects. Metadata is useful for storing additional, structured information on an object. As an example, you could store your user\'s full name and corresponding unique identifier from your system on a Karrio Order object. Do not store any sensitive information as metadata. ## Authentication API keys are used to authenticate requests. You can view and manage your API keys in the Dashboard. Your API keys carry many privileges, so be sure to keep them secure! Do not share your secret API keys in publicly accessible areas such as GitHub, client-side code, and so forth. Authentication to the API is performed via HTTP Basic Auth. Provide your API token as the basic auth username value. You do not need to provide a password. ```shell $ curl https://instance.api.com/v1/shipments \\ -u key_xxxxxx: # The colon prevents curl from asking for a password. ``` If you need to authenticate via bearer auth (e.g., for a cross-origin request), use `-H \"Authorization: Token key_xxxxxx\"` instead of `-u key_xxxxxx`. All API requests must be made over [HTTPS](http://en.wikipedia.org/wiki/HTTP_Secure). API requests without authentication will also fail. * - * The version of the OpenAPI document: 2024.2.rc6 + * The version of the OpenAPI document: 2024.2.rc7 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/requirements.build.txt b/requirements.build.txt index 6b7329705a..982a4e592e 100644 --- a/requirements.build.txt +++ b/requirements.build.txt @@ -16,12 +16,14 @@ Django==4.2.10 -e ./modules/connectors/chronopost -e ./modules/connectors/colissimo -e ./modules/connectors/dhl_express +-e ./modules/connectors/dhl_parcel_de -e ./modules/connectors/dhl_poland -e ./modules/connectors/dhl_universal -e ./modules/connectors/dicom -e ./modules/connectors/dpd -e ./modules/connectors/dpdhl -e ./modules/connectors/fedex +-e ./modules/connectors/fedex_ws -e ./modules/connectors/generic -e ./modules/connectors/geodis -e ./modules/connectors/laposte diff --git a/requirements.txt b/requirements.txt index 5f91317575..40607c87b5 100644 --- a/requirements.txt +++ b/requirements.txt @@ -7,10 +7,9 @@ certifi==2024.2.2 cffi==1.16.0 charset-normalizer==3.3.2 click==8.1.7 -cryptography==42.0.4 +cryptography==42.0.5 cssselect2==0.7.0 defusedxml==0.7.1 -Deprecated==1.2.14 deprecation==2.1.0 diff-match-patch==20230430 dj-database-url==2.1.0 @@ -22,19 +21,19 @@ django-email-verification==0.3.3 django-filter==23.5 django-formtools==2.5.1 django-health-check==3.18.1 -django-import-export==3.3.6 +django-import-export==3.3.7 django-oauth-toolkit==2.3.0 django-otp==1.3.0 django-phonenumber-field==7.3.0 django-picklefield==3.1 django-redis==5.4.0 -django-two-factor-auth==1.15.5 +django-two-factor-auth==1.16.0 djangorestframework==3.14.0 djangorestframework-simplejwt==5.3.1 drf-api-tracking==1.8.4 drf-spectacular==0.27.1 et-xmlfile==1.1.0 -fonttools==4.47.2 +fonttools==4.49.0 graphql-core==3.2.3 gunicorn==21.2.0 h11==0.14.0 @@ -48,55 +47,58 @@ jsonfield==3.1.0 jsonschema==4.21.1 jsonschema-specifications==2023.12.1 jstruct==2021.11 -jwcrypto==1.5.1 --e git+ssh://git@github.com/karrioapi/karrio.git@5e9f9a780e415b75a7a0e62831e943b5383137e9#egg=karrio&subdirectory=modules/sdk --e git+ssh://git@github.com/karrioapi/karrio.git@5e9f9a780e415b75a7a0e62831e943b5383137e9#egg=karrio.allied_express&subdirectory=modules/connectors/allied_express --e git+ssh://git@github.com/karrioapi/karrio.git@5e9f9a780e415b75a7a0e62831e943b5383137e9#egg=karrio.amazon_shipping&subdirectory=modules/connectors/amazon_shipping --e git+ssh://git@github.com/karrioapi/karrio.git@5e9f9a780e415b75a7a0e62831e943b5383137e9#egg=karrio.aramex&subdirectory=modules/connectors/aramex --e git+ssh://git@github.com/karrioapi/karrio.git@5e9f9a780e415b75a7a0e62831e943b5383137e9#egg=karrio.asendia_us&subdirectory=modules/connectors/asendia_us --e git+ssh://git@github.com/karrioapi/karrio.git@5e9f9a780e415b75a7a0e62831e943b5383137e9#egg=karrio.australiapost&subdirectory=modules/connectors/australiapost --e git+ssh://git@github.com/karrioapi/karrio.git@5e9f9a780e415b75a7a0e62831e943b5383137e9#egg=karrio.boxknight&subdirectory=modules/connectors/boxknight --e git+ssh://git@github.com/karrioapi/karrio.git@5e9f9a780e415b75a7a0e62831e943b5383137e9#egg=karrio.bpost&subdirectory=modules/connectors/bpost --e git+ssh://git@github.com/karrioapi/karrio.git@5e9f9a780e415b75a7a0e62831e943b5383137e9#egg=karrio.canadapost&subdirectory=modules/connectors/canadapost --e git+ssh://git@github.com/karrioapi/karrio.git@5e9f9a780e415b75a7a0e62831e943b5383137e9#egg=karrio.canpar&subdirectory=modules/connectors/canpar --e git+ssh://git@github.com/karrioapi/karrio.git@5e9f9a780e415b75a7a0e62831e943b5383137e9#egg=karrio.chronopost&subdirectory=modules/connectors/chronopost --e git+ssh://git@github.com/karrioapi/karrio.git@5e9f9a780e415b75a7a0e62831e943b5383137e9#egg=karrio.colissimo&subdirectory=modules/connectors/colissimo --e git+ssh://git@github.com/karrioapi/karrio.git@5e9f9a780e415b75a7a0e62831e943b5383137e9#egg=karrio.dhl_express&subdirectory=modules/connectors/dhl_express --e git+ssh://git@github.com/karrioapi/karrio.git@5e9f9a780e415b75a7a0e62831e943b5383137e9#egg=karrio.dhl_poland&subdirectory=modules/connectors/dhl_poland --e git+ssh://git@github.com/karrioapi/karrio.git@5e9f9a780e415b75a7a0e62831e943b5383137e9#egg=karrio.dhl_universal&subdirectory=modules/connectors/dhl_universal --e git+ssh://git@github.com/karrioapi/karrio.git@5e9f9a780e415b75a7a0e62831e943b5383137e9#egg=karrio.dicom&subdirectory=modules/connectors/dicom --e git+ssh://git@github.com/karrioapi/karrio.git@5e9f9a780e415b75a7a0e62831e943b5383137e9#egg=karrio.dpd&subdirectory=modules/connectors/dpd --e git+ssh://git@github.com/karrioapi/karrio.git@5e9f9a780e415b75a7a0e62831e943b5383137e9#egg=karrio.dpdhl&subdirectory=modules/connectors/dpdhl --e git+ssh://git@github.com/karrioapi/karrio.git@5e9f9a780e415b75a7a0e62831e943b5383137e9#egg=karrio.easypost&subdirectory=modules/connectors/easypost --e git+ssh://git@github.com/karrioapi/karrio.git@5e9f9a780e415b75a7a0e62831e943b5383137e9#egg=karrio.eshipper&subdirectory=modules/connectors/eshipper --e git+ssh://git@github.com/karrioapi/karrio.git@5e9f9a780e415b75a7a0e62831e943b5383137e9#egg=karrio.fedex&subdirectory=modules/connectors/fedex --e git+ssh://git@github.com/karrioapi/karrio.git@5e9f9a780e415b75a7a0e62831e943b5383137e9#egg=karrio.freightcom&subdirectory=modules/connectors/freightcom --e git+ssh://git@github.com/karrioapi/karrio.git@5e9f9a780e415b75a7a0e62831e943b5383137e9#egg=karrio.generic&subdirectory=modules/connectors/generic --e git+ssh://git@github.com/karrioapi/karrio.git@5e9f9a780e415b75a7a0e62831e943b5383137e9#egg=karrio.geodis&subdirectory=modules/connectors/geodis --e git+ssh://git@github.com/karrioapi/karrio.git@5e9f9a780e415b75a7a0e62831e943b5383137e9#egg=karrio.laposte&subdirectory=modules/connectors/laposte --e git+ssh://git@github.com/karrioapi/karrio.git@5e9f9a780e415b75a7a0e62831e943b5383137e9#egg=karrio.locate2u&subdirectory=modules/connectors/locate2u --e git+ssh://git@github.com/karrioapi/karrio.git@5e9f9a780e415b75a7a0e62831e943b5383137e9#egg=karrio.nationex&subdirectory=modules/connectors/nationex --e git+ssh://git@github.com/karrioapi/karrio.git@5e9f9a780e415b75a7a0e62831e943b5383137e9#egg=karrio.purolator&subdirectory=modules/connectors/purolator --e git+ssh://git@github.com/karrioapi/karrio.git@5e9f9a780e415b75a7a0e62831e943b5383137e9#egg=karrio.roadie&subdirectory=modules/connectors/roadie --e git+ssh://git@github.com/karrioapi/karrio.git@5e9f9a780e415b75a7a0e62831e943b5383137e9#egg=karrio.royalmail&subdirectory=modules/connectors/royalmail --e git+ssh://git@github.com/karrioapi/karrio.git@5e9f9a780e415b75a7a0e62831e943b5383137e9#egg=karrio.sendle&subdirectory=modules/connectors/sendle --e git+ssh://git@github.com/karrioapi/karrio.git@5e9f9a780e415b75a7a0e62831e943b5383137e9#egg=karrio.server&subdirectory=apps/api --e git+ssh://git@github.com/karrioapi/karrio.git@5e9f9a780e415b75a7a0e62831e943b5383137e9#egg=karrio.server.admin&subdirectory=modules/admin --e git+ssh://git@github.com/karrioapi/karrio.git@5e9f9a780e415b75a7a0e62831e943b5383137e9#egg=karrio.server.apps&subdirectory=modules/apps --e git+ssh://git@github.com/karrioapi/karrio.git@5e9f9a780e415b75a7a0e62831e943b5383137e9#egg=karrio.server.core&subdirectory=modules/core --e git+ssh://git@github.com/karrioapi/karrio.git@5e9f9a780e415b75a7a0e62831e943b5383137e9#egg=karrio.server.data&subdirectory=modules/data --e git+ssh://git@github.com/karrioapi/karrio.git@5e9f9a780e415b75a7a0e62831e943b5383137e9#egg=karrio.server.documents&subdirectory=modules/documents --e git+ssh://git@github.com/karrioapi/karrio.git@5e9f9a780e415b75a7a0e62831e943b5383137e9#egg=karrio.server.events&subdirectory=modules/events --e git+ssh://git@github.com/karrioapi/karrio.git@5e9f9a780e415b75a7a0e62831e943b5383137e9#egg=karrio.server.graph&subdirectory=modules/graph --e git+ssh://git@github.com/karrioapi/karrio.git@5e9f9a780e415b75a7a0e62831e943b5383137e9#egg=karrio.server.manager&subdirectory=modules/manager --e git+ssh://git@github.com/karrioapi/karrio.git@5e9f9a780e415b75a7a0e62831e943b5383137e9#egg=karrio.server.orders&subdirectory=modules/orders --e git+ssh://git@github.com/karrioapi/karrio.git@5e9f9a780e415b75a7a0e62831e943b5383137e9#egg=karrio.server.pricing&subdirectory=modules/pricing --e git+ssh://git@github.com/karrioapi/karrio.git@5e9f9a780e415b75a7a0e62831e943b5383137e9#egg=karrio.server.proxy&subdirectory=modules/proxy --e git+ssh://git@github.com/karrioapi/karrio.git@5e9f9a780e415b75a7a0e62831e943b5383137e9#egg=karrio.tnt&subdirectory=modules/connectors/tnt --e git+ssh://git@github.com/karrioapi/karrio.git@5e9f9a780e415b75a7a0e62831e943b5383137e9#egg=karrio.ups&subdirectory=modules/connectors/ups --e git+ssh://git@github.com/karrioapi/karrio.git@5e9f9a780e415b75a7a0e62831e943b5383137e9#egg=karrio.usps&subdirectory=modules/connectors/usps --e git+ssh://git@github.com/karrioapi/karrio.git@5e9f9a780e415b75a7a0e62831e943b5383137e9#egg=karrio.usps_international&subdirectory=modules/connectors/usps_international --e git+ssh://git@github.com/karrioapi/karrio.git@5e9f9a780e415b75a7a0e62831e943b5383137e9#egg=karrio.zoom2u&subdirectory=modules/connectors/zoom2u +jwcrypto==1.5.4 +-e git+ssh://git@github.com/karrioapi/karrio.git@0ba337cc40b984fddf70a5717accd7704fd9b610#egg=karrio&subdirectory=modules/sdk +-e git+ssh://git@github.com/karrioapi/karrio.git@0ba337cc40b984fddf70a5717accd7704fd9b610#egg=karrio.allied_express&subdirectory=modules/connectors/allied_express +-e git+ssh://git@github.com/karrioapi/karrio.git@0ba337cc40b984fddf70a5717accd7704fd9b610#egg=karrio.allied_express_local&subdirectory=modules/connectors/allied_express_local +-e git+ssh://git@github.com/karrioapi/karrio.git@0ba337cc40b984fddf70a5717accd7704fd9b610#egg=karrio.amazon_shipping&subdirectory=modules/connectors/amazon_shipping +-e git+ssh://git@github.com/karrioapi/karrio.git@0ba337cc40b984fddf70a5717accd7704fd9b610#egg=karrio.aramex&subdirectory=modules/connectors/aramex +-e git+ssh://git@github.com/karrioapi/karrio.git@0ba337cc40b984fddf70a5717accd7704fd9b610#egg=karrio.asendia_us&subdirectory=modules/connectors/asendia_us +-e git+ssh://git@github.com/karrioapi/karrio.git@0ba337cc40b984fddf70a5717accd7704fd9b610#egg=karrio.australiapost&subdirectory=modules/connectors/australiapost +-e git+ssh://git@github.com/karrioapi/karrio.git@0ba337cc40b984fddf70a5717accd7704fd9b610#egg=karrio.boxknight&subdirectory=modules/connectors/boxknight +-e git+ssh://git@github.com/karrioapi/karrio.git@0ba337cc40b984fddf70a5717accd7704fd9b610#egg=karrio.bpost&subdirectory=modules/connectors/bpost +-e git+ssh://git@github.com/karrioapi/karrio.git@0ba337cc40b984fddf70a5717accd7704fd9b610#egg=karrio.canadapost&subdirectory=modules/connectors/canadapost +-e git+ssh://git@github.com/karrioapi/karrio.git@0ba337cc40b984fddf70a5717accd7704fd9b610#egg=karrio.canpar&subdirectory=modules/connectors/canpar +-e git+ssh://git@github.com/karrioapi/karrio.git@0ba337cc40b984fddf70a5717accd7704fd9b610#egg=karrio.chronopost&subdirectory=modules/connectors/chronopost +-e git+ssh://git@github.com/karrioapi/karrio.git@0ba337cc40b984fddf70a5717accd7704fd9b610#egg=karrio.colissimo&subdirectory=modules/connectors/colissimo +-e git+ssh://git@github.com/karrioapi/karrio.git@0ba337cc40b984fddf70a5717accd7704fd9b610#egg=karrio.dhl_express&subdirectory=modules/connectors/dhl_express +-e git+ssh://git@github.com/karrioapi/karrio.git@0ba337cc40b984fddf70a5717accd7704fd9b610#egg=karrio.dhl_parcel_de&subdirectory=modules/connectors/dhl_parcel_de +-e git+ssh://git@github.com/karrioapi/karrio.git@0ba337cc40b984fddf70a5717accd7704fd9b610#egg=karrio.dhl_poland&subdirectory=modules/connectors/dhl_poland +-e git+ssh://git@github.com/karrioapi/karrio.git@0ba337cc40b984fddf70a5717accd7704fd9b610#egg=karrio.dhl_universal&subdirectory=modules/connectors/dhl_universal +-e git+ssh://git@github.com/karrioapi/karrio.git@0ba337cc40b984fddf70a5717accd7704fd9b610#egg=karrio.dicom&subdirectory=modules/connectors/dicom +-e git+ssh://git@github.com/karrioapi/karrio.git@0ba337cc40b984fddf70a5717accd7704fd9b610#egg=karrio.dpd&subdirectory=modules/connectors/dpd +-e git+ssh://git@github.com/karrioapi/karrio.git@0ba337cc40b984fddf70a5717accd7704fd9b610#egg=karrio.dpdhl&subdirectory=modules/connectors/dpdhl +-e git+ssh://git@github.com/karrioapi/karrio.git@0ba337cc40b984fddf70a5717accd7704fd9b610#egg=karrio.easypost&subdirectory=modules/connectors/easypost +-e git+ssh://git@github.com/karrioapi/karrio.git@0ba337cc40b984fddf70a5717accd7704fd9b610#egg=karrio.eshipper&subdirectory=modules/connectors/eshipper +-e git+ssh://git@github.com/karrioapi/karrio.git@0ba337cc40b984fddf70a5717accd7704fd9b610#egg=karrio.fedex&subdirectory=modules/connectors/fedex +-e git+ssh://git@github.com/karrioapi/karrio.git@0ba337cc40b984fddf70a5717accd7704fd9b610#egg=karrio.fedex_ws&subdirectory=modules/connectors/fedex_ws +-e git+ssh://git@github.com/karrioapi/karrio.git@0ba337cc40b984fddf70a5717accd7704fd9b610#egg=karrio.freightcom&subdirectory=modules/connectors/freightcom +-e git+ssh://git@github.com/karrioapi/karrio.git@0ba337cc40b984fddf70a5717accd7704fd9b610#egg=karrio.generic&subdirectory=modules/connectors/generic +-e git+ssh://git@github.com/karrioapi/karrio.git@0ba337cc40b984fddf70a5717accd7704fd9b610#egg=karrio.geodis&subdirectory=modules/connectors/geodis +-e git+ssh://git@github.com/karrioapi/karrio.git@0ba337cc40b984fddf70a5717accd7704fd9b610#egg=karrio.laposte&subdirectory=modules/connectors/laposte +-e git+ssh://git@github.com/karrioapi/karrio.git@0ba337cc40b984fddf70a5717accd7704fd9b610#egg=karrio.locate2u&subdirectory=modules/connectors/locate2u +-e git+ssh://git@github.com/karrioapi/karrio.git@0ba337cc40b984fddf70a5717accd7704fd9b610#egg=karrio.nationex&subdirectory=modules/connectors/nationex +-e git+ssh://git@github.com/karrioapi/karrio.git@0ba337cc40b984fddf70a5717accd7704fd9b610#egg=karrio.purolator&subdirectory=modules/connectors/purolator +-e git+ssh://git@github.com/karrioapi/karrio.git@0ba337cc40b984fddf70a5717accd7704fd9b610#egg=karrio.roadie&subdirectory=modules/connectors/roadie +-e git+ssh://git@github.com/karrioapi/karrio.git@0ba337cc40b984fddf70a5717accd7704fd9b610#egg=karrio.royalmail&subdirectory=modules/connectors/royalmail +-e git+ssh://git@github.com/karrioapi/karrio.git@0ba337cc40b984fddf70a5717accd7704fd9b610#egg=karrio.sendle&subdirectory=modules/connectors/sendle +-e git+ssh://git@github.com/karrioapi/karrio.git@0ba337cc40b984fddf70a5717accd7704fd9b610#egg=karrio.server&subdirectory=apps/api +-e git+ssh://git@github.com/karrioapi/karrio.git@0ba337cc40b984fddf70a5717accd7704fd9b610#egg=karrio.server.admin&subdirectory=modules/admin +-e git+ssh://git@github.com/karrioapi/karrio.git@0ba337cc40b984fddf70a5717accd7704fd9b610#egg=karrio.server.apps&subdirectory=modules/apps +-e git+ssh://git@github.com/karrioapi/karrio.git@0ba337cc40b984fddf70a5717accd7704fd9b610#egg=karrio.server.core&subdirectory=modules/core +-e git+ssh://git@github.com/karrioapi/karrio.git@0ba337cc40b984fddf70a5717accd7704fd9b610#egg=karrio.server.data&subdirectory=modules/data +-e git+ssh://git@github.com/karrioapi/karrio.git@0ba337cc40b984fddf70a5717accd7704fd9b610#egg=karrio.server.documents&subdirectory=modules/documents +-e git+ssh://git@github.com/karrioapi/karrio.git@0ba337cc40b984fddf70a5717accd7704fd9b610#egg=karrio.server.events&subdirectory=modules/events +-e git+ssh://git@github.com/karrioapi/karrio.git@0ba337cc40b984fddf70a5717accd7704fd9b610#egg=karrio.server.graph&subdirectory=modules/graph +-e git+ssh://git@github.com/karrioapi/karrio.git@0ba337cc40b984fddf70a5717accd7704fd9b610#egg=karrio.server.manager&subdirectory=modules/manager +-e git+ssh://git@github.com/karrioapi/karrio.git@0ba337cc40b984fddf70a5717accd7704fd9b610#egg=karrio.server.orders&subdirectory=modules/orders +-e git+ssh://git@github.com/karrioapi/karrio.git@0ba337cc40b984fddf70a5717accd7704fd9b610#egg=karrio.server.pricing&subdirectory=modules/pricing +-e git+ssh://git@github.com/karrioapi/karrio.git@0ba337cc40b984fddf70a5717accd7704fd9b610#egg=karrio.server.proxy&subdirectory=modules/proxy +-e git+ssh://git@github.com/karrioapi/karrio.git@0ba337cc40b984fddf70a5717accd7704fd9b610#egg=karrio.tnt&subdirectory=modules/connectors/tnt +-e git+ssh://git@github.com/karrioapi/karrio.git@0ba337cc40b984fddf70a5717accd7704fd9b610#egg=karrio.ups&subdirectory=modules/connectors/ups +-e git+ssh://git@github.com/karrioapi/karrio.git@0ba337cc40b984fddf70a5717accd7704fd9b610#egg=karrio.usps&subdirectory=modules/connectors/usps +-e git+ssh://git@github.com/karrioapi/karrio.git@0ba337cc40b984fddf70a5717accd7704fd9b610#egg=karrio.usps_international&subdirectory=modules/connectors/usps_international +-e git+ssh://git@github.com/karrioapi/karrio.git@0ba337cc40b984fddf70a5717accd7704fd9b610#egg=karrio.zoom2u&subdirectory=modules/connectors/zoom2u lxml==4.9.4 lxml-stubs==0.5.1 MarkupPy==1.14 @@ -107,9 +109,9 @@ oauthlib==3.2.2 odfpy==1.4.1 openpyxl==3.1.2 packaging==23.2 -phonenumbers==8.13.29 +phonenumbers==8.13.31 pillow==10.2.0 -posthog==3.3.4 +posthog==3.4.2 psutil==5.9.8 psycopg2-binary==2.9.9 py-soap==2020.3.2 @@ -128,24 +130,23 @@ qrcode==7.4.2 redis==5.0.1 referencing==0.33.0 requests==2.31.0 -rpds-py==0.17.1 -sentry-sdk==1.40.0 +rpds-py==0.18.0 +sentry-sdk==1.40.5 six==1.16.0 sqlparse==0.4.4 -strawberry-graphql==0.219.1 -strawberry-graphql-django==0.30.0 +strawberry-graphql==0.219.2 +strawberry-graphql-django==0.32.1 tablib==3.5.0 tinycss2==1.2.1 treepoem==3.23.0 -typing_extensions==4.9.0 +typing_extensions==4.10.0 uritemplate==4.1.1 -urllib3==2.2.0 -uvicorn==0.27.0.post1 +urllib3==2.2.1 +uvicorn==0.27.1 validators==0.22.0 -weasyprint==60.2 +weasyprint==61.0 webencodings==0.5.1 whitenoise==6.6.0 -wrapt==1.16.0 xlrd==2.0.1 xlwt==1.3.0 xmltodict==0.13.0 diff --git a/schemas/graphql-admin.json b/schemas/graphql-admin.json index 3b497cc83f..fa751229c2 100644 --- a/schemas/graphql-admin.json +++ b/schemas/graphql-admin.json @@ -18234,13 +18234,9 @@ "name": "customer_number", "description": null, "type": { - "kind": "NON_NULL", - "name": null, - "ofType": { - "kind": "SCALAR", - "name": "String", - "ofType": null - } + "kind": "SCALAR", + "name": "String", + "ofType": null }, "defaultValue": null }, @@ -18248,13 +18244,9 @@ "name": "contract_id", "description": null, "type": { - "kind": "NON_NULL", - "name": null, - "ofType": { - "kind": "SCALAR", - "name": "String", - "ofType": null - } + "kind": "SCALAR", + "name": "String", + "ofType": null }, "defaultValue": null }, diff --git a/schemas/graphql.json b/schemas/graphql.json index 84d5b13e08..6fe66d4ca6 100644 --- a/schemas/graphql.json +++ b/schemas/graphql.json @@ -34658,13 +34658,9 @@ "name": "customer_number", "description": null, "type": { - "kind": "NON_NULL", - "name": null, - "ofType": { - "kind": "SCALAR", - "name": "String", - "ofType": null - } + "kind": "SCALAR", + "name": "String", + "ofType": null }, "defaultValue": null }, @@ -34672,13 +34668,9 @@ "name": "contract_id", "description": null, "type": { - "kind": "NON_NULL", - "name": null, - "ofType": { - "kind": "SCALAR", - "name": "String", - "ofType": null - } + "kind": "SCALAR", + "name": "String", + "ofType": null }, "defaultValue": null }, diff --git a/schemas/openapi.yml b/schemas/openapi.yml index 4be4adc1d4..d74a9c8f2f 100644 --- a/schemas/openapi.yml +++ b/schemas/openapi.yml @@ -16,7 +16,7 @@ info: ## Versioning When backwards-incompatible changes are made to the API, a new, dated version is released. - The current version is `2024.2.rc6`. + The current version is `2024.2.rc7`. Read our API changelog to learn more about backwards compatibility. @@ -86,7 +86,7 @@ info: All API requests must be made over [HTTPS](http://en.wikipedia.org/wiki/HTTP_Secure). API requests without authentication will also fail. title: Karrio API - version: 2024.2.rc6 + version: 2024.2.rc7 paths: /: get: @@ -11940,6 +11940,9 @@ tags: ## Carriers | Carrier Name | Display Name | | ------------ | ------------ | + | australiapost | Australia Post | + | fedex | FedEx | + | fedex_ws | FedEx Web Service | | zoom2u | Zoom2u | | usps_international | USPS International | | usps | USPS | @@ -11969,14 +11972,11 @@ tags: | canadapost | Canada Post | | bpost | Belgian Post | | boxknight | BoxKnight | - | australiapost | Australia Post | | asendia_us | Asendia US | | aramex | Aramex | | amazon_shipping | AmazonShipping | | allied_express_local | Allied Express Local | | allied_express | Allied Express | - | fedex | FedEx | - | fedex_ws | FedEx Web Service | --- ## Services @@ -11984,6 +11984,122 @@ tags: when purchasing shipping labels using single call label creation. You can also find all of the possible service levels for each of your carrier accounts by using [this endpoint](#operation/&&get_services). + ### Australia Post + | Code | Service Name | + | ------------ | ------------ | + | australiapost_parcel_post | T28 | + | australiapost_express_post | E34 | + | australiapost_parcel_post_signature | 3D55 | + | australiapost_express_post_signature | 3J55 | + | australiapost_intl_standard_pack_track | PTI8 | + | australiapost_intl_standard_with_signature | PTI7 | + | australiapost_intl_express_merch | ECM8 | + | australiapost_intl_express_docs | ECD8 | + | australiapost_eparcel_post_returns | PR | + | australiapost_express_eparcel_post_returns | XPR | + + ### FedEx + | Code | Service Name | + | ------------ | ------------ | + | fedex_international_priority_express | FEDEX_INTERNATIONAL_PRIORITY_EXPRESS | + | fedex_international_first | INTERNATIONAL_FIRST | + | fedex_international_priority | FEDEX_INTERNATIONAL_PRIORITY | + | fedex_international_economy | INTERNATIONAL_ECONOMY | + | fedex_ground | FEDEX_GROUND | + | fedex_cargo_mail | FEDEX_CARGO_MAIL | + | fedex_cargo_international_premium | FEDEX_CARGO_INTERNATIONAL_PREMIUM | + | fedex_first_overnight | FIRST_OVERNIGHT | + | fedex_first_overnight_freight | FIRST_OVERNIGHT_FREIGHT | + | fedex_1_day_freight | FEDEX_1_DAY_FREIGHT | + | fedex_2_day_freight | FEDEX_2_DAY_FREIGHT | + | fedex_3_day_freight | FEDEX_3_DAY_FREIGHT | + | fedex_international_priority_freight | INTERNATIONAL_PRIORITY_FREIGHT | + | fedex_international_economy_freight | INTERNATIONAL_ECONOMY_FREIGHT | + | fedex_cargo_airport_to_airport | FEDEX_CARGO_AIRPORT_TO_AIRPORT | + | fedex_international_priority_distribution | INTERNATIONAL_PRIORITY_DISTRIBUTION | + | fedex_ip_direct_distribution_freight | FEDEX_IP_DIRECT_DISTRIBUTION_FREIGHT | + | fedex_intl_ground_distribution | INTL_GROUND_DISTRIBUTION | + | fedex_ground_home_delivery | GROUND_HOME_DELIVERY | + | fedex_smart_post | SMART_POST | + | fedex_priority_overnight | PRIORITY_OVERNIGHT | + | fedex_standard_overnight | STANDARD_OVERNIGHT | + | fedex_2_day | FEDEX_2_DAY | + | fedex_2_day_am | FEDEX_2_DAY_AM | + | fedex_express_saver | FEDEX_EXPRESS_SAVER | + | fedex_same_day | SAME_DAY | + | fedex_same_day_city | SAME_DAY_CITY | + | fedex_one_day_freight | FEDEX_ONE_DAY_FREIGHT | + | fedex_international_economy_distribution | INTERNATIONAL_ECONOMY_DISTRIBUTION | + | fedex_international_connect_plus | FEDEX_INTERNATIONAL_CONNECT_PLUS | + | fedex_international_distribution_freight | INTERNATIONAL_DISTRIBUTION_FREIGHT | + | fedex_regional_economy | FEDEX_REGIONAL_ECONOMY | + | fedex_next_day_freight | FEDEX_NEXT_DAY_FREIGHT | + | fedex_next_day | FEDEX_NEXT_DAY | + | fedex_next_day_10am | FEDEX_NEXT_DAY_10AM | + | fedex_next_day_12pm | FEDEX_NEXT_DAY_12PM | + | fedex_next_day_end_of_day | FEDEX_NEXT_DAY_END_OF_DAY | + | fedex_distance_deferred | FEDEX_DISTANCE_DEFERRED | + + ### FedEx Web Service + | Code | Service Name | + | ------------ | ------------ | + | fedex_europe_first_international_priority | EUROPE_FIRST_INTERNATIONAL_PRIORITY | + | fedex_1_day_freight | FEDEX_1_DAY_FREIGHT | + | fedex_2_day | FEDEX_2_DAY | + | fedex_2_day_am | FEDEX_2_DAY_AM | + | fedex_2_day_freight | FEDEX_2_DAY_FREIGHT | + | fedex_3_day_freight | FEDEX_3_DAY_FREIGHT | + | fedex_cargo_airport_to_airport | FEDEX_CARGO_AIRPORT_TO_AIRPORT | + | fedex_cargo_freight_forwarding | FEDEX_CARGO_FREIGHT_FORWARDING | + | fedex_cargo_international_express_freight | FEDEX_CARGO_INTERNATIONAL_EXPRESS_FREIGHT | + | fedex_cargo_international_premium | FEDEX_CARGO_INTERNATIONAL_PREMIUM | + | fedex_cargo_mail | FEDEX_CARGO_MAIL | + | fedex_cargo_registered_mail | FEDEX_CARGO_REGISTERED_MAIL | + | fedex_cargo_surface_mail | FEDEX_CARGO_SURFACE_MAIL | + | fedex_custom_critical_air_expedite | FEDEX_CUSTOM_CRITICAL_AIR_EXPEDITE | + | fedex_custom_critical_air_expedite_exclusive_use | FEDEX_CUSTOM_CRITICAL_AIR_EXPEDITE_EXCLUSIVE_USE | + | fedex_custom_critical_air_expedite_network | FEDEX_CUSTOM_CRITICAL_AIR_EXPEDITE_NETWORK | + | fedex_custom_critical_charter_air | FEDEX_CUSTOM_CRITICAL_CHARTER_AIR | + | fedex_custom_critical_point_to_point | FEDEX_CUSTOM_CRITICAL_POINT_TO_POINT | + | fedex_custom_critical_surface_expedite | FEDEX_CUSTOM_CRITICAL_SURFACE_EXPEDITE | + | fedex_custom_critical_surface_expedite_exclusive_use | FEDEX_CUSTOM_CRITICAL_SURFACE_EXPEDITE_EXCLUSIVE_USE | + | fedex_custom_critical_temp_assure_air | FEDEX_CUSTOM_CRITICAL_TEMP_ASSURE_AIR | + | fedex_custom_critical_temp_assure_validated_air | FEDEX_CUSTOM_CRITICAL_TEMP_ASSURE_VALIDATED_AIR | + | fedex_custom_critical_white_glove_services | FEDEX_CUSTOM_CRITICAL_WHITE_GLOVE_SERVICES | + | fedex_distance_deferred | FEDEX_DISTANCE_DEFERRED | + | fedex_express_saver | FEDEX_EXPRESS_SAVER | + | fedex_first_freight | FEDEX_FIRST_FREIGHT | + | fedex_freight_economy | FEDEX_FREIGHT_ECONOMY | + | fedex_freight_priority | FEDEX_FREIGHT_PRIORITY | + | fedex_ground | FEDEX_GROUND | + | fedex_international_priority_plus | FEDEX_INTERNATIONAL_PRIORITY_PLUS | + | fedex_next_day_afternoon | FEDEX_NEXT_DAY_AFTERNOON | + | fedex_next_day_early_morning | FEDEX_NEXT_DAY_EARLY_MORNING | + | fedex_next_day_end_of_day | FEDEX_NEXT_DAY_END_OF_DAY | + | fedex_next_day_freight | FEDEX_NEXT_DAY_FREIGHT | + | fedex_next_day_mid_morning | FEDEX_NEXT_DAY_MID_MORNING | + | fedex_first_overnight | FIRST_OVERNIGHT | + | fedex_ground_home_delivery | GROUND_HOME_DELIVERY | + | fedex_international_distribution_freight | INTERNATIONAL_DISTRIBUTION_FREIGHT | + | fedex_international_economy | INTERNATIONAL_ECONOMY | + | fedex_international_economy_distribution | INTERNATIONAL_ECONOMY_DISTRIBUTION | + | fedex_international_economy_freight | INTERNATIONAL_ECONOMY_FREIGHT | + | fedex_international_first | INTERNATIONAL_FIRST | + | fedex_international_ground | INTERNATIONAL_GROUND | + | fedex_international_priority | INTERNATIONAL_PRIORITY | + | fedex_international_priority_distribution | INTERNATIONAL_PRIORITY_DISTRIBUTION | + | fedex_international_priority_express | INTERNATIONAL_PRIORITY_EXPRESS | + | fedex_international_priority_freight | INTERNATIONAL_PRIORITY_FREIGHT | + | fedex_priority_overnight | PRIORITY_OVERNIGHT | + | fedex_same_day | SAME_DAY | + | fedex_same_day_city | SAME_DAY_CITY | + | fedex_same_day_metro_afternoon | SAME_DAY_METRO_AFTERNOON | + | fedex_same_day_metro_morning | SAME_DAY_METRO_MORNING | + | fedex_same_day_metro_rush | SAME_DAY_METRO_RUSH | + | fedex_smart_post | SMART_POST | + | fedex_standard_overnight | STANDARD_OVERNIGHT | + | fedex_transborder_distribution_consolidation | TRANSBORDER_DISTRIBUTION_CONSOLIDATION | + ### Zoom2u | Code | Service Name | | ------------ | ------------ | @@ -13014,11 +13130,11 @@ tags: ### DHL Parcel DE | Code | Service Name | | ------------ | ------------ | - | deutschepost_paket | V01PAK | - | deutschepost_warenpost | V62WP | - | deutschepost_europaket | V54EPAK | - | deutschepost_paket_international | V53WPAK | - | deutschepost_warenpost_international | V66WPI | + | dhl_parcel_de_paket | V01PAK | + | dhl_parcel_de_warenpost | V62WP | + | dhl_parcel_de_europaket | V54EPAK | + | dhl_parcel_de_paket_international | V53WPAK | + | dhl_parcel_de_warenpost_international | V66WPI | ### DHL Express | Code | Service Name | @@ -13143,14 +13259,6 @@ tags: | boxknight_nextday | NEXTDAY | | boxknight_scheduled | SCHEDULED | - ### Australia Post - | Code | Service Name | - | ------------ | ------------ | - | australiapost_parcel_post | T28 | - | australiapost_express_post | E34 | - | australiapost_parcel_post_signature | T28S | - | australiapost_express_post_signature | E34S | - ### Asendia US | Code | Service Name | | ------------ | ------------ | @@ -13168,6 +13276,10 @@ tags: ### Allied Express Local | Code | Service Name | | ------------ | ------------ | + | allied_road_service | R | + | allied_parcel_service | P | + | allied_standard_pallet_service | PT | + | allied_oversized_pallet_service | PT2 | | allied_local_normal_service | N | | allied_local_vip_service | V | | allied_local_executive_service | E | @@ -13181,70 +13293,25 @@ tags: | allied_standard_pallet_service | PT | | allied_oversized_pallet_service | PT2 | - ### FedEx Web Service - | Code | Service Name | - | ------------ | ------------ | - | fedex_europe_first_international_priority | EUROPE_FIRST_INTERNATIONAL_PRIORITY | - | fedex_1_day_freight | FEDEX_1_DAY_FREIGHT | - | fedex_2_day | FEDEX_2_DAY | - | fedex_2_day_am | FEDEX_2_DAY_AM | - | fedex_2_day_freight | FEDEX_2_DAY_FREIGHT | - | fedex_3_day_freight | FEDEX_3_DAY_FREIGHT | - | fedex_cargo_airport_to_airport | FEDEX_CARGO_AIRPORT_TO_AIRPORT | - | fedex_cargo_freight_forwarding | FEDEX_CARGO_FREIGHT_FORWARDING | - | fedex_cargo_international_express_freight | FEDEX_CARGO_INTERNATIONAL_EXPRESS_FREIGHT | - | fedex_cargo_international_premium | FEDEX_CARGO_INTERNATIONAL_PREMIUM | - | fedex_cargo_mail | FEDEX_CARGO_MAIL | - | fedex_cargo_registered_mail | FEDEX_CARGO_REGISTERED_MAIL | - | fedex_cargo_surface_mail | FEDEX_CARGO_SURFACE_MAIL | - | fedex_custom_critical_air_expedite | FEDEX_CUSTOM_CRITICAL_AIR_EXPEDITE | - | fedex_custom_critical_air_expedite_exclusive_use | FEDEX_CUSTOM_CRITICAL_AIR_EXPEDITE_EXCLUSIVE_USE | - | fedex_custom_critical_air_expedite_network | FEDEX_CUSTOM_CRITICAL_AIR_EXPEDITE_NETWORK | - | fedex_custom_critical_charter_air | FEDEX_CUSTOM_CRITICAL_CHARTER_AIR | - | fedex_custom_critical_point_to_point | FEDEX_CUSTOM_CRITICAL_POINT_TO_POINT | - | fedex_custom_critical_surface_expedite | FEDEX_CUSTOM_CRITICAL_SURFACE_EXPEDITE | - | fedex_custom_critical_surface_expedite_exclusive_use | FEDEX_CUSTOM_CRITICAL_SURFACE_EXPEDITE_EXCLUSIVE_USE | - | fedex_custom_critical_temp_assure_air | FEDEX_CUSTOM_CRITICAL_TEMP_ASSURE_AIR | - | fedex_custom_critical_temp_assure_validated_air | FEDEX_CUSTOM_CRITICAL_TEMP_ASSURE_VALIDATED_AIR | - | fedex_custom_critical_white_glove_services | FEDEX_CUSTOM_CRITICAL_WHITE_GLOVE_SERVICES | - | fedex_distance_deferred | FEDEX_DISTANCE_DEFERRED | - | fedex_express_saver | FEDEX_EXPRESS_SAVER | - | fedex_first_freight | FEDEX_FIRST_FREIGHT | - | fedex_freight_economy | FEDEX_FREIGHT_ECONOMY | - | fedex_freight_priority | FEDEX_FREIGHT_PRIORITY | - | fedex_ground | FEDEX_GROUND | - | fedex_international_priority_plus | FEDEX_INTERNATIONAL_PRIORITY_PLUS | - | fedex_next_day_afternoon | FEDEX_NEXT_DAY_AFTERNOON | - | fedex_next_day_early_morning | FEDEX_NEXT_DAY_EARLY_MORNING | - | fedex_next_day_end_of_day | FEDEX_NEXT_DAY_END_OF_DAY | - | fedex_next_day_freight | FEDEX_NEXT_DAY_FREIGHT | - | fedex_next_day_mid_morning | FEDEX_NEXT_DAY_MID_MORNING | - | fedex_first_overnight | FIRST_OVERNIGHT | - | fedex_ground_home_delivery | GROUND_HOME_DELIVERY | - | fedex_international_distribution_freight | INTERNATIONAL_DISTRIBUTION_FREIGHT | - | fedex_international_economy | INTERNATIONAL_ECONOMY | - | fedex_international_economy_distribution | INTERNATIONAL_ECONOMY_DISTRIBUTION | - | fedex_international_economy_freight | INTERNATIONAL_ECONOMY_FREIGHT | - | fedex_international_first | INTERNATIONAL_FIRST | - | fedex_international_ground | INTERNATIONAL_GROUND | - | fedex_international_priority | INTERNATIONAL_PRIORITY | - | fedex_international_priority_distribution | INTERNATIONAL_PRIORITY_DISTRIBUTION | - | fedex_international_priority_express | INTERNATIONAL_PRIORITY_EXPRESS | - | fedex_international_priority_freight | INTERNATIONAL_PRIORITY_FREIGHT | - | fedex_priority_overnight | PRIORITY_OVERNIGHT | - | fedex_same_day | SAME_DAY | - | fedex_same_day_city | SAME_DAY_CITY | - | fedex_same_day_metro_afternoon | SAME_DAY_METRO_AFTERNOON | - | fedex_same_day_metro_morning | SAME_DAY_METRO_MORNING | - | fedex_same_day_metro_rush | SAME_DAY_METRO_RUSH | - | fedex_smart_post | SMART_POST | - | fedex_standard_overnight | STANDARD_OVERNIGHT | - | fedex_transborder_distribution_consolidation | TRANSBORDER_DISTRIBUTION_CONSOLIDATION | - --- ## Parcel Templates Use any of the following templates when you ship with special carrier packaging. + ### FedEx Web Service + | Code | Dimensions | + | ------------ | ------------ | + | fedex_envelope_legal_size | 9.5 x 15.5 x 1 in | + | fedex_padded_pak | 11.75 x 14.75 x 1 in | + | fedex_polyethylene_pak | 12.0 x 15.5 x 1 in | + | fedex_clinical_pak | 13.5 x 18.0 x 1 in | + | fedex_small_box | 12.25 x 10.9 x 1.5 in | + | fedex_medium_box | 13.25 x 11.5 x 2.38 in | + | fedex_large_box | 17.88 x 12.38 x 3.0 in | + | fedex_extra_large_box | 11.88 x 11.0 x 10.75 in | + | fedex_10_kg_box | 15.81 x 12.94 x 10.19 in | + | fedex_25_kg_box | 21.56 x 16.56 x 13.19 in | + | fedex_tube | 38.0 x 6.0 x 6.0 in | + ### UPS | Code | Dimensions | | ------------ | ------------ | @@ -13308,19 +13375,4 @@ tags: | canadapost_xexpresspost_certified_envelope | 26.0 x 15.9 x 1.5 cm | | canadapost_xexpresspost_national_large_envelope | 40.0 x 29.2 x 1.5 cm | - ### FedEx Web Service - | Code | Dimensions | - | ------------ | ------------ | - | fedex_envelope_legal_size | 9.5 x 15.5 x 1 in | - | fedex_padded_pak | 11.75 x 14.75 x 1 in | - | fedex_polyethylene_pak | 12.0 x 15.5 x 1 in | - | fedex_clinical_pak | 13.5 x 18.0 x 1 in | - | fedex_small_box | 12.25 x 10.9 x 1.5 in | - | fedex_medium_box | 13.25 x 11.5 x 2.38 in | - | fedex_large_box | 17.88 x 12.38 x 3.0 in | - | fedex_extra_large_box | 11.88 x 11.0 x 10.75 in | - | fedex_10_kg_box | 15.81 x 12.94 x 10.19 in | - | fedex_25_kg_box | 21.56 x 16.56 x 13.19 in | - | fedex_tube | 38.0 x 6.0 x 6.0 in | - ... diff --git a/source.requirements.txt b/source.requirements.txt index ba4c2c5474..69c17d1bb7 100644 --- a/source.requirements.txt +++ b/source.requirements.txt @@ -3,14 +3,13 @@ asgiref==3.7.2 attrs==23.2.0 backoff==2.2.1 Brotli==1.1.0 -certifi==2023.11.17 +certifi==2024.2.2 cffi==1.16.0 charset-normalizer==3.3.2 click==8.1.7 -cryptography==42.0.4 +cryptography==42.0.5 cssselect2==0.7.0 defusedxml==0.7.1 -Deprecated==1.2.14 deprecation==2.1.0 diff-match-patch==20230430 dj-database-url==2.1.0 @@ -21,20 +20,20 @@ django-downloadview==2.3.0 django-email-verification==0.3.3 django-filter==23.5 django-formtools==2.5.1 -django-health-check==3.17.0 -django-import-export==3.3.6 +django-health-check==3.18.1 +django-import-export==3.3.7 django-oauth-toolkit==2.3.0 django-otp==1.3.0 django-phonenumber-field==7.3.0 django-picklefield==3.1 django-redis==5.4.0 -django-two-factor-auth==1.15.5 +django-two-factor-auth==1.16.0 djangorestframework==3.14.0 djangorestframework-simplejwt==5.3.1 drf-api-tracking==1.8.4 drf-spectacular==0.27.1 et-xmlfile==1.1.0 -fonttools==4.47.2 +fonttools==4.49.0 graphql-core==3.2.3 gunicorn==21.2.0 h11==0.14.0 @@ -48,12 +47,13 @@ jsonfield==3.1.0 jsonschema==4.21.1 jsonschema-specifications==2023.12.1 jstruct==2021.11 -jwcrypto==1.5.1 +jwcrypto==1.5.4 karrio @ file://${PWD}/modules/sdk -karrio.allied-express @ file://${PWD}/modules/connectors/allied_express -karrio.amazon-shipping @ file://${PWD}/modules/connectors/amazon_shipping +karrio.allied_express @ file://${PWD}/modules/connectors/allied_express +karrio.allied_express_local @ file://${PWD}/modules/connectors/allied_express_local +karrio.amazon_shipping @ file://${PWD}/modules/connectors/amazon_shipping karrio.aramex @ file://${PWD}/modules/connectors/aramex -karrio.asendia-us @ file://${PWD}/modules/connectors/asendia_us +karrio.asendia_us @ file://${PWD}/modules/connectors/asendia_us karrio.australiapost @ file://${PWD}/modules/connectors/australiapost karrio.boxknight @ file://${PWD}/modules/connectors/boxknight karrio.bpost @ file://${PWD}/modules/connectors/bpost @@ -61,15 +61,17 @@ karrio.canadapost @ file://${PWD}/modules/connectors/canadapost karrio.canpar @ file://${PWD}/modules/connectors/canpar karrio.chronopost @ file://${PWD}/modules/connectors/chronopost karrio.colissimo @ file://${PWD}/modules/connectors/colissimo -karrio.dhl-express @ file://${PWD}/modules/connectors/dhl_express -karrio.dhl-poland @ file://${PWD}/modules/connectors/dhl_poland -karrio.dhl-universal @ file://${PWD}/modules/connectors/dhl_universal +karrio.dhl_parcel_de @ file://${PWD}/modules/connectors/dhl_parcel_de +karrio.dhl_express @ file://${PWD}/modules/connectors/dhl_express +karrio.dhl_poland @ file://${PWD}/modules/connectors/dhl_poland +karrio.dhl_universal @ file://${PWD}/modules/connectors/dhl_universal karrio.dicom @ file://${PWD}/modules/connectors/dicom karrio.dpd @ file://${PWD}/modules/connectors/dpd karrio.dpdhl @ file://${PWD}/modules/connectors/dpdhl karrio.easypost @ file://${PWD}/modules/connectors/easypost karrio.eshipper @ file://${PWD}/modules/connectors/eshipper karrio.fedex @ file://${PWD}/modules/connectors/fedex +karrio.fedex_ws @ file://${PWD}/modules/connectors/fedex_ws karrio.freightcom @ file://${PWD}/modules/connectors/freightcom karrio.generic @ file://${PWD}/modules/connectors/generic karrio.geodis @ file://${PWD}/modules/connectors/geodis @@ -100,16 +102,16 @@ karrio.zoom2u @ file://${PWD}/modules/connectors/zoom2u lxml==4.9.4 lxml-stubs==0.5.1 MarkupPy==1.14 -MarkupSafe==2.1.4 +MarkupSafe==2.1.5 monotonic==1.6 more-itertools==10.2.0 oauthlib==3.2.2 odfpy==1.4.1 openpyxl==3.1.2 packaging==23.2 -phonenumbers==8.13.28 +phonenumbers==8.13.31 pillow==10.2.0 -posthog==3.3.2 +posthog==3.4.2 psutil==5.9.8 psycopg2-binary==2.9.9 py-soap==2020.3.2 @@ -122,30 +124,29 @@ pypng==0.20220715.0 python-barcode==0.15.1 python-dateutil==2.8.2 python-decouple==3.8 -pytz==2023.3.post1 +pytz==2024.1 PyYAML==6.0.1 qrcode==7.4.2 redis==5.0.1 -referencing==0.32.1 +referencing==0.33.0 requests==2.31.0 -rpds-py==0.17.1 -sentry-sdk==1.39.2 +rpds-py==0.18.0 +sentry-sdk==1.40.5 six==1.16.0 sqlparse==0.4.4 -strawberry-graphql==0.218.0 -strawberry-graphql-django==0.28.3 +strawberry-graphql==0.219.2 +strawberry-graphql-django==0.32.1 tablib==3.5.0 tinycss2==1.2.1 treepoem==3.23.0 -typing_extensions==4.9.0 +typing_extensions==4.10.0 uritemplate==4.1.1 -urllib3==2.1.0 -uvicorn==0.27.0 +urllib3==2.2.1 +uvicorn==0.27.1 validators==0.22.0 -weasyprint==60.2 +weasyprint==61.0 webencodings==0.5.1 whitenoise==6.6.0 -wrapt==1.16.0 xlrd==2.0.1 xlwt==1.3.0 xmltodict==0.13.0