Skip to main content

alter-sdk-rippling

Install pip install alter-sdk-rippling. Core alter-sdk is installed as a dependency.

Import RipplingIntegration from alter_sdk_rippling and construct it with an Alter App and {"grant_id": grant_id}. All 480 operations use immutable contract 2026-10-28. Await call.wait() for immediate or approved execution, then decode with result.body_json(). OAuth and managed-secret/API-key grants use the same binding and controls when the provider supports that credential type.

Public API reference includes every operation's input/output fields and both SDK examples.

Resume after a process restart

Persist the pending call's approvalId (TypeScript) or approval_id (Python) in your durable job record. After restarting, construct a fresh provider client:

const resumed = await provider.resume(savedApprovalId);
const result = await resumed.wait();
const body = result.bodyJson();
resumed = await provider.resume(saved_approval_id)
result = await resumed.wait()
body = result.body_json()

The backend supplies the stored provider, operation and immutable contract version. The provider package verifies provider/version and applies that operation's validator and fault handling. Mismatches raise ManagedOperationError with managed_approval_contract_mismatch or managed_approval_operation_mismatch. The ID yields a union of operation outputs; TypeScript callers can narrow the call by resumed.operation. No operation or version is accepted from the caller.

Generic app.integrations.resume(id) preserves raw response access and exact-number decoding; use the provider package for its response validator. Both use the existing approval poll's proxy:execute or approvals:read permissions and app/agent isolation. Resume also works after execution while the result is retained. Denial, expiry, execution failure and result purging retain the existing approval errors. Resume never resubmits the request. Raw approvals or missing stored identities fail with managed_approval_identity_unavailable.

Metadata

Release files for alter-sdk-rippling 0.4.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 alter-sdk-rippling 0.4.1
File Size Uploaded Provenance Actions
alter_sdk_rippling-0.4.1.tar.gz 389.6 kB With provenance Details for alter_sdk_rippling-0.4.1.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for alter-sdk-rippling 0.4.1
File Interpreter ABI Platform Actions
alter_sdk_rippling-0.4.1-py3-none-any.whl Python 3 none any Details for alter_sdk_rippling-0.4.1-py3-none-any.whl

Total release size: 815.2 kB

Release files / alter_sdk_rippling-0.4.1.tar.gz

Download URL alter_sdk_rippling-0.4.1.tar.gz
Size 389.6 kB
Tags Source
SHA-256 checksum
How to use checksums
7d557e5d8f4bb1e0589df0c9bc1d726a1b3c3621bad6afbeb194354e64b23f5e
BLAKE2b-256 checksum
How to use checksums
25ca83f679f996b117798e9c85ba27c3ba7fa874675bc49bba3eb3c1397fe127
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 3, 2026.

Transparency log

Release files / alter_sdk_rippling-0.4.1-py3-none-any.whl

Download URL alter_sdk_rippling-0.4.1-py3-none-any.whl
Size 425.6 kB
Tags Python 3
SHA-256 checksum
How to use checksums
2e1a76de6b9c784169d9cc13bf7fb0f0dd0c7edc685dda4f1ff1ca600d8ecb73
BLAKE2b-256 checksum
How to use checksums
11cdb3c761fed242b5008c284534a5e3e16fa49fa968bed0d83cbf34ae0175de
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 3, 2026.

Transparency log

Security for alter-sdk-rippling 0.4.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 alter_sdk_rippling-0.4.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 3, 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