dockflow-sdk
Client for the Dockflow API v3: upstream events, tradeflows, documents and the widget.
This Python package is automatically generated by the OpenAPI Generator project:
- API version: 3.0.0
- Package version: 1.0.0
- Generator version: 7.27.0
- Build package: org.openapitools.codegen.languages.PythonClientCodegen
Requirements.
Python 3.11+
Packaging uses standard [project] metadata and [dependency-groups] (PEP 621/735).
Install the package with python -m pip install .; install development dependencies
with Poetry 2.2 or newer using poetry install, or pip 25.1 or newer using
python -m pip install --group dev. The latter installs the group, not the package.
Installation & Usage
pip install
If the python package is hosted on a repository, you can install directly using:
pip install git+https://github.com/Dockflow/dockflow-sdks.git
(you may need to run pip with root permission: sudo pip install git+https://github.com/Dockflow/dockflow-sdks.git)
Then import the package:
import dockflow_sdk
Setuptools
Install via Setuptools.
python setup.py install --user
(or sudo python setup.py install to install the package for all users)
Then import the package:
import dockflow_sdk
Tests
Execute pytest to run the tests.
Getting Started
Please follow the installation procedure and then run the following:
import dockflow_sdk
from dockflow_sdk.rest import ApiException
from pprint import pprint
# Defining the host is optional and defaults to https://api.dockflow.com
# See configuration.py for a list of all supported configuration parameters.
configuration = dockflow_sdk.Configuration(
host = "https://api.dockflow.com"
)
# The client must configure the authentication and authorization parameters
# in accordance with the API server security policy.
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
# Configure Bearer authorization: ApiKey
configuration = dockflow_sdk.Configuration(
access_token = os.environ["BEARER_TOKEN"]
)
# Enter a context with an instance of the API client
with dockflow_sdk.ApiClient(configuration) as api_client:
# Create an instance of the API class
api_instance = dockflow_sdk.DocumentsApi(api_client)
reference = 'reference_example' # str |
try:
# Delete a document
api_instance.delete_document(reference)
except ApiException as e:
print("Exception when calling DocumentsApi->delete_document: %s\n" % e)
Documentation for API Endpoints
All URIs are relative to https://api.dockflow.com
| Class | Method | HTTP request | Description |
|---|---|---|---|
| DocumentsApi | delete_document | DELETE /v3/downstream/documents/{reference} | Delete a document |
| DocumentsApi | get_document | GET /v3/downstream/documents/{reference} | List the documents of a tradeflow |
| DocumentsApi | list_document_types | GET /v3/downstream/documents/types | List document types |
| DocumentsApi | update_document | PATCH /v3/downstream/documents/{reference} | Update a document |
| DocumentsApi | upload_document | POST /v3/downstream/documents | Upload a document to a tradeflow |
| TradeflowsApi | create_tradeflows | POST /v3/downstream/tradeflows | Upsert tradeflows |
| TradeflowsApi | delete_tradeflow | DELETE /v3/downstream/tradeflows/{tradeflow_reference} | Delete a tradeflow |
| UpstreamApi | get_upstream | GET /v3/upstream | Poll upstream events |
| WidgetApi | search_widget | GET /v3/widget/search | Search a shipment for the embeddable tracking widget |
Documentation For Models
- ContainerReference
- CreateTradeflows202Response
- CreateTradeflows202ResponseTradeflowsInner
- DocumentUpdate
- DocumentUpload
- DownstreamTradeflow
- DownstreamTradeflowBillOfLadingReference
- DownstreamTradeflowBookingReference
- DownstreamTradeflowEventsInner
- DownstreamTradeflowFreeTimeOverridesInner
- DownstreamTradeflowMockTracking
- DownstreamTradeflowPartnersInner
- DownstreamTradeflowReferences
- GetDocument200Response
- GetDocument200ResponseDataInner
- GetDocument200ResponseDataInnerDocumentType
- GetUpstream200Response
- GetUpstream400Response
- InlineObject
- ListDocumentTypes200ResponseInner
- UploadDocument202Response
- UploadDocument400Response
- UpstreamRecord
- UpstreamRecordAdditionalReferences
- UpstreamRecordDataQuality
- UpstreamRecordMetadata
- WidgetContainer
- WidgetCountry
- WidgetLeg
- WidgetLocation
- WidgetMilestone
- WidgetPoint
- WidgetSearchResult
- WidgetTrack
- WidgetTrackReading
Documentation For Authorization
Authentication schemes defined for the API:
ApiKey
- Type: Bearer authentication
Author
Request headers
Header names are compared case-insensitively in all Python client libraries.
Request headers are copied; supplying _headers does not change the caller's dict
or the client's shared defaults. The public _headers argument retains its dict
validation and existing value serialization. Pydantic can coerce mappings such as HTTPX Headers to a dict,
combining repeated fields into a single value; _headers does not provide a
repeated-field or list-of-pairs API.
Precedence, from lowest to highest:
_headers(within one dict, the last inserted case variant wins).- Explicit OpenAPI header parameters and generated
Content-Type(or_content_type). GeneratedAcceptis added only when neither_headersnor explicit header parameters contain anAcceptcase variant. ApiClient.default_headers(including headers set withset_default_header).- The client's
cookiesetting, forCookie. - Authentication headers. A non-empty
_request_authreplaces configured authentication for that call;{}retains configured authentication. Cookie authentication appends to the selectedCookievalue.
This retains the existing precedence for identically spelled names and extends it
to case variants. To override a generated content type, use _content_type;
client defaults still take precedence over it. The winning header's spelling and
value are retained for replacements. Cookie authentication uses the canonical
Cookie spelling and appends its value. Values containing legitimate
comma-separated lists are not split or deduplicated. This does not remove
duplicate values inside a header or change the handling of repeated fields
supplied directly to the transport.
Metadata
Release files for dockflow-sdk 1.0.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| dockflow_sdk-1.0.0.tar.gz | 51.0 kB | Without provenance | Details for dockflow_sdk-1.0.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| dockflow_sdk-1.0.0-py3-none-any.whl | Python 3 | none | any | Details for dockflow_sdk-1.0.0-py3-none-any.whl |
Total release size: 139.3 kB
Release files / dockflow_sdk-1.0.0.tar.gz
| Download URL | dockflow_sdk-1.0.0.tar.gz |
|---|---|
| Size | 51.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
76b7d0659b100a30310104f0ac11c0d69a35334b3a6eb586d08230e316ecabda
|
|
BLAKE2b-256 checksum How to use checksums |
8134098b8e2d8c6d453efc7a0bb0cbcc7534dc66a26da3474f8baf1ace09654d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Release files / dockflow_sdk-1.0.0-py3-none-any.whl
| Download URL | dockflow_sdk-1.0.0-py3-none-any.whl |
|---|---|
| Size | 88.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c774c13571af7c6636e30c192d56fcfcf78db40d6cefcf4e9275971994b2f094
|
|
BLAKE2b-256 checksum How to use checksums |
3304e8cc3fe8c72632a40a3270ae9248b03013c9873660b960aee9e9d5d637ea
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Security for dockflow-sdk 1.0.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.