factify 1.0.1

Python SDK for the Factify API

Factify Python SDK

Python SDK for the Factify API.

Summary

Factify API: Factify API enables you to create, manage, and control access to legally-binding documents that replace PDFs.

Authentication

Bearer authentication header of the form Bearer , where is your auth token.

Authorization: Bearer ffy...

Rate Limiting

• 1000 requests per minute per API key
• 100 requests per minute for resource creation (POST)

Errors

Factify uses conventional HTTP status codes and returns structured error responses using the ConnectRPC error format:

{
  "code": "invalid_argument",
  "message": "limit must be positive",
  "details": [
    {
      "reason": "invalid_field_value",
      "request_id": "req_01arwx4k8xrgqskvxq69gdn019",
      "param": "limit"
    }
  ]
}

Table of Contents

• Factify Python SDK
  • Authentication
  • Rate Limiting
  • Errors
  • SDK Installation
  • IDE Support
  • SDK Example Usage
  • Authentication
  • Available Resources and Operations
  • Pagination
  • File uploads
  • Retries
  • Error Handling
  • Server Selection
  • Custom HTTP Client
  • Resource Management
  • Debugging

SDK Installation

[!NOTE] Python version upgrade policy

Once a Python version reaches its official end of life date, a 3-month grace period is provided for users to upgrade. Following this grace period, the minimum python version supported in the SDK will be updated.

The SDK can be installed with uv, pip, or poetry package managers.

uv

uv is a fast Python package installer and resolver, designed as a drop-in replacement for pip and pip-tools. It's recommended for its speed and modern Python tooling capabilities.

uv add factify

PIP

PIP is the default package installer for Python, enabling easy installation and management of packages from PyPI via the command line.

pip install factify

Poetry

Poetry is a modern tool that simplifies dependency management and package publishing by using a single pyproject.toml file to handle project metadata and dependencies.

poetry add factify

Shell and script usage with uv

You can use this SDK in a Python shell with uv and the uvx command that comes with it like so:

uvx --from factify python

It's also possible to write a standalone Python script without needing to set up a whole project like so:

#!/usr/bin/env -S uv run --script
# /// script
# requires-python = ">=3.10"
# dependencies = [
#     "factify",
# ]
# ///

from factify import Factify

sdk = Factify(
  # SDK arguments
)

# Rest of script here...

Once that is saved to a file, you can run it with uv run script.py where script.py can be replaced with the actual file name.

IDE Support

PyCharm

Generally, the SDK will work well with most IDEs out of the box. However, when using PyCharm, you can enjoy much better integration with Pydantic by installing an additional plugin.

• PyCharm Pydantic Plugin

SDK Example Usage

Example

# Synchronous Example
from factify import Factify
from factify.utils import parse_datetime


with Factify(
    bearer_auth="<YOUR_BEARER_TOKEN_HERE>",
) as f_client:

    res = f_client.documents.list(page_token="eyJpZCI6ImRvY18wMWgyeGNlanF0ZjJuYnJleHgzdnFqaHA0MSIsImQiOiJuZXh0In0", created_after=parse_datetime("2023-01-15T01:30:15.01Z"), created_before=parse_datetime("2023-01-15T01:30:15.01Z"))

    while res is not None:
        # Handle items

        res = res.next()

The same SDK client can also be used to make asynchronous requests by importing asyncio.

# Asynchronous Example
import asyncio
from factify import Factify
from factify.utils import parse_datetime

async def main():

    async with Factify(
        bearer_auth="<YOUR_BEARER_TOKEN_HERE>",
    ) as f_client:

        res = await f_client.documents.list_async(page_token="eyJpZCI6ImRvY18wMWgyeGNlanF0ZjJuYnJleHgzdnFqaHA0MSIsImQiOiJuZXh0In0", created_after=parse_datetime("2023-01-15T01:30:15.01Z"), created_before=parse_datetime("2023-01-15T01:30:15.01Z"))

        while res is not None:
            # Handle items

            res = res.next()

asyncio.run(main())

Authentication

Per-Client Security Schemes

This SDK supports the following security scheme globally:

Name	Type	Scheme
bearer_auth	http	HTTP Bearer

To authenticate with the API the bearer_auth parameter must be set when initializing the SDK client instance. For example:

from factify import Factify


with Factify(
    bearer_auth="<YOUR_BEARER_TOKEN_HERE>",
) as f_client:

    res = f_client.api_keys.list(organization_id="<id>")

    while res is not None:
        # Handle items

        res = res.next()

Available Resources and Operations

Available methods

AccessRequests

• inspect - Inspect document access
• list - List access requests
• create - Create an access request
• check_status - Check access request status
• approve - Approve an access request
• deny - Deny an access request

APIKeys

• list - List API keys
• create - Create an API key
• revoke - Revoke an API key

Documents

• list - List documents
• create - Create a document
• get_quota - Get document quota
• get - Retrieve a document
• update - Update a document
• list_duplicates - List duplicate documents
• export - Export a document
• process - Process a document
• transfer_ownership - Transfer document ownership
• trash - Trash a document
• untrash - Restore a document from trash

