octostar-python-client 0.1.764

A client library for accessing Octostar API

octostar-python-client

A client library for accessing Octostar API

Usage

First, create a client:

from octostar import Client

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

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

from octostar import AuthenticatedClient

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

Now call your endpoint and use your models:

from octostar.models import MyDataModel
from octostar.api.my_tag import get_my_data_model
from octostar.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 octostar.models import MyDataModel
from octostar.api.my_tag import get_my_data_model
from octostar.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 octostar.api.default

Installing

pip install octostar-python-client

Testing a PR build (TestPyPI)

Every pull request that touches the SDK publishes a pre-release to TestPyPI versioned 0.0.<pr>.dev<run_number> (e.g. 0.0.898.dev1319) — the <pr> segment is the PR number, so you can find the build for your PR. Use it to test SDK changes before they merge.

TestPyPI does not host third-party dependencies (httpx, tenacity, …), so point the resolver at PyPI as an extra index for them:

# pip
pip install \
  --index-url https://test.pypi.org/simple/ \
  --extra-index-url https://pypi.org/simple/ \
  octostar-python-client==0.0.<pr>.dev<N>

# uv (--index-strategy so uv considers both indexes per-package)
uv pip install \
  --index-url https://test.pypi.org/simple/ \
  --extra-index-url https://pypi.org/simple/ \
  --index-strategy unsafe-best-match \
  octostar-python-client==0.0.<pr>.dev<N>

Releasing

Releases are automated. On every merge to main, the octostar-api release pipeline builds this package and publishes it to PyPI, stamped with the octostar-api version. There is no manual publish step.

To build the package locally for development:

./scripts/sdk/build.sh          # writes octostar_python_client/dist/*.whl and *.tar.gz
pip install octostar_python_client/dist/*.whl