1. Docs
  2. Domain Guides
  3. Angel Numbers

Angel Numbers API, what to build and how to call it

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

111 meaning, 222 meaning, 333 angel number are evergreen viral queries. Gen Z spiritual-tok keeps them trending. The Roxy angel-number endpoints cover the 43 canonical sequences plus a universal lookup that works for any positive integer via digit-root fallback. Users never hit "not found".

What you can build with this

  • 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

What you need, 30 seconds

  1. A Roxy API key. Get one on the pricing page.
  2. Nothing else. Content is pure GET.

Step 1, call your first endpoint

The #1 call is the universal lookup. It accepts any positive integer and always returns something meaningful. Pick a language.

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

The response includes number, type (repeating, sequential, mirror, master, root), digitRoot, isPalindrome, isRepeating, and a meaning block with title, coreMessage, energy, keywords, affirmation, action steps, and area-specific meanings (love, career, spirituality, twin flame).

Step 2, render it to the user

A number card with headline, affirmation, and area breakdown fits most apps.

export function AngelNumberCard({ data }: { data: any }) {
  const { number, meaning } = data;
  return (
    <article>
      <h2>{number}</h2>
      <p className="subtitle">{meaning.title}</p>
      <p>{meaning.coreMessage}</p>

      <aside>
        <h3>Affirmation</h3>
        <p>{meaning.affirmation}</p>
      </aside>

      <h3>By area</h3>
      <dl>
        <dt>Love</dt><dd>{meaning.love}</dd>
        <dt>Career</dt><dd>{meaning.career}</dd>
        <dt>Spirituality</dt><dd>{meaning.spiritual}</dd>
        <dt>Twin flame</dt><dd>{meaning.twinFlame}</dd>
      </dl>
    </article>
  );
}

Step 3, ship the rest

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.

Gotchas

  • The lookup endpoint works for any positive integer. Digit-root fallback covers non-canonical numbers. Do not write validation logic that rejects non-111/222/333 patterns.
  • Numbers are strings in paths, integers in the lookup query. /numbers/1111 path takes a string, /lookup?number=444 query param is the same. Pass strings to be safe.
  • 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, 8 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.