Horoscope Embed Code: Preview and Style Every Widget First
Horoscope embed code for any website. Preview, theme and translate every astrology, tarot and Vedic widget with no account, then go live on one plan.
TL;DR
- Horoscope embed code from RoxyAPI is two lines of HTML that render a live horoscope, birth chart, dasha timeline, bodygraph or tarot spread on any website, with no server and no build step.
- The widget builder shows every widget, theme preset, light or dark mode and language before you create an account.
- Every plan includes every widget in every domain, from Western and Vedic astrology to human design, BaZi, feng shui, numerology and tarot.
- The widgets are built on
@roxyapi/ui, an MIT licensed component library, so one CSS variable brands every widget on your page.
RoxyAPI is the data layer for insight, belief and prediction products, and its horoscope embed code puts that data on a page that has no backend. Most horoscope widgets are a fortune cookie with a zodiac picker: twelve paragraphs, rotated daily, and a separate subscription the day you want tarot beside it. These widgets read the birth moment of each visitor across Western and Vedic astrology, human design, Chinese metaphysics, numerology and tarot, all on one plan with the Astrology API. This guide covers what you can check before you pay, how deep the catalog goes, how to match it to your brand, and which embed code each site builder takes.
How do you get horoscope embed code without writing code?
Open the widget builder, pick a widget, choose a look, and copy the code. The builder writes the snippet, shows a preview of the result, and lists the paste steps for your site builder. Pick, style, paste: no code is written by hand at any point.
The default snippet is one script tag and one mount element. Swap horoscope-card for natal-chart, dasha-timeline or bodygraph and the same two lines render a different reading.
<script src="https://cdn.jsdelivr.net/npm/@roxyapi/ui@latest/dist/cdn/widgets.js" defer></script>
<div data-roxy-widget="horoscope-card" data-publishable-key="pk_live_YOUR_KEY" data-hide-sections="hint"></div>A site builder that accepts only a link, such as Wix, takes the hosted embed URL instead. It carries the same choices as query parameters:
https://roxyapi.com/embed/horoscope-card?pk=pk_live_YOUR_KEYWhat can you check before creating an account?
Everything that decides whether a widget fits your site: the look, the language and the code itself. No sales call, no trial clock, and no dashboard to log into just to see what you are buying. The builder previews each widget from a sample reading, and you can run any endpoint live in the API reference with no account.
| What you want to check | Where | Account needed |
|---|---|---|
| Every widget, grouped by domain | Widget builder | No |
| Theme presets and light, dark or automatic mode | Widget builder preview | No |
| Language of the widget labels | Widget builder language menu | No |
| Chart only, or chart plus written reading | Widget builder Content options | No |
| Optional RoxyAPI credit line | Widget builder Content options | No |
| The exact code and the paste steps per site builder | Widget builder | No |
| Live responses for any endpoint | API reference | No |
| Readings on your own domain | Your site | A plan and a publishable key |
Ready to go live? One plan powers every widget in every domain. See pricing and pick the quota that fits your traffic.
How deep do the widgets go?
As deep as the practice. A sun-sign paragraph speaks to one twelfth of humanity at a time; these widgets work from the exact birth date, time and place of each visitor. Planet positions read the NASA JPL DE440 ephemeris, and birth places resolve to the time zone in force on the birth date.
| Domain | Beyond the daily horoscope |
|---|---|
| Western astrology | Natal and synastry wheels, a transit wheel with the natal chart inside and transits outside, astrocartography lines on a world map, local space compass, annual profections with the lord of the year, fixed star conjunctions |
| Vedic astrology | Kundli, divisional charts from D2 to D60, a Vimshottari dasha timeline that drills down five levels, Ashtakavarga heatmap, Shadbala strength, KP ruling planets, guna milan, panchang |
| Forecast | A dated timeline of events across Western, Vedic and biorhythm cycles, weighted by significance |
| Human design | The full bodygraph with every gate and line, the four variable arrows, and connection charts for two people |
| Chinese astrology and feng shui | BaZi chart, ten-year luck pillars, a nine-palace flying star plate, kua numbers |
| Vastu and kabbalah | A vastu mandala with the devata per square, gematria across every cipher and Hebrew spelling |
| Tarot, numerology and more | Tarot spreads with positions and readings, numerology cards, I Ching hexagrams, a filterable crystal grid, dream symbol search, angel numbers |
Each widget has its own page on Roxy UI with a preview, its fields and its code.
Which widgets does one plan include?
All of them. No per-widget subscriptions, no tarot add-on, no upgrade wall between the horoscope and the kundli. A practitioner site can run a daily horoscope, a dasha timeline, a three-card tarot spread and a human design bodygraph on one plan and one publishable key.
How do you match a widget to your brand?
Pick a theme preset and a mode in the builder, and the code you copy carries that look onto your site. Presets include Rosewater, Eucalyptus, Kiln, Moonlit and Celeste. Mode is light, dark, or automatic to follow the visitor device.
A preset adds one stylesheet line, and a fixed mode wraps the mount:
<link rel="stylesheet" href="https://cdn.jsdelivr.net/npm/@roxyapi/ui@latest/dist/styles/themes/moonlit.css">
<script src="https://cdn.jsdelivr.net/npm/@roxyapi/ui@latest/dist/cdn/widgets.js" defer></script>
<div data-theme="dark">
<div data-roxy-widget="horoscope-card" data-publishable-key="pk_live_YOUR_KEY" data-hide-sections="hint"></div>
</div>Past the presets, the script snippet takes your own CSS. Every widget is built on @roxyapi/ui and reads its colours, fonts, spacing and corners from --roxy-* CSS variables. The widgets inherit the font of your page by default, and one line in your site stylesheet sets the accent on every widget at once:
:root {
--roxy-accent: #6d28d9;
}The full token list, dark mode, per-widget overrides and Tailwind mapping are in the theming guide. The hosted embed URL runs in its own frame, so it takes the presets and modes from the builder.
Which embed code fits your site builder?
Use the script snippet wherever the builder accepts HTML with a script, and the hosted embed URL where it accepts only a link. The builder shows the right form and the paste steps for each platform.
| Site builder | What to paste |
|---|---|
| Squarespace | The snippet in a Code Block, on a plan that runs JavaScript |
| Wix | The hosted embed URL in Embed a site |
| WordPress | The snippet in a Custom HTML block, or the free RoxyAPI plugin |
| Shopify | The snippet in a Custom Liquid section |
| Any other site | The snippet in an embed or code block |
Step-by-step pages for each platform, and fixes for every error a widget can show, are in the widget setup guide.
Is a publishable key safe in page source?
Yes. A widget key is a publishable key (pk_live_) that answers only on the websites you list for it and reads no account data. Remove a site or revoke the key in your account at any time. Secret keys stay on servers, and a widget refuses one in the browser.
When should a developer use the npm components instead?
Use the npm components when you build an app in React, Vue or another framework and fetch the data yourself. The same MIT licensed library ships on npm as @roxyapi/ui: you call the API on your server with a secret key and pass the response to the component as data. The widget is the paste-and-ship path; the component is the app path, and both render the same reading.
| Question | Embedded widget | npm component |
|---|---|---|
| Fetches the reading | Itself, in the visitor browser | Your server, then passed in as data |
| Key | Publishable key in the page | Secret key on your server |
| Build step | None | Your framework build |
| Styling | Presets, modes and --roxy-* variables | The same --roxy-* variables |
| Best for | Site builders and one-link pages | Apps that control fetching and caching |
FAQ
Can I preview astrology widgets without an account?
Yes. The RoxyAPI widget builder previews every widget, theme preset, mode and language with no account and no key. Live readings on your own site start with a plan and a publishable key, and the API reference runs any endpoint live with no account.
Do I pay separately for a horoscope widget and a tarot widget?
No. Every RoxyAPI plan includes every widget in every domain, with no per-widget or per-domain fee. A horoscope, a kundli and a tarot spread run on the same plan and the same publishable key.
Are the widgets more than a daily horoscope?
Yes. Beside the daily horoscope sit natal and transit wheels, astrocartography maps, a five-level dasha timeline, Shadbala and Ashtakavarga, a full human design bodygraph, BaZi luck pillars, flying star plates and tarot spreads. Each works from the birth details your visitor enters.
Can I change the colours and fonts of the widget?
Yes. Pick a theme preset and light or dark mode in the builder, or set --roxy-* CSS variables in your own stylesheet. The widgets inherit your page font by default, and one variable sets the accent on every widget at once.
How do I add a horoscope widget to Wix?
Copy the hosted embed URL from the widget builder, then in the Wix editor choose Add Elements, Embed Code, Popular Embeds, Embed a site, and paste the link. Give the box about 600px of height and publish.
Is the widget code open source?
Yes. The widgets are built on @roxyapi/ui, an MIT licensed component library on GitHub and npm. Live readings run on a RoxyAPI plan.
Conclusion
A fortune cookie in a box is easy to embed and easy to ignore. Open the widget builder, check every widget, theme and language, and go live on one plan when it fits. Explore the Astrology API behind every widget and compare plans on pricing.