noxhere
The unified Python client for every NoxHere resource. Its complete operation
catalog is generated from the same OpenAPI contract as @noxhere/sdk.
from noxhere import NoxHereClient
nox = NoxHereClient(token="nox_sk_...")
projects = nox.workspace.list_projects()
incidents = nox.incidents.get_project_incidents(path={"projectId": "project-1"})
The SDK is optional. The equivalent operation can always be called directly:
import os
import requests
response = requests.get(
f"https://app.noxhere.com/api/v1/projects/{project_id}/incidents",
headers={"Authorization": f"Bearer {os.environ['NOXHERE_API_TOKEN']}"},
timeout=10,
)
response.raise_for_status()
incidents = response.json()
See the repository's direct HTTP guide and the OpenAPI-generated operation examples in the developer reference.
Every path, query, body, and response model is generated from NoxHere's
OpenAPI contract and is available through noxhere.models. Async applications
use the same generated resources:
from noxhere import AsyncNoxHereClient
nox = AsyncNoxHereClient(token="nox_sk_...")
page = await nox.activity.get_nox_feed(query={"limit": 25})
Namespaces are workspace, activity, planning, feedback, and
incidents; connect, feed, ticket, spot, and cue are compatibility
aliases. Use noxhere.incidents.create_incident_client or
noxhere.feedback.create_feedback_client for focused clients.
Server telemetry is available from the same distribution:
import os
from noxhere.telemetry import NoxCueClient
with NoxCueClient(
key=os.environ["NOXHERE_TELEMETRY_KEY"],
identity_hash_key=os.environ["NOXHERE_IDENTITY_HASH_KEY"],
environment="production",
) as telemetry:
telemetry.track("user.registered", user_id="user-42")
telemetry.track("records.parsed", user_id="user-42", value=3)
track() queues delivery and returns immediately; leaving the context flushes
the queue. Identifiers are HMAC-SHA256 protected before JSON serialization and
the original value is never transmitted. Keep the identity key stable—changing
it resets user continuity. Compatibility helpers such as user.registered()
and activity() delegate to the same contract.
noxcue remains available as a deprecated forwarding package for existing
applications; new code should import noxhere.telemetry.
noxhere.events.create_platform_event builds the same common event envelope
as the TypeScript SDK. Versions, size limits, privacy keys, and the registered
event-type catalog are generated from the canonical platform event contract,
so contract changes make the SDK drift check fail until both languages are
regenerated.
Metadata
Release files for noxhere 0.2.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| noxhere-0.2.1.tar.gz | 39.6 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| noxhere-0.2.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 75.6 kB
Release files / noxhere-0.2.1.tar.gz
| Download URL | noxhere-0.2.1.tar.gz |
|---|---|
| Size | 39.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d597650bda0c709444c24e746c9ef18019a0688589cda0f42ad324f597370811
|
|
BLAKE2b-256 checksum How to use checksums |
f6c62ec5c22d6ad28abeaf0d40f590d28ed79fcf37a21601e9ecb2594227257e
|
| 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 8, 2026.
Transparency logRelease files / noxhere-0.2.1-py3-none-any.whl
| Download URL | noxhere-0.2.1-py3-none-any.whl |
|---|---|
| Size | 35.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
fce4c2b60a0e95c16dca013d00b59ce22e2cb7d45bf1878ba0504c12fb61ae02
|
|
BLAKE2b-256 checksum How to use checksums |
da376dee2c31e9a4afa536d91847aecf4bbc51e482e6af704161caae80c0fd96
|
| 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 8, 2026.
Transparency log