Skip to main content

A client library for accessing backend

Project description

reportr-backend-client

A client library for accessing backend

Usage

First, create a client:

from reportr_backend_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 reportr_backend_client import AuthenticatedClient

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

Now call your endpoint and use your models:

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

with client as client:
    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 reportr_backend_client.models import MyDataModel
from reportr_backend_client.api.my_tag import get_my_data_model
from reportr_backend_client.types import Response

async with client as client:
    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
)

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 reportr_backend_client.api.default

Advanced customizations

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. You can also customize the underlying httpx.Client or httpx.AsyncClient (depending on your use-case):

from reportr_backend_client import Client

def log_request(request):
    print(f"Request event hook: {request.method} {request.url} - Waiting for response")

def log_response(response):
    request = response.request
    print(f"Response event hook: {request.method} {request.url} - Status {response.status_code}")

client = Client(
    base_url="https://api.example.com",
    httpx_args={"event_hooks": {"request": [log_request], "response": [log_response]}},
)

# Or get the underlying httpx client to modify directly with client.get_httpx_client() or client.get_async_httpx_client()

You can even set the httpx client directly, but beware that this will override any existing settings (e.g., base_url):

import httpx
from reportr_backend_client import Client

client = Client(
    base_url="https://api.example.com",
)
# Note that base_url needs to be re-set, as would any shared cookies, headers, etc.
client.set_httpx_client(httpx.Client(base_url="https://api.example.com", proxies="http://localhost:8030"))

Building / publishing this package

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>

Project details


Release history Release notifications | RSS feed

Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

reportr_backend_client-0.0.1739736173.dev0.tar.gz (10.7 kB view details)

Uploaded Source

Built Distribution

If you're not sure about the file name format, learn more about wheel file names.

File details

Details for the file reportr_backend_client-0.0.1739736173.dev0.tar.gz.

File metadata

File hashes

Hashes for reportr_backend_client-0.0.1739736173.dev0.tar.gz
Algorithm Hash digest
SHA256 8c930164bfa0bd2b33819355187bd48a834bf0e345d109fc5b23e601dbaf8d2e
MD5 071fd07dca5f038ec05df25376b1bfa0
BLAKE2b-256 e2291cfabaec02781a5fd9f69d4415c4e1de3e870da1ef0e221f80ff9bb168df

See more details on using hashes here.

Provenance

The following attestation bundles were made for reportr_backend_client-0.0.1739736173.dev0.tar.gz:

Publisher: publish-client.yml on reportr-news/backend

Attestations: Values shown here reflect the state when the release was signed and may no longer be current.

File details

Details for the file reportr_backend_client-0.0.1739736173.dev0-py3-none-any.whl.

File metadata

File hashes

Hashes for reportr_backend_client-0.0.1739736173.dev0-py3-none-any.whl
Algorithm Hash digest
SHA256 ac7606619234fff926f96b4b3c61b19f8977b72dd67b253869bdbeb54dcb6b75
MD5 4c17a0743e4ed8c527012150ac2f6727
BLAKE2b-256 4538cda05ddc76bcaf57d4e90a308d926f3e4768dc1132dd0c15b3cef756ee93

See more details on using hashes here.

Provenance

The following attestation bundles were made for reportr_backend_client-0.0.1739736173.dev0-py3-none-any.whl:

Publisher: publish-client.yml on reportr-news/backend

Attestations: Values shown here reflect the state when the release was signed and may no longer be current.

Supported by

AWS Cloud computing and Security Sponsor Datadog Monitoring Depot Continuous Integration Fastly CDN Google Download Analytics Pingdom Monitoring Sentry Error logging StatusPage Status page