Developer documentationSDKs
Once Email SDKs
Open-source SDK candidates for the Once Email receive-only API, with tested downloads for seven ecosystems.
7 Once Email SDKs
Use one reviewed OpenAPI contract from TypeScript, Python, Java, Go, .NET, PHP, or Ruby. Source, reference documentation, versions, and local-download archives are public.
TypeScript
npm ci && npm run buildpython -m pip install .mvn clean installgo mod edit -replace github.com/pangxin12345/once-email-sdks/sdks/go=./once-email-go-sdk-0.1.0-private.2dotnet build OnceEmail.Sdk.slncomposer installbundle install && gem build once_email.gemspecNative CI has passed on Linux, macOS, and Windows. TypeScript and Python include automated tests; Java, Go, .NET, PHP, and Ruby pass their available native build or syntax gates.
The official Go module proxy still lists the older v0.1.0-private.1 prerelease module; the current Go SDK candidate is the versioned archive on this page. There are no formal npm, PyPI, Maven Central, NuGet, Packagist, or RubyGems releases. Public API Key creation and live calls remain closed. Verify SHA256SUMS for the current archive.
Use the language already owned by your test service. Do not add a second runtime only for mailbox polling; the seven clients share the same receive-only contract.
Download one immutable archive, compare its SHA-256 value with SHA256SUMS, read its bundled README and pin the version in your project.
Create one inbox per authorized test, poll within one deadline, treat 429/503 separately, avoid logging messages or codes, and always delete the inbox in finally.
SDK Demo
Download code, docs, and demo together
Versioned archives include source, documentation, safety boundaries, and checksums.
Complete usage guide
Choose your SDK
Use only an application you own or are explicitly authorized to test. Once Email receives mail only; it does not send mail or automate third-party registrations.
Open SHA256SUMS before extracting the file.
Exact local starting point
Use the local build/install command in the README for the current 0.1.0-private.2 archive; the older Go Proxy module is a separate prerelease.
From download to a clean first run
- Choose the language already used by the authorized test service.
- Download that language archive and verify its SHA-256 before extracting it.
- Confirm SDK 0.1.0-private.2, API contract 0.5.0-private-beta, runtime, license, and prerelease status.
- Use the local build/install command in the README for the current 0.1.0-private.2 archive; the older Go Proxy module is a separate prerelease.
- Proceed only with explicitly authorized API access and already issued, valid credentials with the minimum necessary permissions. Store them in a process secret facility; without this access, stop at reviewing the documentation and downloads. Inject the API key through a process secret facility; create, list, read, and handle errors within one deadline.
- Delete in finally on success or failure and never print addresses, messages, codes, links, or keys.
Failure and recovery
Keep 400, 401, 403, 404, 413, 429, and 503 distinct. Timeout, ambiguity, extraction, assertion, and cleanup are also different failures. Retry only within one deadline and never turn a dependency failure into an empty inbox.