Skip to main content

The official Python library for the revox API

Project description

Revox Python API library

PyPI version

The Revox Python library provides convenient access to the Revox REST API from any Python 3.9+ application. The library includes type definitions for all request params and response fields, and offers both synchronous and asynchronous clients powered by httpx.

It is generated with Stainless.

Documentation

The full API of this library can be found in api.md.

Installation

# install from PyPI
pip install revox

Usage

The full API of this library can be found in api.md.

import os
from revox import Revox

client = Revox(
    api_key=os.environ.get("REVOX_API_KEY"),  # This is the default and can be omitted
)

campaign = client.campaigns.create(
    assistant_id="REPLACE_ME",
    contacts=[
        {
            "prompt_variables": {"foo": "string"},
            "to_phone_number": "to_phone_number",
        }
    ],
    name="REPLACE_ME",
)
print(campaign.campaign)

While you can provide an api_key keyword argument, we recommend using python-dotenv to add REVOX_API_KEY="My API Key" to your .env file so that your API Key is not stored in source control.

Async usage

Simply import AsyncRevox instead of Revox and use await with each API call:

import os
import asyncio
from revox import AsyncRevox

client = AsyncRevox(
    api_key=os.environ.get("REVOX_API_KEY"),  # This is the default and can be omitted
)


async def main() -> None:
    campaign = await client.campaigns.create(
        assistant_id="REPLACE_ME",
        contacts=[
            {
                "prompt_variables": {"foo": "string"},
                "to_phone_number": "to_phone_number",
            }
        ],
        name="REPLACE_ME",
    )
    print(campaign.campaign)


asyncio.run(main())

Functionality between the synchronous and asynchronous clients is otherwise identical.

With aiohttp

By default, the async client uses httpx for HTTP requests. However, for improved concurrency performance you may also use aiohttp as the HTTP backend.

You can enable this by installing aiohttp:

# install from PyPI
pip install revox[aiohttp]

Then you can enable it by instantiating the client with http_client=DefaultAioHttpClient():

import os
import asyncio
from revox import DefaultAioHttpClient
from revox import AsyncRevox


async def main() -> None:
    async with AsyncRevox(
        api_key=os.environ.get("REVOX_API_KEY"),  # This is the default and can be omitted
        http_client=DefaultAioHttpClient(),
    ) as client:
        campaign = await client.campaigns.create(
            assistant_id="REPLACE_ME",
            contacts=[
                {
                    "prompt_variables": {"foo": "string"},
                    "to_phone_number": "to_phone_number",
                }
            ],
            name="REPLACE_ME",
        )
        print(campaign.campaign)


asyncio.run(main())

Using types

Nested request parameters are TypedDicts. Responses are Pydantic models which also provide helper methods for things like:

  • Serializing back into JSON, model.to_json()
  • Converting to a dictionary, model.to_dict()

Typed requests and responses provide autocomplete and documentation within your editor. If you would like to see type errors in VS Code to help catch bugs earlier, set python.analysis.typeCheckingMode to basic.

Nested params

Nested parameters are dictionaries, typed using TypedDict, for example:

from revox import Revox

client = Revox()

campaign = client.campaigns.create(
    assistant_id="assistant_id",
    contacts=[
        {
            "prompt_variables": {"foo": "string"},
            "to_phone_number": "to_phone_number",
        }
    ],
    name="x",
    call_retry_config={
        "calling_windows": [
            {
                "calling_window_end_time": "calling_window_end_time",
                "calling_window_start_time": "calling_window_start_time",
                "retry_delay_seconds": 1,
            }
        ],
        "max_retry_attempts": 1,
    },
)
print(campaign.call_retry_config)

Handling errors

When the library is unable to connect to the API (for example, due to network connection problems or a timeout), a subclass of revox.APIConnectionError is raised.

When the API returns a non-success status code (that is, 4xx or 5xx response), a subclass of revox.APIStatusError is raised, containing status_code and response properties.

All errors inherit from revox.APIError.

import revox
from revox import Revox

client = Revox()

try:
    client.campaigns.create(
        assistant_id="REPLACE_ME",
        contacts=[
            {
                "prompt_variables": {"foo": "string"},
                "to_phone_number": "to_phone_number",
            }
        ],
        name="REPLACE_ME",
    )
