Skip to main content

longship-api-client

MIT license PyPI version shields.io Downloads

A client library for accessing Longship API

Usage

First, create a client:

from longship_api_client import Client

client = Client(base_url="https://api.example.com")

If the endpoints you're going to hit require authentication, use AuthenticatedClient instead:

from longship_api_client import AuthenticatedClient

client = AuthenticatedClient(base_url="https://api.example.com", token="SuperSecretToken")

Now call your endpoint and use your models:

from longship_api_client.models import MyDataModel
from longship_api_client.api.my_tag import get_my_data_model
from longship_api_client.types import Response

my_data: MyDataModel = get_my_data_model.sync(client=client)
# or if you need more info (e.g. status_code)
response: Response[MyDataModel] = get_my_data_model.sync_detailed(client=client)

Or do the same thing with an async version:

from longship_api_client.models import MyDataModel
from longship_api_client.api.my_tag import get_my_data_model
from longship_api_client.types import Response

my_data: MyDataModel = await get_my_data_model.asyncio(client=client)
response: Response[MyDataModel] = await get_my_data_model.asyncio_detailed(client=client)

By default, when you're calling an HTTPS API it will attempt to verify that SSL is working correctly. Using certificate verification is highly recommended most of the time, but sometimes you may need to authenticate to a server (especially an internal server) using a custom certificate bundle.

client = AuthenticatedClient(
    base_url="https://internal_api.example.com", 
    token="SuperSecretToken",
    verify_ssl="/path/to/certificate_bundle.pem",
)

You can also disable certificate validation altogether, but beware that this is a security risk.

client = AuthenticatedClient(
    base_url="https://internal_api.example.com", 
    token="SuperSecretToken", 
    verify_ssl=False
)

There are more settings on the generated Client class which let you control more runtime behavior, check out the docstring on that class for more info.

Things to know:

  1. Every path/method combo becomes a Python module with four functions:

    1. sync: Blocking request that returns parsed data (if successful) or None
    2. sync_detailed: Blocking request that always returns a Request, optionally with parsed set if the request was successful.
    3. asyncio: Like sync but async instead of blocking
    4. asyncio_detailed: Like sync_detailed but async instead of blocking
  2. All path/query params, and bodies become method arguments.

  3. If your endpoint had any tags on it, the first tag will be used as a module name for the function (my_tag above)

  4. Any endpoint which did not have a tag will be in longship_api_client.api.default

Building / publishing this Client

This project uses Poetry to manage dependencies and packaging. Here are the basics:

  1. Update the metadata in pyproject.toml (e.g. authors, version)
  2. If you're using a private repository, configure it with Poetry
    1. poetry config repositories.<your-repository-name> <url-to-your-repository>
    2. poetry config http-basic.<your-repository-name> <username> <password>
  3. Publish the client with poetry publish --build -r <your-repository-name> or, if for public PyPI, just poetry publish --build

If you want to install this client into another project without publishing it (e.g. for development) then:

  1. If that project is using Poetry, you can simply do poetry add <path-to-this-client> from that project
  2. If that project is not using Poetry:
    1. Build a wheel with poetry build -f wheel
    2. Install that wheel from the other project pip install <path-to-wheel>

Updating the client

This client was generated with openapi-python-client and to update it to the latest version of the Longship API, you need to download the Swagger configuration to a JSON file and run following in a directory one level above this repo:

openapi-python-client generate --path longship-api-client/fixtures/longship_24-06-23.json

Longship sends null for many optional fields, which the generated from_dict methods only treat as unset after this edit. Run it inside the repo after every regeneration:

grep -rlE 'if isinstance\(_[a-z0-9_]+, Unset\):$' longship_api_client | xargs sed -i '' -E 's/if isinstance\(_([a-z0-9_]+), Unset\):$/if isinstance(_\1, Unset) or _\1 is None:/'

Metadata

Release files for longship 2026.11.2

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for longship 2026.11.2
File Size Uploaded Provenance Actions
longship-2026.11.2.tar.gz 128.9 kB Without provenance Details for longship-2026.11.2.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for longship 2026.11.2
File Interpreter ABI Platform Actions
longship-2026.11.2-py3-none-any.whl Python 3 none any Details for longship-2026.11.2-py3-none-any.whl

Total release size: 545.1 kB

Release files / longship-2026.11.2.tar.gz

Download URL longship-2026.11.2.tar.gz
Size 128.9 kB
Tags Source
SHA-256 checksum
How to use checksums
e552af21682884483945e79c641c6d70e9b038486e2174ed2465bd83847fb7c0
BLAKE2b-256 checksum
How to use checksums
8de36852466ed23afa3a21a45a6b72cd18dae07a749374590bf6768db63c3eef
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via poetry/2.2.1 CPython/3.14.7 Darwin/27.0.0

Release files / longship-2026.11.2-py3-none-any.whl

Download URL longship-2026.11.2-py3-none-any.whl
Size 416.2 kB
Tags Python 3
SHA-256 checksum
How to use checksums
09e51bd5daac95f69545f52824c1fd4f105e27420238eabadafff1c2f0e6ee61
BLAKE2b-256 checksum
How to use checksums
510962a78b07cd271154646d3acf46984578030f45abd98d512a5bc34272a0c7
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via poetry/2.2.1 CPython/3.14.7 Darwin/27.0.0

Security for longship 2026.11.2

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.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page