Migration guide

Map the request.
Review the method.

Offline examples map documented DivineAPI Indian/Western and AstrologyAPI planets request fields into Cloud Astrology API calculation contracts. No vendor account, response copying or live competitor call is involved.

Fields that need an explicit decision

Map local date/time and coordinates. Supply the actual IANA timezone and confirm that its pinned historical offset matches the previous numeric tzone. Repeated clock times require fold; gaps fail. Do not infer a historical zone from a numeric offset.

Select the Cloud Astrology API zodiac/ayanamsa, house and node convention yourself. The example requires explicit method review and accepts a limited set of supported choices; it is not a full vendor adapter. Names, gender, display place, translation options and vendor secrets do not pass to the calculation request.

Expect a new output contract

Use named Cloud Astrology API fields, units, profiles, quotes and receipts. Compare your own authorized reference cases before switching customer traffic. These examples do not reproduce proprietary responses, text, undocumented methods, rounding or identifiers.

Safe migration sequence

  1. Inventory consumed fields and existing method settings.
  2. Convert synthetic requests and validate the new schema.
  3. Review timezone/DST, house, node and ayanamsa choices.
  4. Adapt your parser and verify outputs against authorized cases.
  5. Check quotas, retries, failures, async jobs and rollback before deployment.

Public documentation checked 16 November 2026. Source links accompany each mapping; provider contracts can change.