---
title: "Calculate relocation chart"
method: POST
path: "/ephemeris/relocation"
tags: ["ephemeris"]
---

# Calculate relocation chart

`POST /ephemeris/relocation`

## Request

- Base URL: `https://api.openephemeris.com`
- URL: `https://api.openephemeris.com/ephemeris/relocation`
- Auth: one of:
  - HTTP bearer
  - API key in header `X-OpenEphemeris-API-Key`
  - API key in header `X-API-Key`
  - API key in header `X-Service-Key`

Return angles, house cusps, and planet house changes for a relocated chart. 🤖 AI-optimized output available — add `format=llm` to reduce payload ~55%.

## Query parameters

- `format` string, nullable

## Headers

- `authorization` string, nullable
- `X-API-Key` string, nullable
- `X-OpenEphemeris-API-Key` string, nullable
- `apikey` string, nullable

## Request body

- RelocationRequest: Request payload for generating a relocation chart.
  - `house_system` 'P' | 'K' | 'O' | 'R' | 'C' | 'E' | 'W': Supported house systems.
  - `include_visual` boolean: If true, also render the relocated chart wheel (natal planets in the relocated houses) as SVG or PNG. Visuals incur a +2 credit surcharge.
  - `natal` NatalChartRequest, required: Request for natal chart calculation.
    - `configuration` NatalConfig: Declarative configuration for natal calculations.
      - `ascendant_on_left` boolean, nullable: When true (default), the Ascendant is placed at the 9 o'clock (West/left) position � matching the convention used by Astro.com, Solar Fire, and all major astrology software. Set to false to use the ecliptic-fixed (Aries-pinned) orientation instead.
      - `aspect_backing_discs` boolean, nullable: Wheel rendering only. When true (default), each aspect glyph sits on a small backing disc so it stays legible over crossing lines. Set false to draw bare glyphs. Honoured by /visualization/chart-wheel and /visualization/bi-wheel; rejected with 422 elsewhere.
      - `aspect_orbs` object: Caller-supplied orb allowances in degrees for the aspect lines drawn on the wheel, keyed by aspect name (conjunction, opposition, trine, square, sextile, and the minors quincunx, semisextile, semisquare, sesquiquadrate, quintile, biquintile). Same shape and semantics as ChartConfiguration.aspect_orbs: overrides the default table for the aspects named; aspects not named keep their defaults, and naming a minor is what turns it on. Setting an orb to 0 turns that aspect off entirely. An unknown aspect name is rejected with 422. Honoured by /visualization/chart-wheel and /visualization/bi-wheel (planet-to-planet lines; the include_angle_aspects lines keep their own table) and by /ephemeris/relocation (its aspect grid). /acg/midpoints, /ephemeris/natal/batch and /electional/natal-angle-crossings compute no aspect grid and reject the field with 422 rather than ignore it.
      - `asteroid_groups` AsteroidGroupEnum[]: Optional thematic asteroid groups to include alongside base object_set
      - `ayanamsa` 'lahiri' | 'fagan_bradley' | 'krishnamurti' | 'raman' | 'yukteshwar': Supported sidereal ayanamsa options. All five are computed from the same IAU 2006 general-precession model, so each is epoch-dependent rather than a frozen constant; they differ by up to ~2.3 degrees, which is enough to move a body across a sign boundary. Defaults to lahiri when zodiac_type is sidereal and no system is named.
      - `coordinate_frame` 'ecliptic' | 'equatorial' | 'horizontal': Reference frame for reported coordinates.
      - `coordinate_system` 'geocentric' | 'topocentric' | 'heliocentric' | 'barycentric': Coordinate system used for calculations.
      - `custom_objects` string[], nullable: Explicit body/point slugs to include, additive on top of object_set (and the entire set when object_set='custom'). Ephemeris bodies: sun, moon, mercury, venus, mars, jupiter, saturn, uranus, neptune, pluto, north_node, true_node, lilith, lilith_true, chiron, pholus, lilith_interpolated, eris, sedna, makemake, haumea, quaoar, orcus, ixion, varuna, cupido, hades, zeus, kronos, apollon, admetos, vulkanus, poseidon, eros, sappho, lilith_asteroid, nessus, chariklo, amor, betulia, icarus, apollo, adonis, phaethon, astraea, hebe, flora, metis, parthenope, victoria, egeria, irene, massalia, isis, anubis, odysseus, tolosa, medusa, ambrosia, aletheia, thule, polyxo, myrrha, valentine, hercynia, nestor, siva, atlantis, aphrodite, prometheus, epimetheus, shaposhnikov, lick, huya, ceres, pallas, juno, vesta, hygiea, eunomia, psyche, europa_asteroid, cybele, sylvia, thisbe, camilla, iris, davida, euphrosyne, interamnia. Angle-derived points: vertex, anti_vertex, south_node, part_of_fortune, equatorial_ascendant (alias east_point), equatorial_descendant. Unknown slugs are ignored.
      - `fixed_star_options` FixedStarConfig: Configuration for fixed star calculations.
        - `catalog_version` 'bright_mag3' | 'bright_mag5' | 'royal_stars' | 'parans_key': Fixed star catalog snapshots.
        - `include` boolean: Toggle fixed star conjunction calculations
        - `magnitude_limit` number: Maximum magnitude (lower = brighter)
        - `orb` number: Orb in degrees for fixed star hits
        - `stars` string[]: Optional whitelist of fixed stars to evaluate
      - `house_system` 'P' | 'K' | 'O' | 'R' | 'C' | 'E' | 'W': Supported house systems.
      - `node_source` 'true_osculating' | 'mean' | 'mean_apsides': Node/apsides calculation modes (SE §2.2).
      - `object_set` 'traditional_7' | 'modern_10' | 'modern_plus_chiron' | 'asteroids_major' | 'full' | 'custom': Standardized celestial object bundles.
      - `show_aspect_glyphs` boolean, nullable: Wheel rendering only. When true (default), an aspect glyph is drawn at the midpoint of each aspect line. Set false to draw the lines alone. Honoured by /visualization/chart-wheel and /visualization/bi-wheel; rejected with 422 elsewhere.
      - `zodiac_type` 'tropical' | 'sidereal': Supported zodiac frameworks.
    - `options` ResponseOptions: Options for customizing API response content and format.
      - `declination_orb` number: Orb in degrees for declination-based aspects
      - `include_angle_aspects` boolean: Include aspects between planets and the four chart angles (Ascendant, Descendant, Midheaven, Imum Coeli). Angle aspects use tighter orbs than planet-planet aspects and are flagged with `involves_angle` in the response. Defaults to false: these hits are location-dependent (a relocated chart keeps every planet-planet aspect and changes every angle aspect), so they are opt-in rather than silently added to the existing aspect list.
      - `include_aspects` boolean: Include aspect calculations
      - `include_declination_aspects` boolean: Include declination-based aspects
      - `include_declination_values` boolean: Include per-planet declination and right-ascension values (and topocentric variants when applicable). This is a payload shaping control and may be tier-gated.
      - `include_dignities` boolean: Include dignities (essential + accidental when available)
      - `include_fixed_stars` boolean: DEPRECATED. Fixed-star computation is configured via configuration.fixed_star_options.include. This field will be removed in a future release.
      - `include_hermetic_lots` boolean: Include Hermetic lot payload (aliases accepted: include_arabic_parts)
      - `include_minor_aspects` boolean: Include minor aspects (e.g., quincunx, semisquare, quintile). When False (default), only major aspects are computed.
      - `include_out_of_bounds` boolean: Include out-of-bounds flags for planets
    - `subject` SubjectRequest, required: Subject identity and birth data used to compute a chart.
      - `birth_datetime` DateTimeInput, required: Date/time input in ISO-8601, component, or Julian day form. A value that states a clock time must also state its zone, either as a suffix on the string or via the `timezone` field below.
        - `components` object: Date/time components (year, month, day, and optionally hour, minute, second). If hour/minute are present, pass `timezone` alongside them; without it the request is rejected with 400 ambiguous_datetime. Omit the clock entirely and the date resolves to 12:00 UTC.
        - `iso` string: ISO-8601 datetime (supported range 1550–2650 CE, JPL DE440). If it states a clock time it must carry its zone: either a 'Z'/±HH:MM suffix on the string ("1987-07-15T09:01:00-05:00"), or a `timezone` passed alongside it. A zone-less clock time is rejected with 400 ambiguous_datetime — it is not read as UTC. A date-only value ("1987-07-15") has no clock to be ambiguous about and resolves to 12:00 UTC.
        - `julian_day` number, double: Julian Day Number (always UTC-based, so it needs no zone)
        - `timezone` TimezoneInput: Timezone input using IANA names or UTC offsets.
          - `fold_preference` 'earlier' | 'later': Which occurrence to use when the naive local datetime falls in a fall-back fold (a repeated hour): 'earlier' (default — first occurrence) or 'later'. Only meaningful for naive datetimes; the response reports datetime_status=ambiguous_fold either way so the ambiguity can be surfaced to the user.
          - `iana_name` string: IANA timezone name
          - `time_standard` 'auto' | 'standard' | 'daylight': How to interpret a naive local datetime when this zone is applied. 'auto' (default): resolve through the historical-correction overlay where one covers the region/era, then IANA tzdata. 'standard': force the zone's standard (non-daylight) offset — for callers who KNOW the recorded time was standard time regardless of what tzdata believes. 'daylight': force standard+1h. Forcing either marks the resolution tz_confidence=client_override. Ignored when the datetime carries its own Z/±HH:MM suffix or when utc_offset is used.
          - `utc_offset` number: UTC offset in hours
      - `birth_location` BirthLocation, required: Location context for birth data: coordinates plus timezone.
        - `city` string: City name
        - `country` string: Country
        - `elevation` number: Elevation in meters. Accepted and echoed back unchanged; it does not affect planetary positions, which are computed geocentrically. Elevation changes results only where it is taken as the `elev` query parameter: /eclipse/solar/local (local circumstances) and /time/solar-event plus /ephemeris/agro/* (horizon rise/set times).
        - `latitude` CoordinateInput, required: Flexible coordinate input supporting multiple formats.
          - `components` object: Separate degree components with direction
          - `decimal` number: Decimal degrees (-90 to 90 for lat, -180 to 180 for lon)
          - `dms` string: Degrees, minutes, seconds string (e.g., '40°42'46"N')
        - `location_name` string: Birthplace display name (e.g. "Dallas, TX"). Never affects calculations — coordinates and timezone are the only location facts the engine reads. Echoed back verbatim where the response carries an echo block: as subject.location_name on chart routes that echo a subject (natal, draconic, progressed, synastry, natal-transits, overlay, natal/batch items, predictive transit-chart), inside search_summary on /electional/natal-angle-crossings, metadata on /acg/midpoints, and natal on /human-design/transit-chart. Omitted from the response when not sent.
        - `longitude` CoordinateInput, required: Flexible coordinate input supporting multiple formats.
          - `components` object: Separate degree components with direction
          - `decimal` number: Decimal degrees (-90 to 90 for lat, -180 to 180 for lon)
          - `dms` string: Degrees, minutes, seconds string (e.g., '40°42'46"N')
        - `region` string: State/region
        - `timezone` TimezoneInput, required: Timezone input using IANA names or UTC offsets.
          - `fold_preference` 'earlier' | 'later': Which occurrence to use when the naive local datetime falls in a fall-back fold (a repeated hour): 'earlier' (default — first occurrence) or 'later'. Only meaningful for naive datetimes; the response reports datetime_status=ambiguous_fold either way so the ambiguity can be surfaced to the user.
          - `iana_name` string: IANA timezone name
          - `time_standard` 'auto' | 'standard' | 'daylight': How to interpret a naive local datetime when this zone is applied. 'auto' (default): resolve through the historical-correction overlay where one covers the region/era, then IANA tzdata. 'standard': force the zone's standard (non-daylight) offset — for callers who KNOW the recorded time was standard time regardless of what tzdata believes. 'daylight': force standard+1h. Forcing either marks the resolution tz_confidence=client_override. Ignored when the datetime carries its own Z/±HH:MM suffix or when utc_offset is used.
          - `utc_offset` number: UTC offset in hours
      - `gender` string: Gender (optional)
      - `name` string, required: Subject name
      - `notes` string: Additional notes
  - `natal_id` string: Reserved identifier for previously computed natal context (lookup support depends on deployment configuration)
  - `relocation_lat` number, required: Relocation latitude in decimal degrees
  - `relocation_lon` number, required: Relocation longitude in decimal degrees
  - `visual_config` VisualRenderConfig: Optional rendering preferences for inline chart visuals.
    - `format` 'svg' | 'png': Output encoding: "svg" (default) or "png". PNG requires resvg on the server.
    - `layout` 'graph' | 'mandala': Bodygraph composition: "graph" (default) is the classic layout; "mandala" nests the same diagram inside concentric rings. Ignored for wheel renders. Honored on natal and overlay (transit, connection) bodygraph paths.
    - `size` integer: Canvas pixel dimension. Range [200, 4000]. Default 800.
    - `theme` 'light' | 'dark': Colour palette: "light" (default) or "dark".

## Response `200`

Successful Response

- RelocationResponse: Lean response describing the relocated chart.
  - `angles` RelocationAngles, required: Relocated chart angles.
    - `asc` RelocationAngle, required: Position of a relocated chart angle.
      - `longitude` number, required: Longitude of the angle in degrees
      - `sign` string, required: Zodiac sign occupied by the angle
      - `sign_longitude` number, required: Degrees within the occupied sign
      - `sign_symbol` string: Unicode symbol for the occupied zodiac sign
    - `dsc` RelocationAngle, required: Position of a relocated chart angle.
      - `longitude` number, required: Longitude of the angle in degrees
      - `sign` string, required: Zodiac sign occupied by the angle
      - `sign_longitude` number, required: Degrees within the occupied sign
      - `sign_symbol` string: Unicode symbol for the occupied zodiac sign
    - `ic` RelocationAngle, required: Position of a relocated chart angle.
      - `longitude` number, required: Longitude of the angle in degrees
      - `sign` string, required: Zodiac sign occupied by the angle
      - `sign_longitude` number, required: Degrees within the occupied sign
      - `sign_symbol` string: Unicode symbol for the occupied zodiac sign
    - `mc` RelocationAngle, required: Position of a relocated chart angle.
      - `longitude` number, required: Longitude of the angle in degrees
      - `sign` string, required: Zodiac sign occupied by the angle
      - `sign_longitude` number, required: Degrees within the occupied sign
      - `sign_symbol` string: Unicode symbol for the occupied zodiac sign
  - `calculation_metadata` CalculationMetadata: Metadata about chart calculations. Relaxed to allow minimal fields used by tests while remaining forward-compatible.
    - `ascendant_on_left` boolean, nullable: When true (default), the Ascendant is placed at the 9 o'clock (West/left) position � matching the convention used by Astro.com, Solar Fire, and all major astrology software. Set to false to use the ecliptic-fixed (Aries-pinned) orientation instead.
    - `ayanamsa` union: Sidereal ayanamsa selection
      - 'lahiri' | 'fagan_bradley' | 'krishnamurti' | 'raman' | 'yukteshwar': Supported sidereal ayanamsa options. All five are computed from the same IAU 2006 general-precession model, so each is epoch-dependent rather than a frozen constant; they differ by up to ~2.3 degrees, which is enough to move a body across a sign boundary. Defaults to lahiri when zodiac_type is sidereal and no system is named.
      - string
    - `calculation_time` number: Legacy calculation time in seconds
    - `calculation_time_ms` number: Processing time at the orchestrator layer in milliseconds
    - `calculation_time_utc` string, date-time: UTC timestamp when the calculation executed
    - `coordinate_reference_frame` string: Coordinate frame the positions are expressed in. The engine computes apparent places referred to the true equator/equinox of date and converts them to the true ecliptic of date, so this reads geocentric_true_ecliptic_of_date.
    - `coordinate_system` union: Coordinate system used (geocentric/topocentric)
      - 'geocentric' | 'topocentric' | 'heliocentric' | 'barycentric': Coordinate system used for calculations.
      - string
    - `delta_t_seconds` number: Delta T (TT - UT1) applied during calculation, in seconds
    - `delta_t_source` union: Source of Delta T values (computation engine, IERS, approximation)
      - 'nasa_jpl' | 'iers' | 'approximation_model': Source of ΔT values used in calculations.
      - string
    - `ephemeris_source` string: Primary ephemeris source (e.g., SuperNOVAS / Calceph)
    - `ephemeris_version` string: Version of the ephemeris data files
    - `fixed_star_catalog` union: Fixed star catalog or subset identifier
      - 'bright_mag3' | 'bright_mag5' | 'royal_stars' | 'parans_key': Fixed star catalog snapshots.
      - string
    - `house_system` union: House system actually used during calculation
      - 'P' | 'K' | 'O' | 'R' | 'C' | 'E' | 'W': Supported house systems.
      - string
    - `include_fixed_stars` boolean: Whether fixed stars were included
    - `julian_day` number, double: Julian Day Number representing the calculation instant
    - `missing_objects` object: Objects that could not be calculated along with reasons
    - `node_source` union: Lunar node/apsides mode requested (true osculating, mean, apsides)
      - 'true_osculating' | 'mean' | 'mean_apsides': Node/apsides calculation modes (SE §2.2).
      - string
    - `object_set` union: Named object set or preset powering the calculation
      - 'traditional_7' | 'modern_10' | 'modern_plus_chiron' | 'asteroids_major' | 'full' | 'custom': Standardized celestial object bundles.
      - string
    - `orb_system_used` string: Aspect orb system applied
    - `precision_level` string: Legacy precision descriptor
    - `precision_summary` PrecisionSummary: Structured precision report for calculation metadata.
      - `max_position_error_arcseconds` number: Maximum validated positional error in arcseconds
      - `max_timing_error_seconds` number: Maximum validated timing error in seconds
      - `notes` string: Additional human-readable context for the precision summary
      - `reference_profile` string: Reference dataset or validation profile used for the comparison
    - `processing_time_ms` number: End-to-end processing time in milliseconds
    - `server_version` string: Build identifier of the engine that produced this response. Moves on every deploy, so it is the signal for resolution-LOGIC changes — the class of change that can move a historical offset without touching overlay data (and therefore without moving tz_overlay_version). Poll both.
    - `sidereal_time` number: Local sidereal time in hours
    - `technique_id` string: High-level technique identifier (e.g., natal, synastry, composite, overlay)
    - `technique_label` string: Human-readable technique label
    - `technique_method` string: Method name within a technique (e.g., davidson, midpoint)
    - `technique_version` string: Technique implementation version (for future-proofing)
    - `time_scale` union: Time scale used for internal calculations (UTC, TT, TDB)
      - 'UTC' | 'TT' | 'TDB': Time scale used for reporting results.
      - string
    - `tz_overlay_hash` string: Content hash of the historical-correction overlay dataset that produced this answer. Stamped only when an overlay row applied (tz_rule_source starts with 'overlay:').
    - `tz_overlay_version` integer: Monotonic version of the historical-correction overlay dataset that produced this answer. Stamped only when an overlay row applied. Tracks overlay DATA only — pair with server_version to also catch resolution-logic changes.
    - `tz_precision` 'statutory' | 'documented' | 'inferred': Sourcing grade of the overlay row that produced the offset: 'statutory' (operative text of a session law or statute verified), 'documented' (contemporary reporting), or 'inferred' (deduced from legal context; verify before relying on it near the row's edges). Stamped only when an overlay row applied.
    - `tz_rule_citation` string: Primary-source citation for the overlay row that produced the offset — statute reference, ICC/agency order number, or documented press/almanac source. Stamped only when an overlay row applied.
    - `zodiac_type` union: Zodiac framework applied (tropical/sidereal)
      - 'tropical' | 'sidereal': Supported zodiac frameworks.
      - string
  - `houses` RelocationHouse[], required: House cusps after relocation
    - `index` integer, required: House index (1-12)
    - `longitude` number, required: Longitude of the house cusp
    - `sign` string, required: Zodiac sign on the cusp
    - `sign_longitude` number, required: Degrees within the cusp sign
    - `sign_symbol` string: Unicode symbol for the sign
    - `size` number, required: House size in degrees
  - `metadata` RelocationMetadata, required: Metadata describing the relocation calculation.
    - `calculation_source` string: Computation backend identifier
    - `fallback_used` boolean: True if a fallback house system was required for stability
    - `house_system` string, required: House system code actually used
    - `julian_day` number, double: Julian Day representing the calculation instant
    - `natal_house_system` string: House system used in the natal reference chart
    - `observer_location` RelocationObserverLocation, required: Observer location metadata for the relocated chart.
      - `elevation` number: Elevation in meters above sea level. Accepted and echoed back unchanged; it does not affect planetary positions, which are computed geocentrically. Elevation changes results only where it is taken as the `elev` query parameter: /eclipse/solar/local (local circumstances) and /time/solar-event plus /ephemeris/agro/* (horizon rise/set times).
      - `latitude` number, required: Observer latitude
      - `longitude` number, required: Observer longitude
    - `reference_frame` string: Reference frame for planetary positions
    - `requested_house_system` string: House system code requested by the client
    - `time_system` string: Time standard applied to the calculation
    - `topocentric_flag` boolean: Indicates whether topocentric positions were used
  - `planet_house_changes` PlanetHouseChange[]: Planets whose house placement changed
    - `body` string, required: Name of the celestial body
    - `from_house` integer, required: Original house index
    - `to_house` integer, required: Relocated house index
  - `planets` object: Planetary positions keyed by body name, matching natal chart format
  - `success` boolean: Indicates relocation succeeded
  - `summary` RelocationSummary, required: Summary statistics for a relocation result.
    - `changed_houses` integer, required: Number of houses whose cusps shifted
    - `changed_planets` integer, required: Number of planets that moved houses
    - `notes` string, required: Human-readable summary of key decisions
  - `visual` VisualResult: Embedded diagram payload returned alongside chart data when include_visual=true.
    - `content_type` string, required: MIME type of the data payload.
    - `credits_charged` integer, required: Additional credits consumed to render the visual: 2, or 0 on a re-render that presented a valid render_token.
    - `data` string, required: Raw SVG string (format=svg) or standard base64-encoded PNG bytes (format=png, no data: URI prefix).
    - `format` string, required: Output format: "svg" or "png".
    - `render_token` string: Short-lived (15 min) token for re-rendering this same chart. Send it back in the X-OE-Render-Token header (or a top-level render_token body field) with a request for the same chart inputs — e.g. the same birth data in a different theme or layout — and that request is not charged again. Bound to your account and to the chart-defining inputs; any other request is charged normally.
    - `type` string, required: Diagram kind: "wheel" or "bodygraph".

## Other responses

- `400`: Bad Request - Input validation failed
- `422`: Unprocessable Entity - Invalid input format
- `500`: Internal Server Error - Calculation failed

---

[API](https://skmtc.dev/openephemeris/apis/open-ephemeris-api.md) · [All operations](https://skmtc.dev/openephemeris/apis/open-ephemeris-api/llms.txt) · [OpenAPI document](https://skmtc.dev/openephemeris/apis/open-ephemeris-api/revisions/d195a769cb89?raw)