Skip to main content

Inttegro Python SDK

OpenSSF Scorecard

The official Python client for building server-side Inttegro integrations, with native asynchronous and synchronous clients.

API documentation · Integration guides

Fastest, most modern path: connect an agent to Inttegro MCP at https://mcp.inttegro.com, then ask it to run design_integration. It will produce an implementation and test plan for your application. Use this SDK when you are ready to connect that plan to your Python service.

All official Inttegro SDKs expose the same API capabilities. This package adds Python-specific data access, transports, and test seams.

Install

Requires Python 3.10 or newer.

pip install inttegro

Store your secret key in the server environment:

export INTTEGRO_API_KEY="your_secret_key"

Never put the key in browser code, a mobile app, or source control. The client uses https://api.inttegro.com by default.

Choose a client

AsyncInttegroClient is the default shown in new integration examples. Use it in FastAPI, Starlette, Quart, async Django views, Python Workers, and other event-loop applications. Its HTTP requests are non-blocking and share one connection pool:

import os

from inttegro import AsyncInttegroClient

async with AsyncInttegroClient(api_key=os.environ["INTTEGRO_API_KEY"]) as client:
    order = await client.orders.lookup("or_...")

Create one long-lived client during application startup and call aclose() during shutdown. An async with block is useful for scripts and jobs. Every resource operation on the async client is awaited.

Use InttegroClient in synchronous Django views, Flask, command-line tools, or other code without an event loop:

import os

from inttegro import InttegroClient

client = InttegroClient(api_key=os.environ["INTTEGRO_API_KEY"])
order = client.orders.lookup("or_...")

The two clients expose the same resources, request types, returned domain models, errors, idempotency behavior, and telemetry contract. Do not call the synchronous client directly from an async request handler because it blocks the event loop. The distinct class name is intentional: silently changing the existing InttegroClient methods from values to awaitables would break every synchronous integration. Version 6.3.0 therefore makes the async client the recommended default while preserving the synchronous client as a compatible, explicit option for genuinely synchronous applications.

Create a hosted checkout

Create and finalize an order, then send the customer to its hosted invoice URL:

import os

import inttegro
from inttegro import APIError, LineItemType, ProductType

async def create_checkout() -> str:
    request = inttegro.orders.CreateRequest(
        request_meta=inttegro.orders.RequestMeta(
            idempotency_key="checkout-cart-123",
        ),
        customer_data=inttegro.orders.Customer(
            name="Akua Mensah",
            email_address="akua@example.com",
            phone_number="+233544998605",
        ),
        finalize=True,
        checkout_settings=inttegro.orders.CheckoutSettings(
            redirect_url="https://example.com/orders/complete",
            cancel_url="https://example.com/cart",
        ),
        line_items=[
            inttegro.orders.ProductLineItem(
                type=LineItemType.PRODUCT,
                product=inttegro.orders.Product(
                    type=ProductType.DIGITAL,
                    name="Monthly subscription",
                    quantity=1,
                    price=inttegro.PriceParams(currency=inttegro.Currency.GHS, value=5000),
                ),
            ),
        ],
    )
    try:
        async with inttegro.AsyncInttegroClient(
            api_key=os.environ["INTTEGRO_API_KEY"],
        ) as client:
            order = await client.orders.create(request)
            return order.invoice.format.web.url
    except APIError as error:
        print(error.code, error.detail or str(error))
        raise

Amounts use integer minor units: 5000 GHS is GHS 50.00. Reuse the same idempotency key when retrying the same logical write. If you omit one, the SDK generates a UUIDv7 key for mutating calls.

Observe SDK operations

The SDK emits vendor-neutral OpenTelemetry spans through your application's provider. It never configures an exporter or sends telemetry by itself. Configure OpenTelemetry at application startup; the global provider is used automatically, or pass tracer_provider explicitly:

client = inttegro.AsyncInttegroClient(
    api_key=os.environ["INTTEGRO_API_KEY"],
    tracer_provider=tracer_provider,
)

Spans are named after logical operations such as inttegro.orders.create. HTTP attempts, response receipt, and decoding are span events. API keys, bodies, resource IDs, dynamic URLs, and exception messages are never recorded. See SDK observability for the complete contract and set telemetry_enabled=False when needed.

Report SDK failures

Provide an application-owned reporter to receive one immutable, typed, privacy-safe report after an SDK operation finally fails. The default "unexpected" policy reports transport, timeout, decoding, SDK, unknown_error, and server-side failures while leaving normal 4xx API errors alone:

client = inttegro.InttegroClient(
    api_key=os.environ["INTTEGRO_API_KEY"],
    error_reporter=error_collector.enqueue,
)

