# Ephemeris Range

`POST https://api.astroway.info/v1/ephemeris`

Return planet positions for a date range with configurable step (min 0.01 days). Max range: 1 year for sub-day steps, 5 years otherwise. Optionally filter by planetIds.

Group: Core. Auth: `X-Api-Key` header. Operation ID: `ephemeris`.

## 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. |

## Request body

| Field | Type | Required | Description |
|---|---|---|---|
| `startDate` | string | yes |  |
| `endDate` | string | yes |  |
| `stepDays` | number | no |  |
| `planetIds` | integer[] | no |  |

```json
{
  "startDate": "2024-01-01",
  "endDate": "2024-12-31",
  "stepDays": 1,
  "planetIds": [
    0,
    1,
    2
  ]
}
```

## Responses

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

### Success fields, under `data`

| Field | Type | Required | Description |
|---|---|---|---|
| `ephemeris` | object[] | no |  |

## Example

```bash
curl -X POST https://api.astroway.info/v1/ephemeris \
  -H "X-Api-Key: aw_live_..." \
  -H "Content-Type: application/json" \
  -d '{ "startDate": "2024-01-01", "endDate": "2024-12-31", "stepDays": 1, "planetIds": [ 0, 1, 2 ] }'
```

---

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