POST/api/astro/tarot/yes-no/1 credit

Tarot yes or no

One card drawn against a question, read as yes, no or maybe. How the answer is decided is stated rather than left implicit, because conventions differ between readers and a bare "yes" hides which one produced it. Each card carries a traditional leaning — the Sun and the Ace of Cups lean yes, the Tower and the Nine of Swords lean no, the Two of Swords and Seven of Cups are ambivalent. A reversal flips a yes to a no and a no to a yes; an ambivalent card stays ambivalent either way up. Set `allow_reversed` false to read upright-only. The card and its full keywords come back with the verdict, because "no" on its own is not a reading and the card is what carries the meaning. Every response carries the `seed` that produced it, and sending that seed back reproduces the draw exactly — same cards, same order, same way up. Omit it and one is generated and returned, so a fresh draw is the default and repeating it afterwards is always possible. This is what lets a client store a reading and show it again rather than handing the querent a different answer to the same question.

https://yogataraapi.prahlad.app/api/astro/tarot/yes-no/

Test Request

Authentication

Send your key in the X-API-Key header. Keys are server-side credentials — never put one in browser JavaScript or a mobile app.

X-API-Key: yt_live_a1b2c3d4_…
Content-Type: application/json

Request fields

Field	Type	Required	Notes
allow_reversed	boolean	optional	Whether cards can come up reversed. Some readers work upright-only.
question	string	optional	Optional. Echoed back, and folded into a generated seed.
reversal_chance	number (double)	optional	Probability of a reversal, when reversals are allowed. min 0 · max 1
seed	string	optional	Send a seed to reproduce a draw exactly. Omit it and one is generated and returned, so any draw can be repeated afterwards.

Example request

curl -X POST https://yogataraapi.prahlad.app/api/astro/tarot/yes-no/ \
  -H "X-API-Key: $OCCULT_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"question":"Should I take the offer?","seed":"sample-yesno"}'

Response

{
  "data": {
    "question": "Should I take the offer?",
    "seed": "sample-yesno",
    "reproducible": "Send this seed back to get exactly this draw again.",
    "deck": "Rider-Waite-Smith, 78 cards",
    "reversals_allowed": true,
    "cards": [
      {
        "position": 1,
        "id": 14,
        "name": "Temperance",
        "arcana": "major",
        "suit": null,
        "rank": null,
        "number": 14,
        "element": null,
        "upright": "balance, moderation, patience, blending",
        "reversed": "imbalance, excess, impatience",
        "orientation": "upright",
        "meaning": "balance, moderation, patience, blending",
        "yes_no": "yes"
      }
    ],
    "answer": "yes",
    "card": "Temperance",
    "orientation": "upright",
    "meaning": "balance, moderation, patience, blending",
    "how_decided": "Each card has a traditional leaning. A reversal flips yes to no and no to yes; an ambivalent card stays ambivalent. Conventions differ between readers, so this one is stated rather than left implicit."
  },
  "status": 200,
  "is_error": false,
  "message": "successful"
}

Captured from a real call using the exact request above. Results sit under data.

Errors

Metering errors return { "error": "…", "message": "<code>", "is_error": true }. Show error to people and branch on message. See the error reference.