Skip to main content
Pre-release

This release is a pre-release and may not be stable for production use.

Pinnacle Python Library

pypi

The Pinnacle Python library provides convenient access to the Pinnacle APIs from Python.

Table of Contents

Installation

pip install rcs

Reference

A full reference for this library is available here.

Usage

Instantiate and use the client with the following:

from rcs import Pinnacle
from rcs.brands import AutofillBrandOptions

client = Pinnacle(
    api_key="YOUR_API_KEY",
)
client.brands.autofill(
    additional_info="A developer-friendly, compliant API for SMS, MMS, and RCS, built to scale real conversations.",
    name="Pinnacle",
    options=AutofillBrandOptions(
        force_reload=True,
    ),
    website="https://www.pinnacle.sh",
)

Async Client

The SDK also exports an async client so that you can make non-blocking calls to our API.

import asyncio

from rcs import AsyncPinnacle
from rcs.brands import AutofillBrandOptions

client = AsyncPinnacle(
    api_key="YOUR_API_KEY",
)


async def main() -> None:
    await client.brands.autofill(
        additional_info="A developer-friendly, compliant API for SMS, MMS, and RCS, built to scale real conversations.",
        name="Pinnacle",
        options=AutofillBrandOptions(
            force_reload=True,
        ),
        website="https://www.pinnacle.sh",
    )


asyncio.run(main())

Exception Handling

When the API returns a non-success status code (4xx or 5xx response), a subclass of the following error will be thrown.

from rcs.core.api_error import ApiError

try:
    client.brands.autofill(...)
except ApiError as e:
    print(e.status_code)
    print(e.body)

Advanced

Access Raw Response Data

The SDK provides access to raw response data, including headers, through the .with_raw_response property. The .with_raw_response property returns a "raw" client that can be used to access the .headers and .data attributes.

from rcs import Pinnacle

client = Pinnacle(
    ...,
)
response = client.brands.with_raw_response.autofill(...)
print(response.headers)  # access the response headers
print(response.data)  # access the underlying object

Retries

The SDK is instrumented with automatic retries with exponential backoff. A request will be retried as long as the request is deemed retryable and the number of retry attempts has not grown larger than the configured retry limit (default: 2).

A request is deemed retryable when any of the following HTTP status codes is returned:

  • 408 (Timeout)
  • 429 (Too Many Requests)
  • 5XX (Internal Server Errors)

Use the max_retries request option to configure this behavior.

client.brands.autofill(..., request_options={
    "max_retries": 1
})

Timeouts

The SDK defaults to a 60 second timeout. You can configure this with a timeout option at the client or request level.

from rcs import Pinnacle

client = Pinnacle(
    ...,
    timeout=20.0,
)


# Override timeout for a specific method
client.brands.autofill(..., request_options={
    "timeout_in_seconds": 1
})

Custom Client

You can override the httpx client to customize it for your use-case. Some common use-cases include support for proxies and transports.

import httpx
from rcs import Pinnacle

client = Pinnacle(
    ...,
    httpx_client=httpx.Client(
        proxy="http://my.test.proxy.example.com",
        transport=httpx.HTTPTransport(local_address="0.0.0.0"),
    ),
)

Contributing

While we value open-source contributions to this SDK, this library is generated programmatically. Additions made directly to this library would have to be moved over to our generation code, otherwise they would be overwritten upon the next generated release. Feel free to open a PR as a proof of concept, but know that we will not be able to merge it as-is. We suggest opening an issue first to discuss with us!

On the other hand, contributions to the README are always very welcome!

Metadata

Release files for rcs 2.0.29rc1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for rcs 2.0.29rc1
File Size Uploaded Provenance Actions
rcs-2.0.29rc1.tar.gz 271.5 kB With provenance Details for rcs-2.0.29rc1.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for rcs 2.0.29rc1
File Interpreter ABI Platform Actions
rcs-2.0.29rc1-py3-none-any.whl Python 3 none any Details for rcs-2.0.29rc1-py3-none-any.whl

Total release size: 915.2 kB

Release files / rcs-2.0.29rc1.tar.gz

Download URL rcs-2.0.29rc1.tar.gz
Size 271.5 kB
Tags Source
SHA-256 checksum
How to use checksums
e7cb9271b5cea3280be5491e78154b49c18f1db142f82b6378ebf3606fe529b7
BLAKE2b-256 checksum
How to use checksums
963ae5f6885974e4b5bc68f06fad6b83e88a63ea01f69247bd20953971e213b6
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 Oct 26, 2026.

Transparency log

Release files / rcs-2.0.29rc1-py3-none-any.whl

Download URL rcs-2.0.29rc1-py3-none-any.whl
Size 643.7 kB
Tags Python 3
SHA-256 checksum
How to use checksums
b27a560c6cbfe7a5324518e001bee52ead676b6f114d8e1d5def9e1a75352f76
BLAKE2b-256 checksum
How to use checksums
f7cbe8a0573488dfca94939d7623ed279ee603fc7e0889a931479ae3df64010e
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 Oct 26, 2026.

Transparency log

Security for rcs 2.0.29rc1

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 rcs-2.0.29rc1.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 Oct 26, 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.

Release history Release notifications | RSS feed

This release
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