except revox.APIConnectionError as e:
    print("The server could not be reached")
    print(e.__cause__)  # an underlying Exception, likely raised within httpx.
except revox.RateLimitError as e:
    print("A 429 status code was received; we should back off a bit.")
except revox.APIStatusError as e:
    print("Another non-200-range status code was received")
    print(e.status_code)
    print(e.response)

Error codes are as follows:

Status Code Error Type
400 BadRequestError
401 AuthenticationError
403 PermissionDeniedError
404 NotFoundError
422 UnprocessableEntityError
429 RateLimitError
>=500 InternalServerError
N/A APIConnectionError

Retries

Certain errors are automatically retried 2 times by default, with a short exponential backoff. Connection errors (for example, due to a network connectivity problem), 408 Request Timeout, 409 Conflict, 429 Rate Limit, and >=500 Internal errors are all retried by default.

You can use the max_retries option to configure or disable retry settings:

from revox import Revox

# Configure the default for all requests:
client = Revox(
    # default is 2
    max_retries=0,
)

# Or, configure per-request:
client.with_options(max_retries=5).campaigns.create(
    assistant_id="REPLACE_ME",
    contacts=[
        {
            "prompt_variables": {"foo": "string"},
            "to_phone_number": "to_phone_number",
        }
    ],
    name="REPLACE_ME",
)

Timeouts

By default requests time out after 1 minute. You can configure this with a timeout option, which accepts a float or an httpx.Timeout object:

from revox import Revox

# Configure the default for all requests:
client = Revox(
    # 20 seconds (default is 1 minute)
    timeout=20.0,
)

# More granular control:
client = Revox(
    timeout=httpx.Timeout(60.0, read=5.0, write=10.0, connect=2.0),
)

# Override per-request:
client.with_options(timeout=5.0).campaigns.create(
    assistant_id="REPLACE_ME",
    contacts=[
        {
            "prompt_variables": {"foo": "string"},
            "to_phone_number": "to_phone_number",
        }
    ],
    name="REPLACE_ME",
)

On timeout, an APITimeoutError is thrown.

Note that requests that time out are retried twice by default.

Advanced

Logging

We use the standard library logging module.

You can enable logging by setting the environment variable REVOX_LOG to info.

$ export REVOX_LOG=info

Or to debug for more verbose logging.

How to tell whether None means null or missing

In an API response, a field may be explicitly null, or missing entirely; in either case, its value is None in this library. You can differentiate the two cases with .model_fields_set:

if response.my_field is None:
  if 'my_field' not in response.model_fields_set:
    print('Got json like {}, without a "my_field" key present at all.')
  else:
    print('Got json like {"my_field": null}.')

Accessing raw response data (e.g. headers)

The "raw" Response object can be accessed by prefixing .with_raw_response. to any HTTP method call, e.g.,

from revox import Revox

client = Revox()
response = client.campaigns.with_raw_response.create(
    assistant_id="REPLACE_ME",
    contacts=[{
        "prompt_variables": {
            "foo": "string"
        },
        "to_phone_number": "to_phone_number",
    }],
    name="REPLACE_ME",
)
print(response.headers.get('X-My-Header'))

campaign = response.parse()  # get the object that `campaigns.create()` would have returned
print(campaign.campaign)

These methods return an APIResponse object.

The async client returns an AsyncAPIResponse with the same structure, the only difference being awaitable methods for reading the response content.

.with_streaming_response

The above interface eagerly reads the full response body when you make the request, which may not always be what you want.

To stream the response body, use .with_streaming_response instead, which requires a context manager and only reads the response body once you call .read(), .text(), .json(), .iter_bytes(), .iter_text(), .iter_lines() or .parse(). In the async client, these are async methods.

with client.campaigns.with_streaming_response.create(
    assistant_id="REPLACE_ME",
    contacts=[
        {
            "prompt_variables": {"foo": "string"},
            "to_phone_number": "to_phone_number",
        }
    ],
    name="REPLACE_ME",
) as response:
    print(response.headers.get("X-My-Header"))

    for line in response.iter_lines():
        print(line)

The context manager is required so that the response will reliably be closed.

Making custom/undocumented requests

This library is typed for convenient access to the documented API.

