extend-python

Python library for the Extend API

A Python client for the Extend API, providing a simple and intuitive interface for managing virtual cards, transactions, and more.

Features

• Create and manage virtual cards
• Handle recurring card operations
• Track transactions
• Expense management

Documentation

For detailed API documentation, please visit our Stoplight documentation.

Installation

From PyPI

pip install paywithextend

From Source

git clone https://github.com/paywithextend/extend-python.git
cd extend-python
pip install -e .

Quick Start

Version 3 requires explicit environment selection and client cleanup. See the migration guide for security and compatibility changes.

import asyncio
from extend import ExtendClient
from extend.auth import BasicAuth


async def main():
    # Initialize the client
    async with ExtendClient(
        auth=BasicAuth(
            "your-api-key",
            "your-api-secret",
        ),
        environment="stage",
    ) as client:
        response = await client.virtual_cards.get_virtual_cards()
        # Handle the result in your application; avoid logging financial payloads.


# Run the async function
asyncio.run(main())

Using Custom Authorization

Both ExtendClient and APIClient accept reusable authorization strategies defined in extend.auth, enabling scenarios like JWT-based access or shared credentials across clients.

from extend import ExtendClient
from extend.auth import BearerAuth

auth = BearerAuth(jwt_token="your-jwt-token")
client = ExtendClient(auth=auth, environment="stage")
# await client.aclose() when finished, or prefer async with.

If you want to work with the lower-level APIClient directly, you can pass any Authorization implementation:

from extend.auth import BasicAuth
from extend.client import APIClient

api_client = APIClient(auth=BasicAuth("your-api-key", "your-api-secret"), environment="stage")
# await api_client.aclose() when finished.

Environment Variables

Examples may read EXTEND_API_KEY and EXTEND_API_SECRET explicitly in application code. The SDK and test suite do not automatically load .env files. Live tests use separate EXTEND_TEST_API_KEY / EXTEND_TEST_API_SECRET variables and an explicitly supplied private fixture file. See Testing.

Development Setup

1. Clone the repository:

   git clone https://github.com/paywithextend/extend-python.git
   cd extend-python
   

2. Create and activate a virtual environment:

   python -m venv venv
   source venv/bin/activate  # On Windows: venv\Scripts\activate
   

3. Install development dependencies:

   pip install -e ".[dev]"
   

4. Run tests:

   # Complete offline suite; no account or credentials required.
   python -m pytest -q
   make lint
   

Testing

The default suite verifies every resource's HTTP contract, authentication, errors, transport security, retries, and cleanup without contacting Extend. CI runs it from source and against an installed wheel on Python 3.11–3.14.

Live tests are opt-in and use explicitly provisioned resources. Writes, receipt matching, and reminders each require explicit flags. See the contributor testing guide for fixture setup and cleanup.

Contributing

We welcome contributions from the community!

1. Fork the repository
2. Create your feature branch (git checkout -b feature/amazing-feature)
3. Commit your changes (git commit -m 'Add some amazing feature')
4. Push to the branch (git push origin feature/amazing-feature)
5. Open a Pull Request

License

This project is licensed under the MIT License - see the LICENSE file for details.

Acknowledgments

• Extend API Documentation
• httpx for async HTTP requests

Endpoint availability

Server implementation, public gateway exposure, and account permissions are separate requirements. Organization, member, policy, user, and individual-label helpers may return 403 where the public gateway does not expose those routes. Receipt deletion is also unavailable on some gateways even when upload is enabled. Offline contract tests verify serialization; they do not establish deployed route availability.