SDKs

The Bytloop API is intentionally close to HTTP so any language with a half-decent HTTP client can talk to it in a few lines. Official SDKs are on the roadmap; until they ship, the REST API is the canonical interface.

In the meantime#

The REST API is designed to feel obvious from any HTTP client. Every guide in these docs includes a curl example, and most include Node and Python snippets. Start with:

• Send a transactional email — the primary sending endpoint with curl, Node, and Python.
• Webhooks — receiving events with a signed HMAC handler.
• API explorer — an interactive reference that fires requests against your workspace with a click.

Community SDKs#

None yet. If you build one, open a pull request against the docs and we will link it here once we have taken a look.

What the SDKs will do#

When they ship, the official SDKs will:

• Sign requests with your API key and add the required headers.
• Type every request and response so autocomplete works everywhere.
• Handle retries with exponential backoff on 429 and 5xx, including honouring Retry-After.
• Provide a helper for verifying webhook signatures (see the hand-rolled Node example on the Webhooks page).

Nothing in the SDKs will do anything the REST API cannot — they are a convenience layer, not a replacement.