The Short Version
Start an astrology integration with POST /v1/panchang/daily. It gives the day-level Panchang context most astrology screens need: Tithi, Nakshatra, Yoga, Karana, sunrise-sensitive day framing, and metadata that helps explain where and when the response was calculated.
Use monthly and yearly responses only when the product needs calendar grids, upcoming day planning, or batch-like views. Keep protected calls on your backend so API keys never ship in browser or mobile client code.
Where Panchang Data Fits
- Today screens: show Tithi, Nakshatra, sunrise, sunset, and day notes alongside horoscope content.
- Date detail pages: support user-selected dates with a complete daily Panchang response.
- Muhurat flows: expose auspicious windows only when the active plan includes Muhurat access.
- Calendar browsing: use monthly responses when users scan upcoming days instead of opening one date at a time.
Astrology users notice differences. Display the selected city or resolved timezone where it helps, and keep request IDs in support logs so mismatch reports can be traced.
Location and Timezone Choices
Most astrology apps should begin with supported city lookup because it gives users a familiar selection model and keeps location behavior predictable. Latitude and longitude lookup is better for advanced flows where exact coordinates are important and the plan supports it.
Do not let the frontend silently substitute one city for another. If you use a default location, label it clearly and let the user change it before relying on the result for personal guidance.
Quota and Caching
Daily responses are the natural unit for most astrology interactions. Cache repeated requests for the same date and location on your backend when your product has high traffic. Monthly and yearly calls should be reserved for screens that truly need a larger date range.
Use response headers such as X-Request-ID, X-Quota-Cost, X-Data-Source, and X-Cache-Age when debugging quota usage, cache behavior, or support reports.
Plan Gates to Plan Around
Daily Panchang is available across plans. Astrology apps often need paid-tier features such as monthly Panchang, Muhurat timings, faith filters, latitude and longitude lookup, and richer festival layers. Build UI states that handle unavailable fields as plan-gated features, not broken data.
Before adding bulk calendar views, make the single-date experience easy to inspect. A clear daily screen is the best foundation for user trust and support debugging.
Launch Testing Checklist
- Test today, tomorrow, and user-selected dates for your highest-traffic cities.
- Verify Tithi and Nakshatra boundary behavior around sunrise and day transitions.
- Confirm plan-gated Muhurat and coordinate lookup behavior.
- Capture request IDs for every support-visible calculation mismatch.
- Compare a few important dates with your product's chosen reference sources before launch.