Angel numbers API guide

Ship an angel-number lookup tool, a daily number widget, or a detector for repeating sequences.

111 meaning, 222 meaning, 333 angel number are evergreen viral queries. Gen Z spiritual-tok keeps them trending. The RoxyAPI angel-number endpoints cover 75+ angel numbers plus a universal lookup for sequences of 1 to 8 digits, with digit-root fallback for sequences outside the curated library.

What you can build

• Angel-number meaning pages (every "meaning of 1111" URL backs to this)
• Detectors that spot repeating numbers on clocks and receipts
• Daily angel-number widgets with affirmations
• Spiritual chatbots that interpret any number sequence

Prerequisites

1. A RoxyAPI key. Get your API key.
2. Nothing else. Lookup calls use GET; the daily endpoint uses POST.

Install

npm install @roxyapi/sdk

pip install roxy-sdk

composer require roxyapi/sdk

dotnet add package RoxyApi.Sdk

Set the API key once at SDK construction. Detailed setup in SDK install + usage.

Call the endpoint

The #1 call is the universal lookup. It accepts a string of 1 to 8 digits and returns a curated meaning or digit-root fallback. Pick a language.

curl "https://roxyapi.com/api/v2/angel-numbers/lookup?number=444" \
  -H "X-API-Key: $ROXY_API_KEY"

import { createRoxy } from '@roxyapi/sdk';

const roxy = createRoxy(process.env.ROXY_API_KEY!);

const { data, error } = await roxy.angelNumbers.analyzeNumberSequence({
  query: { number: '444' },
});
if (error) throw error;

const meaning = data.knownMeaning ?? data.digitRootMeaning;
console.log(meaning?.title);
console.log(meaning?.coreMessage);

import os
from roxy_sdk import create_roxy

roxy = create_roxy(os.environ['ROXY_API_KEY'])

result = roxy.angel_numbers.analyze_number_sequence(number='444')
meaning = result.get('knownMeaning') or result['digitRootMeaning']
print(meaning['title'])
print(meaning['coreMessage'])

<?php

use function RoxyAPI\Sdk\createRoxy;

$roxy = createRoxy(getenv('ROXY_API_KEY'));

$result = $roxy->angelNumbers->analyzeNumberSequence(number: '444');
$meaning = $result['knownMeaning'] ?? $result['digitRootMeaning'];
echo $meaning['title'];
echo $meaning['coreMessage'];

using RoxyApi;

var roxy = new RoxyClient(Environment.GetEnvironmentVariable("ROXY_API_KEY")!);

var result = await roxy.AngelNumbers.Lookup.GetAsync(c => c.QueryParameters.Number = "444");

// KnownMeaning is set for recognized sequences (444, 1111, ...); DigitRootMeaning always is
Console.WriteLine(result!.KnownMeaning?.Title ?? result.DigitRootMeaning!.Title);
Console.WriteLine(result.KnownMeaning?.CoreMessage ?? result.DigitRootMeaning!.CoreMessage);

claude mcp add-json --scope user roxy-angel '{"type":"http","url":"https://roxyapi.com/mcp/angel-numbers","headers":{"X-API-Key":"YOUR_KEY"}}'

The response includes number, type (repeating, sequential, mirror, master, root, compound), digitRoot, isPalindrome, isRepeating, a knownMeaning block (present when the number is in the curated library) and a digitRootMeaning fallback (always present). Each meaning block has title, coreMessage, energy, keywords, affirmation, actionSteps, and a nested meaning sub-object with spiritual, love, career, money, twinFlame. Use knownMeaning ?? digitRootMeaning to read the same fields regardless of which is set.

Render the result

Use the generic <roxy-data> renderer from @roxyapi/ui, exposed in React as RoxyData. It accepts any RoxyAPI response and lays out the JSON for you, including the nested knownMeaning and digitRootMeaning blocks, with no per-field markup. Pass the unwrapped data straight in.

'use client';
import { RoxyData } from '@roxyapi/ui-react';
import type { GetAngelNumbersLookupResponse } from '@roxyapi/sdk';

export function AngelNumberCard({ data }: { data: GetAngelNumbersLookupResponse }) {
  return <RoxyData data={data} />;
}

data is the unwrapped SDK response (const { data } = await roxy.angelNumbers.analyzeNumberSequence(...)), typed by GetAngelNumbersLookupResponse from @roxyapi/sdk.

Ship the rest

Build the lookup experience

Accept a sequence of 1 to 8 digits as text, so leading zeroes survive. Let the user optionally choose where they noticed it: clock, receipt, license-plate, phone, address, or price. Send that choice as context to the lookup endpoint and show the returned contextNote alongside the meaning.

Show the number, title, and coreMessage first, with the longer interpretation below. A share card can contain the number, affirmation, and your app name. Let users save favorites and choose whether to receive daily reminders. Present these meanings as spiritual interpretations, not predictions of health, money, or relationships.

Specific number

GET /angel-numbers/numbers/{number} returns the full interpretation when the number is a canonical angel sequence (1111, 222, 777, etc.). Use this for SEO landing pages that map one URL per number.

Daily

POST /angel-numbers/daily returns a daily angel number with optional per-user seed for deterministic push notifications.

See the full list at the Angel Numbers API reference.

Ready-made template

The /templates/astrology-ai-chatbot (multi-domain, covers Angel Numbers via Remote MCP) template ships a working Angel Numbers app you can clone, white-label, and deploy. MIT licensed. For the render layer, see the component catalog in @roxyapi/ui.

Gotchas

• The lookup endpoint accepts 1 to 8 digits. Digit-root fallback covers non-canonical sequences. Do not restrict input to repeating patterns such as 111, 222, or 333.
• Keep numbers as strings. Both the /numbers/1111 path and the /lookup?number=444 query use strings. This also preserves leading zeroes.
• type is the pattern classifier. repeating (444), sequential (123), mirror (121), master (11), root (9). Use this to theme the UI.
• lang controls translation. Pass ?lang=fr for French meanings, 10+ languages supported.

What to build next

For a multi-domain spiritual chatbot, the AI chatbot tutorial wires angel numbers plus tarot plus numerology under one agent. For typed calls, the SDK guide.