Skip to main content

Downloads

Nuntiq Connector Toolkit​

The toolkit is a self-contained Python sandbox for writing and testing connectors on your own machine. Everything runs against in-memory dummy data backed by JSON files — no Nuntiq account, no network, no AWS.

nuntiq-connector-toolkit-0.2.0.zip

v0.2.0 · ~106 KB · Python 3.10+

Download zip

SHA-256: 2fd984fe594b9a3454f8b85658ebae477b0b969b0a1d6ccd6f5eb31fb7f1505c

Verify after download:

(Get-FileHash nuntiq-connector-toolkit-0.2.0.zip -Algorithm SHA256).Hash.ToLower()

What's inside​

nuntiq-connector-toolkit-0.2.0/
├── nuntiq.py                <- entrypoint you run
├── settings.example.json    <- template, copy to settings.json
├── requirements.txt
├── connectors/              <- 6 example entrypoints + your code
├── fixtures/                <- dummy data tables (JSON, edit freely)
├── docs/                    <- SDK reference (also on this site)
├── lib/                     <- the SDK you import
└── _toolkit/                <- sandbox internals (you can ignore)

See Toolkit overview for what each folder does.

Quick start​

  1. Unzip somewhere convenient.
  2. python -m venv .venv && .\.venv\Scripts\activate (Windows) or source .venv/bin/activate (macOS/Linux).
  3. pip install -r requirements.txt.
  4. cp settings.example.json settings.json and edit it.
  5. python nuntiq.py.

Full walkthrough: Installation → Your first connector.

Changelog​

0.2.0 — 2026-05-16​

  • Renamed from ap-receiving-connector-sandbox → nuntiq-connector-toolkit to match the platform rebrand.
  • Bundled with the Nuntiq developer portal.

0.1.0 — 2026-04-25​

  • Initial release. Six example connectors covering the four most common shapes (pull with delta, push with claim/ack/result, lifecycle poll, read-only export).

Stay current​

Toolkit releases are versioned alongside the production framework. Major behavioural changes get a major-version bump; SDK additions are minor. Anything you've written against an older toolkit should run unchanged on the next minor version — file an issue if it doesn't.

The framework itself ships on a separate cadence maintained by Nuntiq. Both share the SDK in lib/ byte-for-byte, so anything that imports cleanly in your toolkit will import cleanly in production at the version you tested against.