Skip to main content

noresponse

Developer-friendly & type-safe Python SDK specifically catered to leverage noresponse API.



Summary

NoResponse API: Server-side signup and gateway risk assessment: a recommendation, polling and signed webhooks.

Assess a signup or gateway event, poll a pending assessment, page through an account's history, record what you later learned, and rotate your API key. Every response carries X-Request-ID; every error is an RFC 9457 problem document. Keep the API key on your server.

Table of Contents

SDK Installation

The SDK can be installed with uv, pip, or poetry package managers.

uv

uv is a fast Python package installer and resolver, designed as a drop-in replacement for pip and pip-tools. It's recommended for its speed and modern Python tooling capabilities.

uv add git+<UNSET>.git

PIP

PIP is the default package installer for Python, enabling easy installation and management of packages from PyPI via the command line.

pip install git+<UNSET>.git

Poetry

Poetry is a modern tool that simplifies dependency management and package publishing by using a single pyproject.toml file to handle project metadata and dependencies.

poetry add git+<UNSET>.git

Shell and script usage with uv

You can use this SDK in a Python shell with uv and the uvx command that comes with it like so:

uvx --from noresponse python

It's also possible to write a standalone Python script without needing to set up a whole project like so:

#!/usr/bin/env -S uv run --script
# /// script
# requires-python = ">=3.10"
# dependencies = [
#     "noresponse",
# ]
# ///

from noresponse import NoResponse

sdk = NoResponse(
  # SDK arguments
)

# Rest of script here...

Once that is saved to a file, you can run it with uv run script.py where script.py can be replaced with the actual file name.

IDE Support

PyCharm

Generally, the SDK will work well with most IDEs out of the box. However, when using PyCharm, you can enjoy much better integration with Pydantic by installing an additional plugin.

SDK Example Usage

Example

# Synchronous Example
from noresponse import NoResponse
import os


with NoResponse(
    api_key=os.getenv("NORESPONSE_API_KEY", ""),
) as no_response:

    res = no_response.assessments.create(idempotency_key="<value>", account_id="acct_7f3a9c", identifiers={
        "email": "new.user@example.com",
    })

    # Handle response
    print(res)

The same SDK client can also be used to make asynchronous requests by importing asyncio.

# Asynchronous Example
import asyncio
from noresponse import NoResponse
import os

async def main():

    async with NoResponse(
        api_key=os.getenv("NORESPONSE_API_KEY", ""),
    ) as no_response:

        res = await no_response.assessments.create_async(idempotency_key="<value>", account_id="acct_7f3a9c", identifiers={
            "email": "new.user@example.com",
        })

        # Handle response
        print(res)

asyncio.run(main())

Authentication

Per-Client Security Schemes

This SDK supports the following security scheme globally:

Name Type Scheme Environment Variable
api_key http HTTP Bearer NORESPONSE_API_KEY

To authenticate with the API the api_key parameter must be set when initializing the SDK client instance. For example:

from noresponse import NoResponse
import os


with NoResponse(
    api_key=os.getenv("NORESPONSE_API_KEY", ""),
) as no_response:

    res = no_response.assessments.create(idempotency_key="<value>", account_id="acct_7f3a9c", identifiers={
        "email": "new.user@example.com",
    })

    # Handle response
    print(res)

Available Resources and Operations

Available methods

Assessments

  • create - Assess identifiers for a signup or gateway decision.
  • get - Poll the authoritative assessment of one assessment.
  • record_outcome - Report what was later learned about an assessed account.
  • query - Page through one account's unexpired assessments.

Keys

  • rotate - Rotate the API key that signs the request.

Pagination

Some of the endpoints in this SDK support pagination. To use pagination, you make your SDK calls as usual, but the returned response object will have a Next method that can be called to pull down the next group of results. If the return value of Next is None, then there are no more pages to be fetched.

Here's an example of one such pagination call:

from noresponse import NoResponse
import os


with NoResponse(
    api_key=os.getenv("NORESPONSE_API_KEY", ""),
) as no_response:

    res = no_response.assessments.query(account_id="acct_7f3a9c", limit=20)

    while res is not None:
        # Handle items

        res = res.next()

Retries

Some of the endpoints in this SDK support retries. If you use the SDK without any configuration, it will fall back to the default retry strategy provided by the API. However, the default retry strategy can be overridden on a per-operation basis, or across the entire SDK.

To change the default retry strategy for a single API call, simply provide a RetryConfig object to the call:

from noresponse import NoResponse
from noresponse.utils import BackoffStrategy, RetryConfig
import os