Use error_reporting_policy="all" to include expected API failures; cancellations are never reported. Call report.to_dict() when a collector needs a JSON-serializable value. Reports contain the logical operation, static route, server host, status and request IDs when available, duration, safe API error codes, SDK identity, stable fingerprint, exception type, and trace IDs when tracing is active. They exclude credentials, headers, bodies, resource IDs, dynamic URLs, exception messages, and stack traces. Reporter failures are isolated and the original SDK error is still raised.

Error reporting is completely opt-in. Without error_reporter, the SDK does not calculate report metadata, create an event ID or timestamp, allocate a report, or serialize a payload.

Work with the API

The SDK covers orders and checkout, customers, products and prices, purchase intents, payment methods, balances, payouts and refunds, notifications, files, application settings, keys, and country specifications. Resources use snake-case attributes such as purchase_intents and payment_methods.

Python-specific features:

  • Native async HTTP transport powered by HTTPX, plus a dependency-light synchronous standard-library transport.
  • OpenAPI-generated, immutable request and domain dataclasses with fully typed nested fields.
  • Resource namespaces such as inttegro.orders.CreateRequest keep related request objects together.
  • Backwards-compatible mapping access and to_dict() conversion on every domain object.
  • Backwards-compatible dictionary request payloads for integrations migrating to typed objects.
  • JSON-compatible string enums for public API values.
  • Configurable timeout, base URL, and injectable transport for tests or custom networking.
  • Structured authentication, rate-limit, network, timeout, and API exceptions.

Request and returned domain fields are available to editors, Pyright, and mypy without plugins:

import os

import inttegro

client = inttegro.AsyncInttegroClient(api_key=os.environ["INTTEGRO_API_KEY"])

request = inttegro.refunds.CreateRequest(
    order_id="or_0123456789abcdefghijklmnopqrstuvwxyzABCD",
    reason=inttegro.RefundReason.REQUESTED_BY_CUSTOMER,
    line_items=[
        inttegro.refunds.LineItem(
            order_line_item_id="oli_abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMN",
            refund_amount=inttegro.AmountParams(currency=inttegro.Currency.GHS, value=2500),
        ),
    ],
)

refund: inttegro.Refund = await client.refunds.create(request)
print(refund.id, refund.total.value)

See the API reference for request fields and lifecycle rules, errors for recovery guidance, and idempotency for safe retries.

Verify a release

The GitHub release for each version is the canonical record. It contains the exact wheel and source distribution uploaded to PyPI, SHA-256 checksums, and a Sigstore attestation tied to the source commit and release workflow.

sha256sum --check SHA256SUMS
gh attestation verify inttegro-6.3.0-py3-none-any.whl \
  --repo zebodotdev/inttegro-sdk-python

Develop

poetry install
poetry run python scripts/generate_async_resources.py --check
poetry run python -m unittest discover -s tests -p "test_*.py"
poetry run mypy src
poetry run pyright

Release files for inttegro 6.3.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for inttegro 6.3.0
File Size Uploaded
inttegro-6.3.0.tar.gz 101.1 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for inttegro 6.3.0
File Interpreter ABI Platform
inttegro-6.3.0-py3-none-any.whl Python 3 none any Details

Total release size: 253.4 kB

Release files / inttegro-6.3.0.tar.gz

Download URL inttegro-6.3.0.tar.gz
Size 101.1 kB
Tags Source
SHA-256 checksum
How to use checksums
c8e444a0a2176542c34405bf1fb8d7d432178047b10df81440bac6482438ae5e
BLAKE2b-256 checksum
How to use checksums
34132de42817caf8605cade332174409f5ecd77ccc4d8cf3f3d38f79b6433623
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 7, 2026.

Transparency log

Release files / inttegro-6.3.0-py3-none-any.whl

Download URL inttegro-6.3.0-py3-none-any.whl
Size 152.3 kB
Tags Python 3
SHA-256 checksum
How to use checksums
39256c1546cbe18829eff53984e1f00e27393ee9ce2daf043fbcacf8a22110e9
BLAKE2b-256 checksum
How to use checksums
d46b4de31e201a36d0bffd477f68502efadd09e9f5db53e87c590bf2da81f1af
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 7, 2026.

Transparency log

Release history Release notifications | RSS feed

10.1.0

2 release files

10.0.1

2 release files

10.0.0

2 release files

9.0.0

2 release files

8.0.0

2 release files

7.0.0

2 release files

6.3.1

2 release files

This release

6.3.0 This release

2 release files

6.2.0

2 release files

6.1.2

2 release files

6.1.1

2 release files

6.0.0

2 release files

5.0.0

2 release files

4.0.0

2 release files

3.0.1

2 release files

3.0.0

2 release files

2.1.0

2 release files

2.0.0

2 release files

1.0.0

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page