Skip to content
AstroWay/api v2.325.0 · docs
all systems operational

Lenormand: Pair Combination

POST
/tarot/lenormand/combination
request.sh
curl -X POST https://api.astroway.info/v1/tarot/lenormand/combination \
-H "X-Api-Key: aw_live_..." \
-H "Content-Type: application/json" \
-d '{ "cards": [ "heart", "ring" ] }'

Reads two Lenormand cards as a pair: the first is the subject, the second describes it, so order matters. Returns the reading, the reading in the other order and the combined tone. Composed from per-card phrases we wrote, not a copied pair table.

fields
string

Comma-separated dotted paths, relative to data, to keep in the response. A path is applied to every element of an array, so planets.name means the name of each planet. Paths that match nothing come back in _fields_unmatched; a list where nothing matches at all is a 400, because an empty object would be a confident wrong answer.

Example
planets.name,planets.longitude
precision
integer
<= 15

Round every non-integer number in the response to this many decimal places. Integers are left alone, because an id is not a measurement. Ecliptic longitudes ship with fourteen decimals by default; 2 is about a tenth of an arcminute.

Example
4
Idempotency-Key
string
>= 1 characters <= 255 characters /^[\x21-\x7E]+$/

Unique per logical operation, kept across retries. For 24 hours from the first request, a repeat with the same key, method, path, body and query string returns the stored response with Idempotent-Replayed: true and costs 0 credits. The same key with a different body or query string is a 409 IDEMPOTENCY_KEY_REUSED; a repeat while the first is still running is a 409 IDEMPOTENCY_IN_PROGRESS. Only 2xx responses are kept. See /idempotency/.

Example
01HXY2A7ZM0ABCDEF
Media type application/json
object
cards required

Two Lenormand slugs in reading order, e.g. [“heart”, “ring”].

Array<string>
Example
{
"cards": [
"heart",
"ring"
]
}

Successful calculation

Media type application/json
object
ok
boolean
data
object
first
object
slug
string
nullable
number
number
nullable
name
string
nullable
meaning
string
nullable
second
object
slug
string
nullable
number
number
nullable
name
string
nullable
meaning
string
nullable
reading
string
nullable
readingReversedOrder
string
nullable
tone
string
nullable
rule
string
nullable
basis
string
nullable
Example
{
"ok": true,
"data": {
"first": {
"slug": "heart",
"number": 24,
"name": "Heart",
"meaning": "love, romance, feeling, generosity"
},
"second": {
"slug": "ring",
"number": 25,
"name": "Ring",
"meaning": "commitment, contract, partnership, cycle"
},
"reading": "Love and feeling, bound by agreement.",
"readingReversedOrder": "A commitment or contract, warm and loving.",
"tone": "positive",
"rule": "The first card is the subject and the second describes it, so the order matters: Heart then Ring is love that becomes a commitment, Ring then Heart a commitment made with love.",
"basis": "convention"
}
}

Validation error

Media type application/json
Example
{
"ok": false,
"error": {
"code": "INVALID_INPUT",
"message": "Validation failed: date: Date must be YYYY-MM-DD",
"details": [
{
"path": "date",
"message": "Date must be YYYY-MM-DD"
}
]
}
}

Missing or invalid API key

Media type application/json
Example
{
"ok": false,
"error": {
"code": "INVALID_API_KEY",
"message": "Invalid API key"
}
}