Changelog & SDK Releases
What changed in the API, the portal, and the orenyx-sdk package, in the order it actually shipped. This is a record of real changes, not a marketing feature list — an entry appears here once it is live, not when it was planned.
The API itself has a single version (
/api/v1) and has never had a breaking change — see the Versioning & Deprecation Policy for what would count as one. Everything below is additive: new capability, or a fix to existing behavior, never a change that breaks an existing integration.SDK releases
orenyx-sdk@0.1.0— first public release on npm. Covers API-key and OAuth token authentication, scoped access, and two-factor-aware account flows. Install withnpm install orenyx-sdk.
2026-07-30
- Added a generic context API — a per-tenant key-value store for a bot, workflow, or integration to persist small pieces of state between calls.
- API responses now include X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset headers on every request authenticated with an API key, not only once a request is already rate-limited.
- Tenant subscription plan (Small / Mid / Large) is now persisted directly on the tenant record, kept in sync from both the portal's plan-change action and Stripe's own subscription webhooks — including plan changes made directly in the Stripe Customer Portal.
- Refunds can now be initiated through the API and are reconciled through the same webhook-confirmed path as chargebacks, so there is exactly one place a REFUND ledger entry is ever written.
- Usage metering now records real data (API calls, leads processed) instead of an empty framework with nothing feeding it.
- Database backups are now encrypted at rest (AES-256-GCM) and can optionally upload to S3 for offsite storage.
- Fixed a bug where a deleted or reordered ledger entry was not detected by hash-chain verification — verification now checks each entry against a running expected hash per currency, not just its own internal consistency.
- Fixed duplicate settlement records being created on a redelivered reconciliation job; settlement reconciliation is now idempotent per tenant, period, and currency.
- Settlement reconciliation endpoints changed from GET to POST, since they trigger a real reconciliation rather than only reading data.
- Added a "Run" action for saved workflows, so a workflow can be triggered on demand instead of only by its configured automatic trigger.
- Two-factor authentication is now a self-service, per-account toggle in Settings, and defaults to off for new signups; the signup email-verification code is now mandatory and enforced server-side.
- Automated dunning emails now go out at each escalation stage, on a daily schedule, instead of only writing an audit log entry with no notification.
- Portal role checks (team, billing, integrations access) that were previously duplicated across multiple files now come from one shared module.
- Published an Information Security Policy and a public Security & Trust page.
2026-07-29
- The SDK was renamed to orenyx-sdk and published publicly on npm.
- A suspended tenant's API keys and OAuth tokens now stop working immediately, and a paused bot's queued jobs re-queue themselves instead of being dropped.
- The API moved to versioned /v1/ routes.
Earlier
Everything before the dates above, including the original lead-intake, qualification, scheduling, payment, and follow-up pipeline, the workflow execution engine, and the initial Developer Portal, is covered in the SOC 2 Overview and Compliance pages rather than repeated here entry by entry.
Was this page helpful?