Skip to main content

Inttegro Python SDK

The Inttegro Python SDK builds server-side integrations with typed request dataclasses, immutable domain objects, JSON-compatible enums, and Python-native resource namespaces.

Start with MCP

Before writing SDK code, connect your MCP client and ask MCP to design the integration for your Python application. Use the resulting implementation and test plan to guide the code you write with this SDK.

Install

The SDK requires Python 3.10 or newer. Install the package from PyPI:

pip install inttegro
Keep the SDK on the server

Load the secret API key securely from server-side code. Never place the key in browser code, a mobile application, or source control.

Create a client

import os

import inttegro

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

Request classes live with their resource, such as inttegro.orders.CreateRequest. Returned resources are typed domain objects with attribute access, backwards-compatible mapping access, and to_dict().

See it in a complete app

Use either demo to follow a ticket sale from reservation to Inttegro Checkout:

Both keep the ticket, price, and fulfillment decision on the server and use the Python SDK to create the payable order.

Observability

The global OpenTelemetry provider is used automatically. Pass a provider when the client should use an explicitly managed tracing pipeline:

import os

import inttegro
from opentelemetry import trace

client = inttegro.InttegroClient(
    api_key=os.environ["INTTEGRO_API_KEY"],
    tracer_provider=trace.get_tracer_provider(),
)

Inttegro emits vendor-neutral OpenTelemetry spans through the provider configured by your application. The SDK does not choose an exporter or observability vendor, and it does not send telemetry by itself.

Each public SDK call creates one CLIENT span named after the logical operation, such as inttegro.orders.create. HTTP attempts, retries, response receipt, decoding, and failures appear as events on that span. W3C trace context is propagated on outbound requests.

Span attributes and data-safety contract

The stable attributes are:

  • inttegro.operation.name, SDK language and SDK version
  • HTTP method and response status when available
  • destination host and the static API route template
  • the safe request identifier returned by the API
  • a low-cardinality failure category such as a timeout

SDK telemetry never records API keys, authorization headers, request or response bodies, customer or payment data, resource identifiers, dynamic URLs, query strings, exception messages, or stack traces.

To turn off Inttegro instrumentation for a client, use telemetry_enabled=False.

Report SDK failures​

Pass an application-owned callback to receive one immutable, typed report after an SDK operation finally fails:

import os

import inttegro


def enqueue_error(report: inttegro.ErrorReport) -> None:
    payload = report.to_dict()
    _ = payload  # Forward the payload to your collector or queue.


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

The default policy reports transport, timeout, decoding, SDK, unknown, and server-side failures. Expected API failures such as normal 4xx responses stay with the caller. Use error_reporting_policy="all" when the collector should receive those failures too. Cancellation is never reported.

When the collector needs a JSON-compatible payload, use report.to_dict().

Report fields and data-safety contract

A report contains:

  • the logical operation, static route, server host, status, duration, and safe request identifier when available
  • safe API error codes and a stable, low-cardinality fingerprint
  • SDK identity, exception type, and active trace identifiers

Reports never contain API keys, authorization headers, request or response bodies, customer or payment data, resource identifiers, dynamic URLs, query strings, exception messages, or stack traces.

Reporting is completely opt-in. Unless error_reporter is configured, the SDK does no reporting-specific timing or metadata preparation, creates no event ID or report object, and serializes nothing. Report construction and collector failures are isolated, so the caller still receives the original SDK failure.

Continue