EntryPages

• generate - Generate entry page

Organizations

• list - List organizations
• get - Retrieve an organization
• update - Update an organization

Organizations.Invites

• list - List organization invitations
• create - Invite a user to join an organization
• accept - Accept an invitation
• resend - Resend an invitation email
• revoke - Revoke an invitation

Organizations.Members

• list - List organization members
• add - Add a member to an organization
• remove - Remove an organization member
• update - Update an organization member

Policies

• list - List document policies
• attach - Attach a policy
• detach - Detach a policy

Sharing

• get_general_access - Get general access
• set_general_access - Set general access
• list - List document access
• grant - Grant document access
• create_share_link - Create share link
• revoke - Revoke document access
• update - Update document access

Timelines

• get - Get document timeline

Usage

• get - Get organization quota status
• list_key_quotas - List API key quotas
• delete_key_quota - Delete API key quota
• set_key_quota - Set API key quota
• get_history - Get usage history

UserPreferences

• get - Get user preferences

Users

• get_me - Get current user

Versions

• list - List document versions
• create - Create a new version
• get - Retrieve a version
• update - Update a version

Pagination

Some of the endpoints in this SDK support pagination. To use pagination, you make your SDK calls as usual, but the returned response object will have a Next method that can be called to pull down the next group of results. If the return value of Next is None, then there are no more pages to be fetched.

Here's an example of one such pagination call:

from factify import Factify


with Factify(
    bearer_auth="<YOUR_BEARER_TOKEN_HERE>",
) as f_client:

    res = f_client.api_keys.list(organization_id="<id>")

    while res is not None:
        # Handle items

        res = res.next()

File uploads

Certain SDK methods accept file objects as part of a request body or multi-part request. It is possible and typically recommended to upload files as a stream rather than reading the entire contents into memory. This avoids excessive memory consumption and potentially crashing with out-of-memory errors when working with very large files. The following example demonstrates how to attach a file stream to a request.

[!TIP]

For endpoints that handle file uploads bytes arrays can also be used. However, using streams is recommended for large files.

from factify import Factify


with Factify(
    bearer_auth="<YOUR_BEARER_TOKEN_HERE>",
) as f_client:

    res = f_client.documents.create(payload={
        "file_name": "example.file",
        "content": open("example.file", "rb"),
    }, title="<value>")

    # Handle response
    print(res)

Retries

Some of the endpoints in this SDK support retries. If you use the SDK without any configuration, it will fall back to the default retry strategy provided by the API. However, the default retry strategy can be overridden on a per-operation basis, or across the entire SDK.

To change the default retry strategy for a single API call, simply provide a RetryConfig object to the call:

from factify import Factify
from factify.utils import BackoffStrategy, RetryConfig


with Factify(
    bearer_auth="<YOUR_BEARER_TOKEN_HERE>",
) as f_client:

    res = f_client.api_keys.list(organization_id="<id>",
        RetryConfig("backoff", BackoffStrategy(1, 50, 1.1, 100), False))

    while res is not None:
        # Handle items

        res = res.next()

If you'd like to override the default retry strategy for all operations that support retries, you can use the retry_config optional parameter when initializing the SDK:

from factify import Factify
from factify.utils import BackoffStrategy, RetryConfig


with Factify(
    retry_config=RetryConfig("backoff", BackoffStrategy(1, 50, 1.1, 100), False),
    bearer_auth="<YOUR_BEARER_TOKEN_HERE>",
) as f_client:

    res = f_client.api_keys.list(organization_id="<id>")

    while res is not None:
        # Handle items

        res = res.next()

Error Handling

FactifyError is the base class for all HTTP error responses. It has the following properties:

Property	Type	Description
err.message	str	Error message
err.status_code	int	HTTP response status code eg 404
err.headers	httpx.Headers	HTTP response headers
err.body	str	HTTP body. Can be empty string if no body is returned.
err.raw_response	httpx.Response	Raw HTTP response
err.data		Optional. Some errors may contain structured data. See Error Classes.

Example

from factify import Factify, errors


with Factify(
    bearer_auth="<YOUR_BEARER_TOKEN_HERE>",
) as f_client:
    res = None
    try:

        res = f_client.api_keys.list(organization_id="<id>")

        while res is not None:
            # Handle items

            res = res.next()


    except errors.FactifyError as e:
        # The base class for HTTP error responses
        print(e.message)
        print(e.status_code)
        print(e.body)
        print(e.headers)
        print(e.raw_response)

        # Depending on the method different errors may be thrown
        if isinstance(e, errors.ErrorResponse):
            print(e.data.code)  # models.Code
            print(e.data.details)  # Optional[List[models.ErrorDetail]]
            print(e.data.message)  # str

Error Classes

Primary errors:

• FactifyError: The base class for HTTP error responses.
  • ErrorResponse: Invalid request parameters.

Less common errors (5)

Network errors:

