Thanks for taking the time to look at the source. This SDK is a thin wrapper around the Ready APIs HTTP surface - most issues are best filed against the upstream platform, but a few belong here.
- The Python client (
src/readyapis/) - Type stubs /
__init__.pyre-exports - Tests under
tests/ - GitHub Actions for test + PyPI publish (trusted-publisher OIDC)
- API behavior, endpoint accuracy, rate limits, billing - see readyapis.com/docs
- Dataset corrections (e.g. "this ZIP code is wrong") - email
support@readyapis.comwith the source you have in mind
Good issue includes:
- Python version (
python --version) readyapisversion (pip show readyapis | grep Version)- Minimal repro - the smallest code that triggers the problem, with secrets redacted
- What you expected, what happened
If the SDK call returned an error from the server, include the full error object - that helps tell SDK bugs from API bugs.
For non-trivial changes, open an issue first so we can discuss the shape. For typo fixes / docstring improvements, just send the PR.
git clone https://github.com/ReadyAPIs-com/readyapis-python.git
cd readyapis-python
python -m venv .venv && source .venv/bin/activate
pip install -e ".[dev]"
pytestPRs need:
- Passing CI (test + lint)
- A test covering the change (mock the HTTP layer; we don't hit prod in CI)
- A line in
CHANGELOG.mdunder "Unreleased"
Don't open public issues for security problems. Email support@readyapis.com directly. We try to acknowledge within one business day.
By contributing you agree your work is licensed under MIT (the project's license).