Skip to content
RoxyAPI
Get API Key

Changelog

Every new domain, SDK, Remote MCP server, and integration we ship, newest first.

Engineered since

2020

In production since

2024

Dated releases

70

Latest release

November 2026

Live build

v2.1112

  1. November 2026

    Platform

    The API reference playground moves beside every endpoint

    The live playground the reference has carried since launch now sits beside every endpoint and stays in view: code in every SDK language, its Remote MCP tool, editable example values and a live call with or without a key. Larger domains group into sections, and each domain page copies as Markdown.

  2. October 2026

    Platform

    Rosie gains conversations that follow your account

    Signed in, every chat with Rosie, the RoxyAPI guide on the site, is saved to your account and picks up where you left off on any device. Signed out, the conversation stays in your browser across visits. New chat starts fresh anywhere.

    UI

    Widgets gain a builder

    Pick any widget, preview it on desktop and phone, match your site with a theme preset and light or dark, and copy code for Squarespace, Wix, WordPress, Shopify or any page. Signed in, your key is filled in or created for your website in one step. Guides walk through the horoscope, birth chart, moon phase and tarot card widgets.

    UI

    Roxy UI gains a page for every component

    Every component has its own reference page with a live preview in each theme, code for HTML, React, Vue, Next.js and no-code sites, and its endpoints, attributes, sections and events, all from the published catalog.

    Platform

    Pause and resume billing from your account

    Pause a subscription and billing stops at once: the API key keeps working through the period already paid for. Resume any time on the same key, with nothing charged on the day, across every payment method.

    Platform

    Birth profiles gain the local day of each user

    Numerology charts and the Hebrew birthday take the local date of the user, so an age, a maturity cycle or a next birthday turns over on their own day anywhere on Earth. Secondary progressions read in the natal house system you choose, and KP planet tables answer at any latitude.

    Platform

    Location search reaches every town and village

    City search covers every city, town and village on record, whatever its population, each with coordinates and its IANA timezone. A hamlet with no recorded population resolves as surely as a capital, and a state, province or country in the query picks out the right one of many with the same name.

    UI

    Roxy UI components reach version 1.1

    The first stable line and the 95th release since 0.0.1 in May, for the web components and the React and Vue packages. Every component themes from a few design tokens with light, dark and named presets, charts open full size on a click, and the React package renders in Next.js server components.

    UI

    Widgets embed with a single attribute

    Every widget tag knows its own reading, so a publishable key or one route on your server is the whole snippet, the city search included; a setting such as the horoscope period picks another reading. Planet and sign names read in the page language across transits, asteroids and map widgets.

    UI

    Widgets gain hosting from your own domain

    Serve the widget files from your own site and route every request through your own server, so visitors load nothing from another host; one open source PHP file does it on any PHP site, with a Webasyst guide. Forms read in the language of the page and answer in the visitor time zone.

    SDK

    Official SDKs gain automatic retries and typed error codes

    Every official SDK now retries a rate-limited or briefly failed call on its own, honouring the wait the API asks for, and ships every error code as a typed constant. The Rust SDK moves to 2.0, with types that stay compatible as the API grows.

    Platform

    Retries become free: server errors no longer count against quota

    A request that fails on our side with a server error does not count against your monthly allowance, and the usage numbers in your account, the usage endpoint and the rate limit headers reflect it. Retry with confidence: a failure on our side never costs you a request.

Get API Key