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

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.21
File Size Uploaded
forward_sdk-0.1.21.tar.gz 744.0 kB Details

Built distribution (wheel)

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

Total release size: 1.1 MB

Release files / forward_sdk-0.1.21.tar.gz

Download URL forward_sdk-0.1.21.tar.gz
Size 744.0 kB
Tags Source
SHA-256 checksum
How to use checksums
b811fd416720b54f0647385386f94822f38058ad46672eae97133ca42042bf6d
BLAKE2b-256 checksum
How to use checksums
6a7471042578893158d1540297aeae3f8d12b1834938389a60b4ba22dc5c32a5
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 Oct 10, 2026.

Transparency log

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

Download URL forward_sdk-0.1.21-py3-none-any.whl
Size 404.2 kB
Tags Python 3
SHA-256 checksum
How to use checksums
0ee9e756f00d2e817f5c823b0f6ecc938dc6e26bef88c3f1a81cbdfe2622c043
BLAKE2b-256 checksum
How to use checksums
ba1f8bf964c3c26b663e460361ae2d4710825171dfda8ef7e01759ccb1f02de9
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 Oct 10, 2026.

Transparency log

Release history Release notifications | RSS feed

This release

0.1.21 This release

2 release files

0.1.20

2 release files

0.1.19

2 release files

0.1.16

2 release files

0.1.15

2 release files

0.1.14

2 release files

0.1.13

2 release files

0.1.12

2 release files

0.1.11

2 release files

0.1.10

2 release files

0.1.9

2 release files

0.1.8

2 release files

0.1.7

2 release files

0.1.6

2 release files

0.1.5

2 release files

0.1.4

2 release files

0.1.3

2 release files

0.1.2

2 release files

0.1.1

2 release files

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