Skip to main content

Schedulin Python Library

fern shield pypi

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

Table of Contents

Installation

pip install schedulin

Reference

A full reference for this library is available here.

Handling timeouts

A request that exceeds its timeout raises httpx's TimeoutException (e.g. httpx.ReadTimeout) — not ApiError, which is reserved for non-2xx responses. Catch both when you set a timeout:

import httpx

from schedulin import Schedulin
from schedulin.core.api_error import ApiError

client = Schedulin(api_key="YOUR_API_KEY", timeout=20.0)
try:
    client.posts.list()
except httpx.TimeoutException:
    ...  # timed out — safe to retry idempotent calls
except ApiError as e:
    print(e.status_code, e.body)

Usage

Instantiate and use the client with the following:

from schedulin import Schedulin

client = Schedulin(
    api_key="<value>",
)

client.posts.create(
    caption="caption",
    social_account_id="socialAccountId",
)

Environments

This SDK allows you to configure different environments for API requests.

from schedulin import Schedulin
from schedulin.environment import SchedulinEnvironment

client = Schedulin(
    environment=SchedulinEnvironment.DEFAULT,
)

Async Client

The SDK also exports an async client so that you can make non-blocking calls to our API. Note that if you are constructing an Async httpx client class to pass into this client, use httpx.AsyncClient() instead of httpx.Client() (e.g. for the httpx_client parameter of this client).

import asyncio

from schedulin import AsyncSchedulin

client = AsyncSchedulin(
    api_key="<value>",
)


async def main() -> None:
    await client.posts.create(
        caption="caption",
        social_account_id="socialAccountId",
    )


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 schedulin.core.api_error import ApiError

try:
    client.posts.create(...)
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 schedulin import Schedulin

client = Schedulin(...)
response = client.posts.with_raw_response.create(...)
print(response.headers)  # access the response headers
print(response.status_code)  # access the response status code
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).

Which status codes are retried depends on the retryStatusCodes generator configuration:

legacy (current default): retries on

  • 408 (Timeout)
  • 409 (Conflict)
  • 429 (Too Many Requests)
  • 5XX (All server errors, including 500)

recommended: retries on

  • 408 (Timeout)
  • 409 (Conflict)
  • 429 (Too Many Requests)
  • 502 (Bad Gateway)
  • 503 (Service Unavailable)
  • 504 (Gateway Timeout)

Use the max_retries request option to configure this behavior.

client.posts.create(..., 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 schedulin import Schedulin

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

# Override timeout for a specific method
client.posts.create(..., request_options={
    "timeout": 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 schedulin import Schedulin

client = Schedulin(
    ...,
    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 schedulin 0.4.16

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

Source distribution (sdist)

Source distribution for schedulin 0.4.16
File Size Uploaded Provenance
schedulin-0.4.16.tar.gz 115.3 kB Without provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for schedulin 0.4.16
File Interpreter ABI Platform
schedulin-0.4.16-py3-none-any.whl Python 3 none any Details

Total release size: 332.2 kB

Release files / schedulin-0.4.16.tar.gz

Download URL schedulin-0.4.16.tar.gz
Size 115.3 kB
Tags Source
SHA-256 checksum
How to use checksums
211c557a93acc18eb618f6db94529e69df63804bad416fc8c7d3f69cabb4e7b8
BLAKE2b-256 checksum
How to use checksums
a749f7a404064895524b81c6eaffef0a597dfba24e2e8e1401b19e15a2c5487a
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.12.15

Release files / schedulin-0.4.16-py3-none-any.whl

Download URL schedulin-0.4.16-py3-none-any.whl
Size 216.9 kB
Tags Python 3
SHA-256 checksum
How to use checksums
d95bfebe6399630a75d25ae0e11ccf738fc935dd7a744a71cf8fc3d9dfeea423
BLAKE2b-256 checksum
How to use checksums
3f5d2593f5b2e7b179c6fba5a4723e2fe5604080f379eadb8ca3181af2a160e1
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.12.15

Security for schedulin 0.4.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.

No provenance found

None of the files in this release were uploaded with provenance metadata.

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

0.4.16 This release

2 release files No provenance

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