SEARCH ASTRO INSIGHT API DOCS
The Biorhythm Details By Date API provides biorhythm related data and calculations using Vedic Astrology principles. This endpoint is designed for astrology applications, kundli generation, horoscope platforms, and developer integrations requiring accurate JSON-based responses and scalable REST API access.
https://json.astroinsightapi.com/api/v1/biorhythm/biorhythm-details-by-date
en
hi
ma
Methodology and astrological context for Biorhythm Details By Date.
The Biorhythm Details By Date API calculates a person's biorhythm cycles for a specific target date, rather than the current day. By supplying both birth details and a separate reference date, this endpoint enables historical lookups, future projections, and date-specific biorhythm analysis — making it ideal for planning, retrospective insights, and time-based comparisons.
This endpoint computes the state of a person's biorhythm cycles — physical, emotional, intellectual, and secondary — as they stand on a user-specified date. Unlike a standard biorhythm endpoint that calculates cycles for today, this variant accepts an explicit target date (cDay, cMonth, cYear) alongside the person's birth details, allowing the caller to query biorhythm data for any point in time: past, present, or future.
Multi-language support is available via the Accept-Language header, and the Ayanamsha system can be specified through the X-Ayanamsha header for consistency with other astrology-based endpoints on the platform.
The response provides detailed biorhythm cycle data for the specified target date, which may include:
Payload specifications for JSON request body.
| Parameter | Type | Description & Example |
|---|---|---|
|
day
Required
|
integer |
Day of birth (1–31).
Example:
15
|
|
month
Required
|
integer |
Month of birth (1–12).
Example:
9
|
|
year
Required
|
integer |
Year of birth (e.g., 1994).
Example:
1994
|
|
hour
Required
|
integer |
Hour of birth in 24-hour format (0–23).
Example:
12
|
|
min
Required
|
integer |
Minute of birth (0–59).
Example:
30
|
|
sec
Optional
|
integer |
Second of birth (0–59). Optional. If not provided, it is considered as 0.
Example:
30
|
|
lat
Required
|
float |
Latitude of the birth location.
Example:
28.6139
|
|
lon
Required
|
float |
Longitude of the birth location.
Example:
77.1025
|
|
tzone
Optional
|
float |
Timezone offset from UTC. Optional. If not provided, it is considered as 5.5 (IST).
Example:
5.5
|
|
cDay
Required
|
integer |
Day of birth (1–31).
Example:
15
|
|
cMonth
Required
|
integer |
Month of birth (1–12).
Example:
9
|
|
cYear
Required
|
integer |
Year of birth (e.g., 2030).
Example:
2030
|
| Header Key | Value / Format | Description |
|---|---|---|
|
Authorization
Required
|
Basic {base64} |
Base64 encoded string of CLIENT_ID:CLIENT_SECRET. |
|
Content-Type
Required
|
application/json |
Specifies JSON payload format in request body. |
|
Accept-Language
Optional
|
en, hi, ta, te... |
Returns localized astrology output. Default: en |
|
X-Ayanamsha
Optional
|
lahiri, raman, krishnamurti... |
Ayanamsha system: lahiri, raman, fagan_bradley, usha_shashi, krishnamurti, djwhal_khul, yukteshwar, jn_bhasin, suryasiddhanta, aryabhata. Default: lahiri |
Explore complementary endpoints in this category.
Comprehensive developer guidance for Biorhythm Details By Date.
The Biorhythm Details By Date API provides authentic Biorhythm calculations based on Vedic astrology algorithms. It returns structured JSON data containing detailed planetary positions, house calculations, and astrological parameters suitable for Kundli apps, astrology websites, and developer applications.
The Biorhythm Details By Date API requires standard Vedic birth details: day, month, year, hour, min, sec, latitude (lat), longitude (lon), and timezone (tzone). All parameters can be passed in the JSON request body.
Each calculation request to Biorhythm Details By Date consumes 1 API credit. The endpoint delivers high performance with an average response time of ~58ms.
Authenticate using HTTP Basic Authentication by including your Base64 encoded client_id:client_secret credentials in the Authorization header (Authorization: Basic BASE64(client_id:client_secret)).
Yes! The API supports multiple languages including English, Hindi, Marathi. Pass your desired language code (e.g. 'hi' for Hindi, 'ta' for Tamil, 'en' for English) in the Accept-Language request header.
Supported Ayanamshas include NC Lahiri (Default), BV Raman, Krishnamurti (KP), Fagan Bradley, Usha Shashi, Djwhal Khul, Sri Yukteshwar, JN Bhasin, Surya Siddhanta, and Aryabhata. Specify your choice using the X-Ayanamsha header.
The API returns clean JSON UTF-8 output. Successful requests return HTTP 200 OK with the computed data payload. Parameter validation errors return HTTP 422 with actionable error messages.