If you need to access undocumented endpoints, params, or response properties, the library can still be used.

Undocumented endpoints

To make requests to undocumented endpoints, you can make requests using client.get, client.post, and other http verbs. Options on the client will be respected (such as retries) when making this request.

import httpx

response = client.post(
    "/foo",
    cast_to=httpx.Response,
    body={"my_param": True},
)

print(response.headers.get("x-foo"))

Undocumented request params

If you want to explicitly send an extra param, you can do so with the extra_query, extra_body, and extra_headers request options.

Undocumented response properties

To access undocumented response properties, you can access the extra fields like response.unknown_prop. You can also get all the extra fields on the Pydantic model as a dict with response.model_extra.

Configuring the HTTP client

You can directly override the httpx client to customize it for your use case, including:

import httpx
from revox import Revox, DefaultHttpxClient

client = Revox(
    # Or use the `REVOX_BASE_URL` env var
    base_url="http://my.test.server.example.com:8083",
    http_client=DefaultHttpxClient(
        proxy="http://my.test.proxy.example.com",
        transport=httpx.HTTPTransport(local_address="0.0.0.0"),
    ),
)

You can also customize the client on a per-request basis by using with_options():

client.with_options(http_client=DefaultHttpxClient(...))

Managing HTTP resources

By default the library closes underlying HTTP connections whenever the client is garbage collected. You can manually close the client using the .close() method if desired, or with a context manager that closes when exiting.

from revox import Revox

with Revox() as client:
  # make requests here
  ...

# HTTP client is now closed

Versioning

This package generally follows SemVer conventions, though certain backwards-incompatible changes may be released as minor versions:

  1. Changes that only affect static types, without breaking runtime behavior.
  2. Changes to library internals which are technically public but not intended or documented for external use. (Please open a GitHub issue to let us know if you are relying on such internals.)
  3. Changes that we do not expect to impact the vast majority of users in practice.

We take backwards-compatibility seriously and work hard to ensure you can rely on a smooth upgrade experience.

We are keen for your feedback; please open an issue with questions, bugs, or suggestions.

Determining the installed version

If you've upgraded to the latest version but aren't seeing any new features you were expecting then your python environment is likely still using an older version.

You can determine the version that is being used at runtime with:

import revox
print(revox.__version__)

Requirements

Python 3.9 or higher.

Contributing

See the contributing documentation.

Project details


Download files

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

Source Distribution

revox-0.1.1.tar.gz (241.6 kB view details)

Uploaded Source

Built Distribution

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

revox-0.1.1-py3-none-any.whl (130.1 kB view details)

Uploaded Python 3

File details

Details for the file revox-0.1.1.tar.gz.

File metadata

  • Download URL: revox-0.1.1.tar.gz
  • Upload date:
  • Size: 241.6 kB
  • Tags: Source
  • Uploaded using Trusted Publishing? Yes
  • Uploaded via: uv/0.9.13 {"installer":{"name":"uv","version":"0.9.13"},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}

File hashes

Hashes for revox-0.1.1.tar.gz
Algorithm Hash digest
SHA256 e7b524027addb27c4a18e9acfb95be569a9d7ef96b9e1f24418aa26a35d478ef
MD5 de312bd5834f92b7333773a95ac11681
BLAKE2b-256 91c8ccec3a409f9c8b3f760f842bec8ae155b0c78ae8307f9ccdcf7f39fca2d4

See more details on using hashes here.

File details

Details for the file revox-0.1.1-py3-none-any.whl.

File metadata

  • Download URL: revox-0.1.1-py3-none-any.whl
  • Upload date:
  • Size: 130.1 kB
  • Tags: Python 3
  • Uploaded using Trusted Publishing? Yes
  • Uploaded via: uv/0.9.13 {"installer":{"name":"uv","version":"0.9.13"},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}

File hashes

Hashes for revox-0.1.1-py3-none-any.whl
Algorithm Hash digest
SHA256 e3ebf711cf81f83b43a44004ac87d40a3256fa822c730f142868a6c767a3ebed
MD5 74208b59aaf1b019fb545d68b71bf870
BLAKE2b-256 db1dec02cadbcbec078f229390076ddd0fa14cee54491d7bf6cebc0831326900

See more details on using hashes here.

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