Skip to main content

forward-sdk

Python SDK for the Forward Networks REST API.

A Forward Networks Field Integration. Built and maintained by the field team to make integration work easier. It is not a supported Forward Networks product: it carries no SLA, and issues are handled on a best-effort basis rather than through Forward Support.

Status: pre-release. The public API is not yet stable.

pip install forward-sdk
from forward_sdk import ForwardClient

with ForwardClient.from_env() as client:
    for network in client.networks.list():
        print(network.id, network.name)

    rows = client.nqe.query(
        "foreach device in network.devices select {name: device.name}",
        network_id="101",
    )

Authentication is HTTP basic with an API token: its access key is the username and its secret is the password.

What it covers

Every operation in Forward's API. The groups integrations use most -- NQE, snapshots, networks, devices and device tags -- are hand-written with curated names and behaviour such as waiting for a snapshot to finish processing. The rest are generated from the OpenAPI description Forward produces from its own server code.

Both a synchronous and an asynchronous client, with identical surfaces.

Notable

NQE first. Running a query, paging or streaming the results, diffing a query across snapshots, and publishing queries to the library are all first-class. Paging carries guard rails for the ways it can go wrong in production: a result set that ends early, a server that stops advancing, a query far larger than expected.

Typed, but tolerant. Responses are pydantic models. Unknown fields and unknown enum values are preserved rather than rejected, so a Forward release that adds either does not break an older SDK. NQE rows stay dict[str, Any], because a query's columns are defined by the query.

Honest about refusals. A missing licence, a feature absent from your deployment, and a role-based denial all arrive as the same status codes, so the SDK does not pretend to tell them apart. It gives you Forward's own explanation and a documented hint about what gates that operation.

Documentation

https://forwardnetworks.github.io/forward-python-sdk/

Requirements

Python 3.10 or newer.

Licence

MIT.

Metadata

Release files for forward-sdk 0.1.28

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

Source distribution (sdist)

Source distribution for forward-sdk 0.1.28
File Size Uploaded Provenance Actions
forward_sdk-0.1.28.tar.gz 1.1 MB With provenance Details for forward_sdk-0.1.28.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for forward-sdk 0.1.28
File Interpreter ABI Platform Actions
forward_sdk-0.1.28-py3-none-any.whl Python 3 none any Details for forward_sdk-0.1.28-py3-none-any.whl

Total release size: 1.7 MB

Release files / forward_sdk-0.1.28.tar.gz

Download URL forward_sdk-0.1.28.tar.gz
Size 1.1 MB
Tags Source
SHA-256 checksum
How to use checksums
4770b51dd7809b0caeebf56e9962f871d3e2e4185e5ae7264f6c72c9ec850df2
BLAKE2b-256 checksum
How to use checksums
617e86ef9fccddf0b2a7becfcb088cc280cb1649a0fc239875d76a5516b3236a
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Oct 28, 2026.

Transparency log

Release files / forward_sdk-0.1.28-py3-none-any.whl

Download URL forward_sdk-0.1.28-py3-none-any.whl
Size 562.8 kB
Tags Python 3
SHA-256 checksum
How to use checksums
b09f37a6d0c907ccc5744c758073486dea5ba4d20a64d07029d321655d5a5fd1
BLAKE2b-256 checksum
How to use checksums
81bba243e47300401dfd114057d83da36259984b38d782ca7574f51d0a8decb1
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Oct 28, 2026.

Transparency log

Security for forward-sdk 0.1.28

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.

Select from 2 files

Attestation for forward_sdk-0.1.28.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 Oct 28, 2026.

Transparency log

A 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.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

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