# Angel Numbers for Life Path

`GET https://api.astroway.info/v1/esoteric/angel-numbers/by-life-path/{n}`

Angel numbers aligned to a given life-path number (1-9, 11, 22, 33). Useful to identify recurring numerical signatures aligned with one's soul path.

Group: Esoteric. Auth: `X-Api-Key` header. Operation ID: `esoteric_angel-numbers_by-life-path_{n}_get`.

## Parameters

| Name | In | Required | Type | Description |
|---|---|---|---|---|
| `n` | path | yes | integer | Life path number: 1-9, or the master numbers 11, 22, 33. |
| `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. |

## Responses

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

### Success fields, under `data`

| Field | Type | Required | Description |
|---|---|---|---|
| `lifePath` | number | no |  |
| `items` | object[] | no |  |
| `count` | number | no |  |

## Example

```bash
curl -X GET https://api.astroway.info/v1/esoteric/angel-numbers/by-life-path/{n} \
  -H "X-Api-Key: aw_live_..." \
  -H "Content-Type: application/json"
```

---

Rendered from https://api.astroway.info/v1/openapi.json. HTML page: https://api.astroway.info/docs/api/operations/esoteric_angel-numbers_by-life-path_n_get/