linkbridge (Python SDK)
Official Python client for the Linkbridge
e-invoicing API. Mirrors the surface of the Go and
Node SDKs against the same OpenAPI contract
(tools/openapi/openapi.yaml).
- Zero runtime dependencies — uses only the Python standard library so the package drops cleanly into Lambda layers, vendored POS firmware, and air-gapped merchant ERPs.
- Sync API with explicit OAuth2 client-credentials handling and automatic token refresh.
- Webhook signature verification with constant-time comparison and the same 5-minute clock-skew window enforced server-side.
Install
pip install linkbridge
Requires Python 3.9 or newer.
Quickstart
from linkbridge import LinkbridgeClient
client = LinkbridgeClient(
base_url="https://api.linkbridge.ng",
client_id="your-client-id",
client_secret="your-client-secret",
scopes=["invoices:write", "invoices:read"],
)
accepted = client.invoices.submit({
"irn": "INV001-SVC01-20260601",
"invoice_kind": "B2B",
# …rest of the canonical NRS payload — see
# packages/schema/invoice.schema.json
})
print(accepted["irn"], accepted["status"])
# Read back, paginate, retry, mutate payment status:
record = client.invoices.get(accepted["irn"])
page = client.invoices.list(limit=20, status="failed")
requeued = client.invoices.transmit(accepted["irn"])
paid = client.invoices.update_status(accepted["irn"],
payment_status="PAID", reference="RCPT-001")
Webhook verification
from linkbridge import verify_webhook, SignatureError
@app.post("/hooks/linkbridge")
def hook(request):
try:
verify_webhook(
secret=os.environ["WEBHOOK_SECRET"].encode(),
body=request.body, # raw bytes off the wire
header=request.headers["X-Linkbridge-Signature"],
)
except SignatureError:
return 401
# …handle the event
Errors
All non-2xx responses raise linkbridge.APIError, which exposes the
HTTP status, the canonical error.code, the human error.message, and
the trace_id so that operators can correlate against server logs.
Versioning
The package follows the same 0.MINOR.PATCH cadence as the API surface
during the beta. Breaking changes will be confined to MINOR bumps until
the API freezes at 1.0.0.
Metadata
Release files for linkbridge 0.4.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| linkbridge-0.4.0.tar.gz | 12.6 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| linkbridge-0.4.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 21.9 kB
Release files / linkbridge-0.4.0.tar.gz
| Download URL | linkbridge-0.4.0.tar.gz |
|---|---|
| Size | 12.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
740f705cb2732ac3e937b8a9cda11eb0a1108c5ab4a742d0939823556df3986c
|
|
BLAKE2b-256 checksum How to use checksums |
96f0cc56eef19a3ed9e512cf695b7978519696bce97b4efd4a1c76a32ff7925c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.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 Jul 20, 2026.
Transparency logRelease files / linkbridge-0.4.0-py3-none-any.whl
| Download URL | linkbridge-0.4.0-py3-none-any.whl |
|---|---|
| Size | 9.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
389f0eec972fb18c9b6a32de5c36a73e894168ea5cbffa6c06ea07341bebe2b8
|
|
BLAKE2b-256 checksum How to use checksums |
7f1702075a83c25e86a5f83a1de9a6475bf2bec7f24529a6bbaa3c17bca56420
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.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 Jul 20, 2026.
Transparency logSecurity for linkbridge 0.4.0
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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for linkbridge-0.4.0.tar.gz
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 Jul 20, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.