Skip to main content

Build Status PyPI

coderpad-py

Python library for the CoderPad Interview API.

Installation

pip install coderpad-py

This is tested on Python 3.12+.

Getting Started

"""Example usage."""

import sys

from coderpad.client import CoderPad

client = CoderPad(api_key="your-api-key")
pad = client.pads.create(title="Interview", language="python")
_ = sys.stdout.write(pad.title)
for listed_pad in client.pads.list():
    _ = sys.stdout.write(listed_pad.title)
org = client.organization.get()
_ = sys.stdout.write(org.organization_name)
for user in client.organization.users.list():
    _ = sys.stdout.write(user.email)

The organization users endpoint also supports server-side email filtering:

"""Filter organization users by email."""

from coderpad.client import CoderPad

client = CoderPad(api_key="your-api-key")
users = client.organization.users.list(email="person@example.com")

The equivalent asynchronous operation is await client.organization.users.list(email="person@example.com").

HTTPX2 transports

HTTPX remains the default client family. To opt in to HTTPX2, construct the HTTPX2 transport explicitly and pass it to the client. The standard coderpad-py installation includes both client families.

"""Configure CoderPad to use HTTPX2."""

import sys

import httpx2

from coderpad.client import CoderPad
from coderpad.transports import HTTPX2Transport

transport = HTTPX2Transport(timeout=httpx2.Timeout(timeout=10))
with CoderPad(api_key="your-api-key", transport=transport) as client:
    _ = sys.stdout.write(client.base_url)

Use AsyncHTTPX2Transport with AsyncCoderPad for asynchronous calls. The limits, proxy and timeout arguments passed to these transports accept HTTPX2 configuration objects. Do not pass equivalent httpx objects across the package boundary. If the Screen API should also use HTTPX2, pass a separate HTTPX2 transport as screen_transport.

Existing HTTPX users do not need to change anything. Migrating to HTTPX2 only requires selecting the new transport. The CoderPad client methods and returned models are unchanged.

CoderPad Screen

Screen uses a separate API key and host from Interview:

"""List Screen campaigns and candidate tests."""

from coderpad import CoderPad

client = CoderPad(
    api_key="your-interview-api-key",
    screen_api_key="your-screen-api-key",
)
campaigns = client.screen.campaigns.list()
page = client.screen.tests.list(campaign_id=campaigns[0].id, limit=50)
assert page.pagination is not None

Screen test listings use offset pagination. While page.pagination.has_more_items is true, request the next page with start=page.pagination.next_start. Use SCREEN_EU_BASE_URL as screen_base_url for EU-hosted organizations. All Screen operations have equivalent methods on AsyncCoderPad.

Environment variables

Set CODERPAD_API_KEY for the Interview API. Optionally set CODERPAD_SCREEN_API_KEY for Screen. Then construct a client with CoderPad.from_env() or AsyncCoderPad.from_env():

"""Load API keys from the environment."""

import sys

from coderpad.client import CoderPad

client = CoderPad.from_env()
_ = sys.stdout.write(client.base_url)

Full Documentation

See the full documentation.

Environment discovery

Use client.languages.list() to discover available environments and client.languages.get(language="multifile_python") to retrieve starter code and environment context before authoring a project. Both methods return the complete catalog JSON and are also available on AsyncCoderPad.

Create a project pad with client.pads.create(language="multifile_python"). Pass file_contents using QuestionFileContent overlays, or pass a zip_file or directory path to replace the template files. A question ID and starter content are mutually exclusive. Project pad responses can have null language and contents. Retrieve files through client.pads.get_environment(environment_id=...) using the pad’s environment IDs.

Metadata

Release files for coderpad-py 2026.11.11.1

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

Source distribution (sdist)

Source distribution for coderpad-py 2026.11.11.1
File Size Uploaded Provenance Actions
coderpad_py-2026.11.11.1.tar.gz 155.2 kB With provenance Details for coderpad_py-2026.11.11.1.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for coderpad-py 2026.11.11.1
File Interpreter ABI Platform Actions
coderpad_py-2026.11.11.1-py3-none-any.whl Python 3 none any Details for coderpad_py-2026.11.11.1-py3-none-any.whl

Total release size: 222.3 kB

Release files / coderpad_py-2026.11.11.1.tar.gz

Download URL coderpad_py-2026.11.11.1.tar.gz
Size 155.2 kB
Tags Source
SHA-256 checksum
How to use checksums
cfce246289f2fa74a0a2dbdae3a98992b26af479a6c1e917e0649b85dd853319
BLAKE2b-256 checksum
How to use checksums
2b501a36cf1476e0f1a2dd11645c349b578982a2e20cb4f5c7c3ecc69e65ecae
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 Nov 11, 2026.

Transparency log

Release files / coderpad_py-2026.11.11.1-py3-none-any.whl

Download URL coderpad_py-2026.11.11.1-py3-none-any.whl
Size 67.1 kB
Tags Python 3
SHA-256 checksum
How to use checksums
7efb7c986c32abc717729b46d9f8741449982fd4ede194b321c580c76721bbb7
BLAKE2b-256 checksum
How to use checksums
3ac94eecf85bb56690d9b1939c0b8d3919e152cc0f06f999caa100800f34e667
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 Nov 11, 2026.

Transparency log

Security for coderpad-py 2026.11.11.1

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

Both files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for coderpad_py-2026.11.11.1.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 Nov 11, 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