Name | payi JSON |
Version |
0.1.0a106
JSON |
| download |
home_page | None |
Summary | The official Python library for the payi API |
upload_time | 2025-07-30 00:23:22 |
maintainer | None |
docs_url | None |
author | None |
requires_python | >=3.8 |
license | Apache-2.0 |
keywords |
|
VCS |
 |
bugtrack_url |
|
requirements |
No requirements were recorded.
|
Travis-CI |
No Travis.
|
coveralls test coverage |
No coveralls.
|
# Payi Python API library
<!-- prettier-ignore -->
[)](https://pypi.org/project/payi/)
The Payi Python library provides convenient access to the Payi REST API from any Python 3.8+
application. The library includes type definitions for all request params and response fields,
and offers both synchronous and asynchronous clients powered by [httpx](https://github.com/encode/httpx).
It is generated with [Stainless](https://www.stainless.com/).
## Documentation
The REST API documentation can be found on [docs.payi.com](https://docs.payi.com). The full API of this library can be found in [api.md](https://github.com/Pay-i/pay-i-python/tree/main/api.md).
## Installation
```sh
# install from PyPI
pip install --pre payi
```
## Usage
The full API of this library can be found in [api.md](https://github.com/Pay-i/pay-i-python/tree/main/api.md).
```python
import os
from payi import Payi
client = Payi(
api_key=os.environ.get("PAYI_API_KEY"), # This is the default and can be omitted
)
use_case_definition = client.use_cases.definitions.create(
description="Sample Use Case Definition Description",
name="SampleUseCaseDefinition",
)
print(use_case_definition.request_id)
```
While you can provide an `api_key` keyword argument,
we recommend using [python-dotenv](https://pypi.org/project/python-dotenv/)
to add `PAYI_API_KEY="My API Key"` to your `.env` file
so that your API Key is not stored in source control.
## Async usage
Simply import `AsyncPayi` instead of `Payi` and use `await` with each API call:
```python
import os
import asyncio
from payi import AsyncPayi
client = AsyncPayi(
api_key=os.environ.get("PAYI_API_KEY"), # This is the default and can be omitted
)
async def main() -> None:
use_case_definition = await client.use_cases.definitions.create(
description="Sample Use Case Definition Description",
name="SampleUseCaseDefinition",
)
print(use_case_definition.request_id)
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`:
```sh
# install from PyPI
pip install --pre payi[aiohttp]
```
Then you can enable it by instantiating the client with `http_client=DefaultAioHttpClient()`:
```python
import asyncio
from payi import DefaultAioHttpClient
from payi import AsyncPayi
async def main() -> None:
async with AsyncPayi(
api_key="My API Key",
http_client=DefaultAioHttpClient(),
) as client:
use_case_definition = await client.use_cases.definitions.create(
description="Sample Use Case Definition Description",
name="SampleUseCaseDefinition",
)
print(use_case_definition.request_id)
asyncio.run(main())
```
## Using types
Nested request parameters are [TypedDicts](https://docs.python.org/3/library/typing.html#typing.TypedDict). Responses are [Pydantic models](https://docs.pydantic.dev) 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`.
## Pagination
List methods in the Payi API are paginated.
This library provides auto-paginating iterators with each list response, so you do not have to request successive pages manually:
```python
from payi import Payi
client = Payi()
all_definitions = []
# Automatically fetches more pages as needed.
for definition in client.use_cases.definitions.list():
# Do something with definition here
all_definitions.append(definition)
print(all_definitions)
```
Or, asynchronously:
```python
import asyncio
from payi import AsyncPayi
client = AsyncPayi()
async def main() -> None:
all_definitions = []
# Iterate through items across all pages, issuing requests as needed.
async for definition in client.use_cases.definitions.list():
all_definitions.append(definition)
print(all_definitions)
asyncio.run(main())
```
Alternatively, you can use the `.has_next_page()`, `.next_page_info()`, or `.get_next_page()` methods for more granular control working with pages:
```python
first_page = await client.use_cases.definitions.list()
if first_page.has_next_page():
print(f"will fetch next page using these details: {first_page.next_page_info()}")
next_page = await first_page.get_next_page()
print(f"number of items we just fetched: {len(next_page.items)}")
# Remove `await` for non-async usage.
```
Or just work directly with the returned data:
```python
first_page = await client.use_cases.definitions.list()
print(f"next page cursor: {first_page.cursor}") # => "next page cursor: ..."
for definition in first_page.items:
print(definition.request_id)
# Remove `await` for non-async usage.
```
## Nested params
Nested parameters are dictionaries, typed using `TypedDict`, for example:
```python
from payi import Payi
client = Payi()
use_case_definition = client.use_cases.definitions.create(
description="x",
name="x",
limit_config={"max": 0},
)
print(use_case_definition.limit_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 `payi.APIConnectionError` is raised.
When the API returns a non-success status code (that is, 4xx or 5xx
response), a subclass of `payi.APIStatusError` is raised, containing `status_code` and `response` properties.
All errors inherit from `payi.APIError`.
```python
import payi
from payi import Payi
client = Payi()
try:
client.use_cases.definitions.create(
description="Sample Use Case Definition Description",
name="SampleUseCaseDefinition",
)
except payi.APIConnectionError as e:
print("The server could not be reached")
print(e.__cause__) # an underlying Exception, likely raised within httpx.
except payi.RateLimitError as e:
print("A 429 status code was received; we should back off a bit.")
except payi.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:
```python
from payi import Payi
# Configure the default for all requests:
client = Payi(
# default is 2
max_retries=0,
)
# Or, configure per-request:
client.with_options(max_retries=5).use_cases.definitions.create(
description="Sample Use Case Definition Description",
name="SampleUseCaseDefinition",
)
```
### 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`](https://www.python-httpx.org/advanced/timeouts/#fine-tuning-the-configuration) object:
```python
from payi import Payi
# Configure the default for all requests:
client = Payi(
# 20 seconds (default is 1 minute)
timeout=20.0,
)
# More granular control:
client = Payi(
timeout=httpx.Timeout(60.0, read=5.0, write=10.0, connect=2.0),
)
# Override per-request:
client.with_options(timeout=5.0).use_cases.definitions.create(
description="Sample Use Case Definition Description",
name="SampleUseCaseDefinition",
)
```
On timeout, an `APITimeoutError` is thrown.
Note that requests that time out are [retried twice by default](https://github.com/Pay-i/pay-i-python/tree/main/#retries).
## Advanced
### Logging
We use the standard library [`logging`](https://docs.python.org/3/library/logging.html) module.
You can enable logging by setting the environment variable `PAYI_LOG` to `info`.
```shell
$ export PAYI_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`:
```py
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.,
```py
from payi import Payi
client = Payi()
response = client.use_cases.definitions.with_raw_response.create(
description="Sample Use Case Definition Description",
name="SampleUseCaseDefinition",
)
print(response.headers.get('X-My-Header'))
definition = response.parse() # get the object that `use_cases.definitions.create()` would have returned
print(definition.request_id)
```
These methods return an [`APIResponse`](https://github.com/Pay-i/pay-i-python/tree/main/src/payi/_response.py) object.
The async client returns an [`AsyncAPIResponse`](https://github.com/Pay-i/pay-i-python/tree/main/src/payi/_response.py) with the same structure, the only difference being `await`able 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.
```python
with client.use_cases.definitions.with_streaming_response.create(
description="Sample Use Case Definition Description",
name="SampleUseCaseDefinition",
) 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.
```py
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`](https://docs.pydantic.dev/latest/api/base_model/#pydantic.BaseModel.model_extra).
### Configuring the HTTP client
You can directly override the [httpx client](https://www.python-httpx.org/api/#client) to customize it for your use case, including:
- Support for [proxies](https://www.python-httpx.org/advanced/proxies/)
- Custom [transports](https://www.python-httpx.org/advanced/transports/)
- Additional [advanced](https://www.python-httpx.org/advanced/clients/) functionality
```python
import httpx
from payi import Payi, DefaultHttpxClient
client = Payi(
# Or use the `PAYI_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()`:
```python
client.with_options(http_client=DefaultHttpxClient(...))
```
### Managing HTTP resources
By default the library closes underlying HTTP connections whenever the client is [garbage collected](https://docs.python.org/3/reference/datamodel.html#object.__del__). You can manually close the client using the `.close()` method if desired, or with a context manager that closes when exiting.
```py
from payi import Payi
with Payi() as client:
# make requests here
...
# HTTP client is now closed
```
## Versioning
This package generally follows [SemVer](https://semver.org/spec/v2.0.0.html) 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](https://www.github.com/Pay-i/pay-i-python/issues) 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:
```py
import payi
print(payi.__version__)
```
## Requirements
Python 3.8 or higher.
## Contributing
See [the contributing documentation](https://github.com/Pay-i/pay-i-python/tree/main/./CONTRIBUTING.md).
Raw data
{
"_id": null,
"home_page": null,
"name": "payi",
"maintainer": null,
"docs_url": null,
"requires_python": ">=3.8",
"maintainer_email": null,
"keywords": null,
"author": null,
"author_email": "Payi <support@payi.com>",
"download_url": "https://files.pythonhosted.org/packages/e6/6f/3d422d7882299269c02f8467caec21c06b40910b986215bbc61997d0b174/payi-0.1.0a106.tar.gz",
"platform": null,
"description": "# Payi Python API library\n\n<!-- prettier-ignore -->\n[)](https://pypi.org/project/payi/)\n\nThe Payi Python library provides convenient access to the Payi REST API from any Python 3.8+\napplication. The library includes type definitions for all request params and response fields,\nand offers both synchronous and asynchronous clients powered by [httpx](https://github.com/encode/httpx).\n\nIt is generated with [Stainless](https://www.stainless.com/).\n\n## Documentation\n\nThe REST API documentation can be found on [docs.payi.com](https://docs.payi.com). The full API of this library can be found in [api.md](https://github.com/Pay-i/pay-i-python/tree/main/api.md).\n\n## Installation\n\n```sh\n# install from PyPI\npip install --pre payi\n```\n\n## Usage\n\nThe full API of this library can be found in [api.md](https://github.com/Pay-i/pay-i-python/tree/main/api.md).\n\n```python\nimport os\nfrom payi import Payi\n\nclient = Payi(\n api_key=os.environ.get(\"PAYI_API_KEY\"), # This is the default and can be omitted\n)\n\nuse_case_definition = client.use_cases.definitions.create(\n description=\"Sample Use Case Definition Description\",\n name=\"SampleUseCaseDefinition\",\n)\nprint(use_case_definition.request_id)\n```\n\nWhile you can provide an `api_key` keyword argument,\nwe recommend using [python-dotenv](https://pypi.org/project/python-dotenv/)\nto add `PAYI_API_KEY=\"My API Key\"` to your `.env` file\nso that your API Key is not stored in source control.\n\n## Async usage\n\nSimply import `AsyncPayi` instead of `Payi` and use `await` with each API call:\n\n```python\nimport os\nimport asyncio\nfrom payi import AsyncPayi\n\nclient = AsyncPayi(\n api_key=os.environ.get(\"PAYI_API_KEY\"), # This is the default and can be omitted\n)\n\n\nasync def main() -> None:\n use_case_definition = await client.use_cases.definitions.create(\n description=\"Sample Use Case Definition Description\",\n name=\"SampleUseCaseDefinition\",\n )\n print(use_case_definition.request_id)\n\n\nasyncio.run(main())\n```\n\nFunctionality between the synchronous and asynchronous clients is otherwise identical.\n\n### With aiohttp\n\nBy default, the async client uses `httpx` for HTTP requests. However, for improved concurrency performance you may also use `aiohttp` as the HTTP backend.\n\nYou can enable this by installing `aiohttp`:\n\n```sh\n# install from PyPI\npip install --pre payi[aiohttp]\n```\n\nThen you can enable it by instantiating the client with `http_client=DefaultAioHttpClient()`:\n\n```python\nimport asyncio\nfrom payi import DefaultAioHttpClient\nfrom payi import AsyncPayi\n\n\nasync def main() -> None:\n async with AsyncPayi(\n api_key=\"My API Key\",\n http_client=DefaultAioHttpClient(),\n ) as client:\n use_case_definition = await client.use_cases.definitions.create(\n description=\"Sample Use Case Definition Description\",\n name=\"SampleUseCaseDefinition\",\n )\n print(use_case_definition.request_id)\n\n\nasyncio.run(main())\n```\n\n## Using types\n\nNested request parameters are [TypedDicts](https://docs.python.org/3/library/typing.html#typing.TypedDict). Responses are [Pydantic models](https://docs.pydantic.dev) which also provide helper methods for things like:\n\n- Serializing back into JSON, `model.to_json()`\n- Converting to a dictionary, `model.to_dict()`\n\nTyped 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`.\n\n## Pagination\n\nList methods in the Payi API are paginated.\n\nThis library provides auto-paginating iterators with each list response, so you do not have to request successive pages manually:\n\n```python\nfrom payi import Payi\n\nclient = Payi()\n\nall_definitions = []\n# Automatically fetches more pages as needed.\nfor definition in client.use_cases.definitions.list():\n # Do something with definition here\n all_definitions.append(definition)\nprint(all_definitions)\n```\n\nOr, asynchronously:\n\n```python\nimport asyncio\nfrom payi import AsyncPayi\n\nclient = AsyncPayi()\n\n\nasync def main() -> None:\n all_definitions = []\n # Iterate through items across all pages, issuing requests as needed.\n async for definition in client.use_cases.definitions.list():\n all_definitions.append(definition)\n print(all_definitions)\n\n\nasyncio.run(main())\n```\n\nAlternatively, you can use the `.has_next_page()`, `.next_page_info()`, or `.get_next_page()` methods for more granular control working with pages:\n\n```python\nfirst_page = await client.use_cases.definitions.list()\nif first_page.has_next_page():\n print(f\"will fetch next page using these details: {first_page.next_page_info()}\")\n next_page = await first_page.get_next_page()\n print(f\"number of items we just fetched: {len(next_page.items)}\")\n\n# Remove `await` for non-async usage.\n```\n\nOr just work directly with the returned data:\n\n```python\nfirst_page = await client.use_cases.definitions.list()\n\nprint(f\"next page cursor: {first_page.cursor}\") # => \"next page cursor: ...\"\nfor definition in first_page.items:\n print(definition.request_id)\n\n# Remove `await` for non-async usage.\n```\n\n## Nested params\n\nNested parameters are dictionaries, typed using `TypedDict`, for example:\n\n```python\nfrom payi import Payi\n\nclient = Payi()\n\nuse_case_definition = client.use_cases.definitions.create(\n description=\"x\",\n name=\"x\",\n limit_config={\"max\": 0},\n)\nprint(use_case_definition.limit_config)\n```\n\n## Handling errors\n\nWhen the library is unable to connect to the API (for example, due to network connection problems or a timeout), a subclass of `payi.APIConnectionError` is raised.\n\nWhen the API returns a non-success status code (that is, 4xx or 5xx\nresponse), a subclass of `payi.APIStatusError` is raised, containing `status_code` and `response` properties.\n\nAll errors inherit from `payi.APIError`.\n\n```python\nimport payi\nfrom payi import Payi\n\nclient = Payi()\n\ntry:\n client.use_cases.definitions.create(\n description=\"Sample Use Case Definition Description\",\n name=\"SampleUseCaseDefinition\",\n )\nexcept payi.APIConnectionError as e:\n print(\"The server could not be reached\")\n print(e.__cause__) # an underlying Exception, likely raised within httpx.\nexcept payi.RateLimitError as e:\n print(\"A 429 status code was received; we should back off a bit.\")\nexcept payi.APIStatusError as e:\n print(\"Another non-200-range status code was received\")\n print(e.status_code)\n print(e.response)\n```\n\nError codes are as follows:\n\n| Status Code | Error Type |\n| ----------- | -------------------------- |\n| 400 | `BadRequestError` |\n| 401 | `AuthenticationError` |\n| 403 | `PermissionDeniedError` |\n| 404 | `NotFoundError` |\n| 422 | `UnprocessableEntityError` |\n| 429 | `RateLimitError` |\n| >=500 | `InternalServerError` |\n| N/A | `APIConnectionError` |\n\n### Retries\n\nCertain errors are automatically retried 2 times by default, with a short exponential backoff.\nConnection errors (for example, due to a network connectivity problem), 408 Request Timeout, 409 Conflict,\n429 Rate Limit, and >=500 Internal errors are all retried by default.\n\nYou can use the `max_retries` option to configure or disable retry settings:\n\n```python\nfrom payi import Payi\n\n# Configure the default for all requests:\nclient = Payi(\n # default is 2\n max_retries=0,\n)\n\n# Or, configure per-request:\nclient.with_options(max_retries=5).use_cases.definitions.create(\n description=\"Sample Use Case Definition Description\",\n name=\"SampleUseCaseDefinition\",\n)\n```\n\n### Timeouts\n\nBy default requests time out after 1 minute. You can configure this with a `timeout` option,\nwhich accepts a float or an [`httpx.Timeout`](https://www.python-httpx.org/advanced/timeouts/#fine-tuning-the-configuration) object:\n\n```python\nfrom payi import Payi\n\n# Configure the default for all requests:\nclient = Payi(\n # 20 seconds (default is 1 minute)\n timeout=20.0,\n)\n\n# More granular control:\nclient = Payi(\n timeout=httpx.Timeout(60.0, read=5.0, write=10.0, connect=2.0),\n)\n\n# Override per-request:\nclient.with_options(timeout=5.0).use_cases.definitions.create(\n description=\"Sample Use Case Definition Description\",\n name=\"SampleUseCaseDefinition\",\n)\n```\n\nOn timeout, an `APITimeoutError` is thrown.\n\nNote that requests that time out are [retried twice by default](https://github.com/Pay-i/pay-i-python/tree/main/#retries).\n\n## Advanced\n\n### Logging\n\nWe use the standard library [`logging`](https://docs.python.org/3/library/logging.html) module.\n\nYou can enable logging by setting the environment variable `PAYI_LOG` to `info`.\n\n```shell\n$ export PAYI_LOG=info\n```\n\nOr to `debug` for more verbose logging.\n\n### How to tell whether `None` means `null` or missing\n\nIn 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`:\n\n```py\nif response.my_field is None:\n if 'my_field' not in response.model_fields_set:\n print('Got json like {}, without a \"my_field\" key present at all.')\n else:\n print('Got json like {\"my_field\": null}.')\n```\n\n### Accessing raw response data (e.g. headers)\n\nThe \"raw\" Response object can be accessed by prefixing `.with_raw_response.` to any HTTP method call, e.g.,\n\n```py\nfrom payi import Payi\n\nclient = Payi()\nresponse = client.use_cases.definitions.with_raw_response.create(\n description=\"Sample Use Case Definition Description\",\n name=\"SampleUseCaseDefinition\",\n)\nprint(response.headers.get('X-My-Header'))\n\ndefinition = response.parse() # get the object that `use_cases.definitions.create()` would have returned\nprint(definition.request_id)\n```\n\nThese methods return an [`APIResponse`](https://github.com/Pay-i/pay-i-python/tree/main/src/payi/_response.py) object.\n\nThe async client returns an [`AsyncAPIResponse`](https://github.com/Pay-i/pay-i-python/tree/main/src/payi/_response.py) with the same structure, the only difference being `await`able methods for reading the response content.\n\n#### `.with_streaming_response`\n\nThe above interface eagerly reads the full response body when you make the request, which may not always be what you want.\n\nTo 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.\n\n```python\nwith client.use_cases.definitions.with_streaming_response.create(\n description=\"Sample Use Case Definition Description\",\n name=\"SampleUseCaseDefinition\",\n) as response:\n print(response.headers.get(\"X-My-Header\"))\n\n for line in response.iter_lines():\n print(line)\n```\n\nThe context manager is required so that the response will reliably be closed.\n\n### Making custom/undocumented requests\n\nThis library is typed for convenient access to the documented API.\n\nIf you need to access undocumented endpoints, params, or response properties, the library can still be used.\n\n#### Undocumented endpoints\n\nTo make requests to undocumented endpoints, you can make requests using `client.get`, `client.post`, and other\nhttp verbs. Options on the client will be respected (such as retries) when making this request.\n\n```py\nimport httpx\n\nresponse = client.post(\n \"/foo\",\n cast_to=httpx.Response,\n body={\"my_param\": True},\n)\n\nprint(response.headers.get(\"x-foo\"))\n```\n\n#### Undocumented request params\n\nIf you want to explicitly send an extra param, you can do so with the `extra_query`, `extra_body`, and `extra_headers` request\noptions.\n\n#### Undocumented response properties\n\nTo access undocumented response properties, you can access the extra fields like `response.unknown_prop`. You\ncan also get all the extra fields on the Pydantic model as a dict with\n[`response.model_extra`](https://docs.pydantic.dev/latest/api/base_model/#pydantic.BaseModel.model_extra).\n\n### Configuring the HTTP client\n\nYou can directly override the [httpx client](https://www.python-httpx.org/api/#client) to customize it for your use case, including:\n\n- Support for [proxies](https://www.python-httpx.org/advanced/proxies/)\n- Custom [transports](https://www.python-httpx.org/advanced/transports/)\n- Additional [advanced](https://www.python-httpx.org/advanced/clients/) functionality\n\n```python\nimport httpx\nfrom payi import Payi, DefaultHttpxClient\n\nclient = Payi(\n # Or use the `PAYI_BASE_URL` env var\n base_url=\"http://my.test.server.example.com:8083\",\n http_client=DefaultHttpxClient(\n proxy=\"http://my.test.proxy.example.com\",\n transport=httpx.HTTPTransport(local_address=\"0.0.0.0\"),\n ),\n)\n```\n\nYou can also customize the client on a per-request basis by using `with_options()`:\n\n```python\nclient.with_options(http_client=DefaultHttpxClient(...))\n```\n\n### Managing HTTP resources\n\nBy default the library closes underlying HTTP connections whenever the client is [garbage collected](https://docs.python.org/3/reference/datamodel.html#object.__del__). You can manually close the client using the `.close()` method if desired, or with a context manager that closes when exiting.\n\n```py\nfrom payi import Payi\n\nwith Payi() as client:\n # make requests here\n ...\n\n# HTTP client is now closed\n```\n\n## Versioning\n\nThis package generally follows [SemVer](https://semver.org/spec/v2.0.0.html) conventions, though certain backwards-incompatible changes may be released as minor versions:\n\n1. Changes that only affect static types, without breaking runtime behavior.\n2. 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.)_\n3. Changes that we do not expect to impact the vast majority of users in practice.\n\nWe take backwards-compatibility seriously and work hard to ensure you can rely on a smooth upgrade experience.\n\nWe are keen for your feedback; please open an [issue](https://www.github.com/Pay-i/pay-i-python/issues) with questions, bugs, or suggestions.\n\n### Determining the installed version\n\nIf 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.\n\nYou can determine the version that is being used at runtime with:\n\n```py\nimport payi\nprint(payi.__version__)\n```\n\n## Requirements\n\nPython 3.8 or higher.\n\n## Contributing\n\nSee [the contributing documentation](https://github.com/Pay-i/pay-i-python/tree/main/./CONTRIBUTING.md).\n",
"bugtrack_url": null,
"license": "Apache-2.0",
"summary": "The official Python library for the payi API",
"version": "0.1.0a106",
"project_urls": {
"Homepage": "https://github.com/Pay-i/pay-i-python",
"Repository": "https://github.com/Pay-i/pay-i-python"
},
"split_keywords": [],
"urls": [
{
"comment_text": "",
"digests": {
"blake2b_256": "12000b7357a3799f69d82c7fb070046d67b8809aee9949379efc11be20ad1bc0",
"md5": "1a4e75128f373a7bd378274bf8148092",
"sha256": "410f18ead2902bdd12bb609f0a331e5c59bff3ac635c78e19e65f7c4e94ade83"
},
"downloads": -1,
"filename": "payi-0.1.0a106-py3-none-any.whl",
"has_sig": false,
"md5_digest": "1a4e75128f373a7bd378274bf8148092",
"packagetype": "bdist_wheel",
"python_version": "py3",
"requires_python": ">=3.8",
"size": 176459,
"upload_time": "2025-07-30T00:23:21",
"upload_time_iso_8601": "2025-07-30T00:23:21.222421Z",
"url": "https://files.pythonhosted.org/packages/12/00/0b7357a3799f69d82c7fb070046d67b8809aee9949379efc11be20ad1bc0/payi-0.1.0a106-py3-none-any.whl",
"yanked": false,
"yanked_reason": null
},
{
"comment_text": "",
"digests": {
"blake2b_256": "e66f3d422d7882299269c02f8467caec21c06b40910b986215bbc61997d0b174",
"md5": "824ef949e43beda6c8723b1d5c6b80f4",
"sha256": "1af4f533c51e537444996a863ac8ccbf8e665f3a66a3dd3866c78e9eee053c0c"
},
"downloads": -1,
"filename": "payi-0.1.0a106.tar.gz",
"has_sig": false,
"md5_digest": "824ef949e43beda6c8723b1d5c6b80f4",
"packagetype": "sdist",
"python_version": "source",
"requires_python": ">=3.8",
"size": 166062,
"upload_time": "2025-07-30T00:23:22",
"upload_time_iso_8601": "2025-07-30T00:23:22.899980Z",
"url": "https://files.pythonhosted.org/packages/e6/6f/3d422d7882299269c02f8467caec21c06b40910b986215bbc61997d0b174/payi-0.1.0a106.tar.gz",
"yanked": false,
"yanked_reason": null
}
],
"upload_time": "2025-07-30 00:23:22",
"github": true,
"gitlab": false,
"bitbucket": false,
"codeberg": false,
"github_user": "Pay-i",
"github_project": "pay-i-python",
"github_not_found": true,
"lcname": "payi"
}