• httpx.RequestError: Base class for request errors.
  • httpx.ConnectError: HTTP client was unable to make a request to a server.
  • httpx.TimeoutException: HTTP request timed out.

Inherit from FactifyError:

• ResponseValidationError: Type mismatch between the response data and the expected Pydantic model. Provides access to the Pydantic validation error via the cause attribute.

Server Selection

Select Server by Index

You can override the default server globally by passing a server index to the server_idx: int optional parameter when initializing the SDK client instance. The selected server will then be used as the default on the operations that use it. This table lists the indexes associated with the available servers:

#	Server	Description
0	https://api.factify.com	Production
1	https://api.factify-dev.com	Development (internal only)

Example

from factify import Factify


with Factify(
    server_idx=0,
    bearer_auth="<YOUR_BEARER_TOKEN_HERE>",
) as f_client:

    res = f_client.api_keys.list(organization_id="<id>")

    while res is not None:
        # Handle items

        res = res.next()

Override Server URL Per-Client

The default server can also be overridden globally by passing a URL to the server_url: str optional parameter when initializing the SDK client instance. For example:

from factify import Factify


with Factify(
    server_url="https://api.factify-dev.com",
    bearer_auth="<YOUR_BEARER_TOKEN_HERE>",
) as f_client:

    res = f_client.api_keys.list(organization_id="<id>")

    while res is not None:
        # Handle items

        res = res.next()

Custom HTTP Client

The Python SDK makes API calls using the httpx HTTP library. In order to provide a convenient way to configure timeouts, cookies, proxies, custom headers, and other low-level configuration, you can initialize the SDK client with your own HTTP client instance. Depending on whether you are using the sync or async version of the SDK, you can pass an instance of HttpClient or AsyncHttpClient respectively, which are Protocol's ensuring that the client has the necessary methods to make API calls. This allows you to wrap the client with your own custom logic, such as adding custom headers, logging, or error handling, or you can just pass an instance of httpx.Client or httpx.AsyncClient directly.

For example, you could specify a header for every request that this sdk makes as follows:

from factify import Factify
import httpx

http_client = httpx.Client(headers={"x-custom-header": "someValue"})
s = Factify(client=http_client)

or you could wrap the client with your own custom logic:

from factify import Factify
from factify.httpclient import AsyncHttpClient
import httpx

class CustomClient(AsyncHttpClient):
    client: AsyncHttpClient

    def __init__(self, client: AsyncHttpClient):
        self.client = client

    async def send(
        self,
        request: httpx.Request,
        *,
        stream: bool = False,
        auth: Union[
            httpx._types.AuthTypes, httpx._client.UseClientDefault, None
        ] = httpx.USE_CLIENT_DEFAULT,
        follow_redirects: Union[
            bool, httpx._client.UseClientDefault
        ] = httpx.USE_CLIENT_DEFAULT,
    ) -> httpx.Response:
        request.headers["Client-Level-Header"] = "added by client"

        return await self.client.send(
            request, stream=stream, auth=auth, follow_redirects=follow_redirects
        )

    def build_request(
        self,
        method: str,
        url: httpx._types.URLTypes,
        *,
        content: Optional[httpx._types.RequestContent] = None,
        data: Optional[httpx._types.RequestData] = None,
        files: Optional[httpx._types.RequestFiles] = None,
        json: Optional[Any] = None,
        params: Optional[httpx._types.QueryParamTypes] = None,
        headers: Optional[httpx._types.HeaderTypes] = None,
        cookies: Optional[httpx._types.CookieTypes] = None,
        timeout: Union[
            httpx._types.TimeoutTypes, httpx._client.UseClientDefault
        ] = httpx.USE_CLIENT_DEFAULT,
        extensions: Optional[httpx._types.RequestExtensions] = None,
    ) -> httpx.Request:
        return self.client.build_request(
            method,
            url,
            content=content,
            data=data,
            files=files,
            json=json,
            params=params,
            headers=headers,
            cookies=cookies,
            timeout=timeout,
            extensions=extensions,
        )

s = Factify(async_client=CustomClient(httpx.AsyncClient()))

Resource Management

The Factify class implements the context manager protocol and registers a finalizer function to close the underlying sync and async HTTPX clients it uses under the hood. This will close HTTP connections, release memory and free up other resources held by the SDK. In short-lived Python programs and notebooks that make a few SDK method calls, resource management may not be a concern. However, in longer-lived programs, it is beneficial to create a single SDK instance via a context manager and reuse it across the application.

from factify import Factify
def main():

    with Factify(
        bearer_auth="<YOUR_BEARER_TOKEN_HERE>",
    ) as f_client:
        # Rest of application here...


# Or when using async:
async def amain():

    async with Factify(
        bearer_auth="<YOUR_BEARER_TOKEN_HERE>",
    ) as f_client:
        # Rest of application here...

Debugging

You can setup your SDK to emit debug logs for SDK requests and responses.

You can pass your own logger class directly into your SDK.

from factify import Factify
import logging

logging.basicConfig(level=logging.DEBUG)
s = Factify(debug_logger=logging.getLogger("factify"))