Skip to content

Releases: Rayon-API/rayon-sdk-py

rayon-sdk-py 1.1.5

Choose a tag to compare

@RayonAPI RayonAPI released this 23 Oct 11:16

Clarify generation failure and incomplete-result messages with conditional script-loader and support guidance. Explain generated header and form validation failures without assigning fault to supplied material.

Includes a focused regression test. Runtime request, retry and billing behavior is unchanged.

rayon-sdk-py 1.1.4

Choose a tag to compare

@RayonAPI RayonAPI released this 20 Oct 18:04

Persistent clients retain original material within 128 bundles / 16 MiB per client, coalesce simultaneous uploads, and refresh material on the next generation near expiry.

A confirmed HTTP 422 material_expired response with billing_status: "not_charged" can recover once using retained originals. Each generation preserves its current request, profile and cookie inputs. Transport failures, cancellation and ambiguous billing outcomes are never automatically retried. Recovery and material waiting share one monotonic overall deadline.

Validation: 263 tests passed on Python 3.12; source/wheel builds, archive audit, twine validation, installation and version import passed.

1.1.3

Choose a tag to compare

@RayonAPI RayonAPI released this 19 Oct 15:08
ec8ad25

Clearer API errors with optional reasons, recovery guidance, safe domain and field details, and billing status.

Existing exception types, error codes and retry behavior are preserved. No automatic request retries are added.

1.1.2 — Retry guidance

Choose a tag to compare

@RayonAPI RayonAPI released this 17 Oct 11:32
7179594

Expose the optional API error.retryable flag as safe boolean metadata without automatically retrying requests. Add request-history guidance for confirmed, pending and unavailable billing outcomes; retain current header/form API support.

Validation: 178 tests; wheel/sdist build; twine checks. Version 1.1.2.

1.1.1 — Clearer HTTP errors and current API guidance

Choose a tag to compare

@RayonAPI RayonAPI released this 15 Oct 07:50
14225f1

Clarify HTTP errors and current API guidance.

v1.1.0

Choose a tag to compare

@RayonAPI RayonAPI released this 14 Oct 21:33
15a47c8

Add opt-in mode: "form" generation with typed form results, exact-case ordered
fields, and a telemetry-only encoded body. Validate form transport, UTF-8, limits,
and complete telemetry families. Default header generation and material reuse remain
compatible. Accept the six required headers plus an optional fresh same-family a0,
preserving returned names and values. Reject incomplete, duplicate, mixed-family and
unsafe header sets. Form results remain exactly six fields. Reject mismatched response
transports and redact form values in inspection.

v1.0.3

Choose a tag to compare

@RayonAPI RayonAPI released this 14 Oct 17:22
a4cdcfe

Documentation-only release. Runtime behavior is unchanged.

  • Shorter setup and generation instructions using prepared client-owned material.
  • Clearer request/session requirements and links to the material collection guide.
  • Generic examples without real target businesses.

v1.0.2

Choose a tag to compare

@RayonAPI RayonAPI released this 13 Oct 12:04

Improves integration guidance and rejects malformed server material references that cannot be reused. Keeps the material-only API contract and fresh generation behavior.

Includes sync/async clients and clearer lifecycle, cache, error and transport documentation.

v1.0.1

Choose a tag to compare

@RayonAPI RayonAPI released this 13 Oct 10:18

Set the default complete API-call deadline to 45 seconds for material-only generation. Explicit caller overrides are unchanged. No generation or profile logic changed.

Verified 103 Python tests and 81 JavaScript tests, plus packaged exports.

v1.0.0

Choose a tag to compare

@RayonAPI RayonAPI released this 13 Oct 10:03

Version 1.0 uses the material-only RayonAPI contract.

  • Generate through POST /v1/shape with ordered protection scripts (or a material reference), a browser profile and the exact application request.
  • Reuse HTTP connections, retrieve usage and handle structured errors and cancellation.
  • Keep target cookies and application credentials in your own target session. Generated headers do not establish target acceptance.

Validated by SDK contract, deadline, redaction and packaged export tests.