with NoResponse(
    api_key=os.getenv("NORESPONSE_API_KEY", ""),
) as no_response:

    res = no_response.assessments.create(idempotency_key="<value>", account_id="acct_7f3a9c", identifiers={
        "email": "new.user@example.com",
    },
        RetryConfig("backoff", BackoffStrategy(1, 50, 1.1, 100), False))

    # Handle response
    print(res)

If you'd like to override the default retry strategy for all operations that support retries, you can use the retry_config optional parameter when initializing the SDK:

from noresponse import NoResponse
from noresponse.utils import BackoffStrategy, RetryConfig
import os


with NoResponse(
    retry_config=RetryConfig("backoff", BackoffStrategy(1, 50, 1.1, 100), False),
    api_key=os.getenv("NORESPONSE_API_KEY", ""),
) as no_response:

    res = no_response.assessments.create(idempotency_key="<value>", account_id="acct_7f3a9c", identifiers={
        "email": "new.user@example.com",
    })

    # Handle response
    print(res)

Error Handling

APIError is the base class for all HTTP error responses. It has the following properties:

Property Type Description
err.message str Error message
err.status_code int HTTP response status code eg 404
err.headers httpx.Headers HTTP response headers
err.body str HTTP body. Can be empty string if no body is returned.
err.raw_response httpx.Response Raw HTTP response
err.data Optional. Some errors may contain structured data. See Error Classes.

Example

from noresponse import NoResponse, models
import os
from typing import Literal


with NoResponse(
    api_key=os.getenv("NORESPONSE_API_KEY", ""),
) as no_response:
    res = None
    try:

        res = no_response.assessments.create(idempotency_key="<value>", account_id="acct_7f3a9c", identifiers={
            "email": "new.user@example.com",
        })

        # Handle response
        print(res)


    except models.errors.APIError as e:
        # The base class for HTTP error responses
        print(e.message)
        print(e.status_code)
        print(e.body)
        print(e.headers)
        print(e.raw_response)

        # Depending on the method different errors may be thrown
        if isinstance(e, models.errors.BadRequestError):
            print(e.data.type)  # str
            print(e.data.title)  # str
            print(e.data.status)  # Literal[400]
            print(e.data.detail)  # str
            print(e.data.instance)  # Optional[str]

Error Classes

Primary errors:

Less common errors (5)

Network errors:

Inherit from APIError:

  • ResponseValidationError: Type mismatch between the response data and the expected Pydantic model. Provides access to the Pydantic validation error via the cause attribute.

Server Selection

Override Server URL Per-Client

The default server can be overridden globally by passing a URL to the server_url: str optional parameter when initializing the SDK client instance. For example:

from noresponse import NoResponse
import os


with NoResponse(
    server_url="https://api.noresponse.org",
    api_key=os.getenv("NORESPONSE_API_KEY", ""),
) as no_response:

    res = no_response.assessments.create(idempotency_key="<value>", account_id="acct_7f3a9c", identifiers={
        "email": "new.user@example.com",
    })

    # Handle response
    print(res)

Custom HTTP Client

The Python SDK makes API calls using the httpx HTTP library. In order to provide a convenient way to configure timeouts, cookies, proxies, custom headers, and other low-level configuration, you can initialize the SDK client with your own HTTP client instance. Depending on whether you are using the sync or async version of the SDK, you can pass an instance of HttpClient or AsyncHttpClient respectively, which are Protocol's ensuring that the client has the necessary methods to make API calls. This allows you to wrap the client with your own custom logic, such as adding custom headers, logging, or error handling, or you can just pass an instance of httpx.Client or httpx.AsyncClient directly.

For example, you could specify a header for every request that this sdk makes as follows:

from noresponse import NoResponse
import httpx

http_client = httpx.Client(headers={"x-custom-header": "someValue"})
s = NoResponse(client=http_client)

or you could wrap the client with your own custom logic:

from noresponse import NoResponse
from noresponse.httpclient import AsyncHttpClient
import httpx

