Insitive SDK downloads

TypeScript / JavaScript

@insitive/api 0.4.2

Install the release tarball straight from this host:

npm install https://insitive-api-production.up.railway.app/api/developers/sdk/files/insitive-api-0.4.2.tgz
# or
bun add https://insitive-api-production.up.railway.app/api/developers/sdk/files/insitive-api-0.4.2.tgz

Verify the download against the SHA-256 published below before you install it in an automated environment — npm does not check the hash for a tarball URL:

curl -sL https://insitive-api-production.up.railway.app/api/developers/sdk/files/insitive-api-0.4.2.tgz | shasum -a 256

Earlier releases are also on the public npm registry as @insitive/api; this host is the channel that always carries the current release.

Python

insitive-api 0.4.0

Recommended — install the artifact by URL. insitive-api is not registered on PyPI, so naming a URL resolves no package name against any public index, and the #sha256= fragment makes pip verify the bytes it downloaded:

pip install https://insitive-api-production.up.railway.app/api/developers/sdk/files/insitive_api-0.4.0-py3-none-any.whl#sha256=0642b42ad03e1e639594c982531fd37b2664e7e08bd898353ddabfa96f678916

With uv:

uv pip install https://insitive-api-production.up.railway.app/api/developers/sdk/files/insitive_api-0.4.0-py3-none-any.whl#sha256=0642b42ad03e1e639594c982531fd37b2664e7e08bd898353ddabfa96f678916

In requirements.txt:

insitive-api @ https://insitive-api-production.up.railway.app/api/developers/sdk/files/insitive_api-0.4.0-py3-none-any.whl#sha256=0642b42ad03e1e639594c982531fd37b2664e7e08bd898353ddabfa96f678916

Installing by name from our PEP 503 index also works, but pip merges candidates from every configured index, so a package published to PyPI under this name could win resolution. Pin the exact version if you use it:

pip install --extra-index-url https://insitive-api-production.up.railway.app/api/developers/sdk/simple/ insitive-api==0.4.0

Verifying a download

Every artifact's SHA-256 is listed above. For Python, the hash travels in the #sha256= fragment of the install URL and the index links, so pip verifies the download itself. npm has no equivalent for a tarball URL, so check the TypeScript tarball by hand:

shasum -a 256 <file>