Skip to main content

noxhere

The unified Python client for every NoxHere resource. Its complete operation catalog is generated from the same OpenAPI contract as @noxhere/sdk.

Install the official distribution from PyPI:

python -m pip install --upgrade noxhere
from noxhere import NoxHereClient

nox = NoxHereClient(token="nox_sk_...")
services = nox.workspace.list_nox_services()

The SDK is optional. The equivalent operation can always be called directly:

import os
import requests

response = requests.get(
    "https://app.noxhere.com/api/v1/services",
    headers={"Authorization": f"Bearer {os.environ['NOXHERE_API_TOKEN']}"},
    timeout=10,
)
response.raise_for_status()
services = 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_activity(query={"limit": 25})

Namespaces are workspace, activity, planning, feedback, stats, and incidents. These unified namespaces are the only supported resource names. Use noxhere.stats.create_stats_client, 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 create_telemetry

with create_telemetry() as telemetry:
    telemetry.user.registered("user-42")
    telemetry.events.record_parsed("user-42", "record-7")

create_telemetry() reads NOXHERE_API_TOKEN (preferred) or the legacy NOXHERE_INGEST_KEY, plus NOXHERE_SOURCE_ID, NOXHERE_IDENTITY_HASH_KEY, NOXHERE_IDENTITY_KEY_ID, NOXHERE_ENVIRONMENT, and NOXHERE_RELEASE. track() queues delivery and returns immediately; process shutdown or leaving the context flushes the queue. Delivery failures are returned or retained for flush() and never raised into the host application. Set NOXHERE_TELEMETRY_MODE=memory in tests, then inspect telemetry.captured_events without making network calls. 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. The typed events helpers keep built-in event names out of application strings while event timing remains an explicit decision at the call site.

telemetry 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.6

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

Source distribution (sdist)

Source distribution for noxhere 0.2.6
File Size Uploaded
noxhere-0.2.6.tar.gz 42.6 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for noxhere 0.2.6
File Interpreter ABI Platform
noxhere-0.2.6-py3-none-any.whl Python 3 none any Details

Total release size: 81.5 kB

Release files / noxhere-0.2.6.tar.gz

Download URL noxhere-0.2.6.tar.gz
Size 42.6 kB
Tags Source
SHA-256 checksum
How to use checksums
4ea35ba57fcd9aa81dc4935a4e27d940a6e30d0dfc68467ffd1eb942f898bd6d
BLAKE2b-256 checksum
How to use checksums
59b5f693d942c65349590b631d71ec9fb5337924b78cd1f3f99b7ae3c958c06f
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 15, 2026.

Transparency log

Release files / noxhere-0.2.6-py3-none-any.whl

Download URL noxhere-0.2.6-py3-none-any.whl
Size 38.9 kB
Tags Python 3
SHA-256 checksum
How to use checksums
bc4500eebfbbb9bdd7b0cc1d15e3f3267814695220d2b583a10f88eea7870317
BLAKE2b-256 checksum
How to use checksums
fe335558fd35a4f92ce6ebd5275b1f97d8276dc2c0e111390b81430ddf7ede40
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 15, 2026.

Transparency log

Release history Release notifications | RSS feed

This release

0.2.6 This release

2 release files

0.2.5

2 release files

0.2.4

2 release files

0.2.3

2 release files

0.2.2

2 release files

0.2.1

2 release files

0.2.0

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