# Lenormand: Pair Combination

`POST https://api.astroway.info/v1/tarot/lenormand/combination`

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.

Group: Tarot: Lenormand. Auth: `X-Api-Key` header. Operation ID: `tarot_lenormand_combination`.

## Parameters

| Name | In | Required | Type | Description |
|---|---|---|---|---|
| `fields` | query | no | 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. |
| `precision` | query | no | integer | 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. |
| `Idempotency-Key` | header | no | string | 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/. |

## Request body

| Field | Type | Required | Description |
|---|---|---|---|
| `cards` | string[] | yes | Two Lenormand slugs in reading order, e.g. ["heart", "ring"]. |

```json
{
  "cards": [
    "heart",
    "ring"
  ]
}
```

## Responses

| Status | Meaning |
|---|---|
| 200 | Successful calculation |
| 400 | Validation error |
| 401 | Missing or invalid API key |

### Success fields, under `data`

| Field | Type | Required | Description |
|---|---|---|---|
| `first` | object | no |  |
| `first.slug` | string | no |  |
| `first.number` | number | no |  |
| `first.name` | string | no |  |
| `first.meaning` | string | no |  |
| `second` | object | no |  |
| `second.slug` | string | no |  |
| `second.number` | number | no |  |
| `second.name` | string | no |  |
| `second.meaning` | string | no |  |
| `reading` | string | no |  |
| `readingReversedOrder` | string | no |  |
| `tone` | string | no |  |
| `rule` | string | no |  |
| `basis` | string | no |  |

## Example

```bash
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" ] }'
```

---

Rendered from https://api.astroway.info/v1/openapi.json. HTML page: https://api.astroway.info/docs/api/operations/tarot_lenormand_combination/