class CustomClient(AsyncHttpClient):
    client: AsyncHttpClient

    def __init__(self, client: AsyncHttpClient):
        self.client = client

    async def send(
        self,
        request: httpx.Request,
        *,
        stream: bool = False,
        auth: Union[
            httpx._types.AuthTypes, httpx._client.UseClientDefault, None
        ] = httpx.USE_CLIENT_DEFAULT,
        follow_redirects: Union[
            bool, httpx._client.UseClientDefault
        ] = httpx.USE_CLIENT_DEFAULT,
    ) -> httpx.Response:
        request.headers["Client-Level-Header"] = "added by client"

        return await self.client.send(
            request, stream=stream, auth=auth, follow_redirects=follow_redirects
        )

    def build_request(
        self,
        method: str,
        url: httpx._types.URLTypes,
        *,
        content: Optional[httpx._types.RequestContent] = None,
        data: Optional[httpx._types.RequestData] = None,
        files: Optional[httpx._types.RequestFiles] = None,
        json: Optional[Any] = None,
        params: Optional[httpx._types.QueryParamTypes] = None,
        headers: Optional[httpx._types.HeaderTypes] = None,
        cookies: Optional[httpx._types.CookieTypes] = None,
        timeout: Union[
            httpx._types.TimeoutTypes, httpx._client.UseClientDefault
        ] = httpx.USE_CLIENT_DEFAULT,
        extensions: Optional[httpx._types.RequestExtensions] = None,
    ) -> httpx.Request:
        return self.client.build_request(
            method,
            url,
            content=content,
            data=data,
            files=files,
            json=json,
            params=params,
            headers=headers,
            cookies=cookies,
            timeout=timeout,
            extensions=extensions,
        )

s = NoResponse(async_client=CustomClient(httpx.AsyncClient()))

httpx2 (Pydantic's httpx fork)

httpx2 is Pydantic's maintained fork of httpx. To run this SDK on httpx2, call alias_httpx() at your program's entry point, before importing the SDK, so every import httpx — including the ones inside the SDK — resolves to httpx2:

import httpx2

httpx2.alias_httpx()

from noresponse import NoResponse

s = NoResponse()

An SDK can also be generated against httpx2 directly, so it depends on the fork instead of httpx, by setting python.httpClientLibrary: httpx2 in gen.yaml.

Resource Management

The NoResponse class implements the context manager protocol and registers a finalizer function to close the underlying sync and async HTTPX clients it uses under the hood. This will close HTTP connections, release memory and free up other resources held by the SDK. In short-lived Python programs and notebooks that make a few SDK method calls, resource management may not be a concern. However, in longer-lived programs, it is beneficial to create a single SDK instance via a context manager and reuse it across the application.

from noresponse import NoResponse
import os
def main():

    with NoResponse(
        api_key=os.getenv("NORESPONSE_API_KEY", ""),
    ) as no_response:
        # Rest of application here...


# Or when using async:
async def amain():

    async with NoResponse(
        api_key=os.getenv("NORESPONSE_API_KEY", ""),
    ) as no_response:
        # Rest of application here...

Debugging

You can setup your SDK to emit debug logs for SDK requests and responses.

You can pass your own logger class directly into your SDK.

from noresponse import NoResponse
import logging

logging.basicConfig(level=logging.DEBUG)
s = NoResponse(debug_logger=logging.getLogger("noresponse"))

You can also enable a default debug logger by setting an environment variable NORESPONSE_DEBUG to true.

Development

Maturity

This SDK is in beta, and there may be breaking changes between versions without a major version update. Therefore, we recommend pinning usage to a specific package version. This way, you can install the same version each time without breaking changes unless you are intentionally looking for the latest version.

Contributions

While we value open-source contributions to this SDK, this library is generated programmatically. Any manual changes added to internal files will be overwritten on the next generation. We look forward to hearing your feedback. Feel free to open a PR or an issue with a proof of concept and we'll do our best to include it in a future release.

Metadata

Release files for noresponse 2.0.3

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

Source distribution (sdist)

Source distribution for noresponse 2.0.3
File Size Uploaded Provenance
noresponse-2.0.3.tar.gz 94.2 kB Without provenance Details

Built distribution (wheel)

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

Total release size: 230.7 kB

Release files / noresponse-2.0.3.tar.gz

Download URL noresponse-2.0.3.tar.gz
Size 94.2 kB
Tags Source
SHA-256 checksum
How to use checksums
3853c88f2697084781e9556e4a2a70b23d6ba64b8f050e013fd69bd3eb2468ad
BLAKE2b-256 checksum
How to use checksums
27025de34aea5abf816419d0ff40d5c6b42bc7c75d8ada2e93530ec7aeee205a
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Release files / noresponse-2.0.3-py3-none-any.whl

Download URL noresponse-2.0.3-py3-none-any.whl
Size 136.5 kB
Tags Python 3
SHA-256 checksum
How to use checksums
e886e6cfe3ae2d8005cbffbcb5e510235738d19da3a69c6631a7e42ab541c2e5
BLAKE2b-256 checksum
How to use checksums
7675ccc6743d794e28452c38f608ae20016672687080c73d7ec450b383d4ad61
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Security for noresponse 2.0.3

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.

No provenance found

None of the files in this release were uploaded with provenance metadata.

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.

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