Skip to content
AstroWay/api v2.325.0 · docs
all systems operational

Prashna: yes/no indicators

POST
/vedic/prashna/analysis
request.sh
curl -X POST https://api.astroway.info/v1/vedic/prashna/analysis \
-H "X-Api-Key: aw_live_..." \
-H "Content-Type: application/json" \
-d '{ "date": "1962-11-06", "time": "09:20:00", "timezoneOffset": 5.5, "latitude": 12.9716, "longitude": 77.5946, "ayanamsa": "raman", "category": "relationship" }'

Prasna Tantra indicators for one category (relationship, career, travel, lost-item, litigation, general; health is refused): the house of the question and its lord, the ascendant, the Lagna lord and the Moon, Tajika aspects, Ithasala, Easarapha and Kamboola between the Lagna lord, the significator and the Moon, and the category’s own stanzas. Each indicator has its rule, what the chart shows, whether it fired and its source; then an equal-weight tally, the II.5-8 success grade and the II.10-12 timing. No prediction text.

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

Example
planets.name,planets.longitude
precision
integer
<= 15

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.

Example
4
Idempotency-Key
string
>= 1 characters <= 255 characters /^[\x21-\x7E]+$/

Unique per logical operation, kept across retries. For 24 hours from the first request, a repeat with the same key, method, path, body and query string returns the stored response with Idempotent-Replayed: true and costs 0 credits. The same key with a different body or query string is a 409 IDEMPOTENCY_KEY_REUSED; a repeat while the first is still running is a 409 IDEMPOTENCY_IN_PROGRESS. Only 2xx responses are kept. See /idempotency/.

Example
01HXY2A7ZM0ABCDEF
Media type application/json

The Prashna chart input plus the category of the question.

object
date required

Date of the question, YYYY-MM-DD, local.

string
/^\d{4}-\d{2}-\d{2}$/
time required

Time of the question, HH:mm:ss, local.

string
/^\d{2}:\d{2}(:\d{2})?$/
timezoneOffset

Hours from UTC at the given moment, not minutes. Fractional zones are hours too: 5.5 for India, 5.75 for Nepal, -3.5 for Newfoundland. Defaults to 0, meaning UTC. Ignored when timezone is sent.

number
0 nullable >= -14 <= 14
timezone

IANA zone name such as Europe/Kyiv, or auto to look the zone up from latitude and longitude. The server takes the offset that zone kept at this local date and time, summer time included, and uses it in place of timezoneOffset. A clock time that happened twice takes the first occurrence; one skipped when clocks went forward takes the offset from before the change. Abbreviations such as EST are refused. Before 1970 the tz database is not reliable for every place, so send timezoneOffset when the local clock is known.

string
latitude required
number
>= -90 <= 90
longitude required
number
>= -180 <= 180
ayanamsaId
number
nullable
ayanamsa

Sidereal school by name. Lahiri when omitted. Equivalent to ayanamsaId; send either.

string
Allowed values: fagan-bradley lahiri de-luce raman krishnamurti kp yukteshwar jn-bhasin true-citra djwhal-khul
arudhaSign

Arudha: the sign (1 Aries .. 12 Pisces) of the direction the querent faces or the square of the chakra the querent touches (Prasna Marga II.7-11). Omit it and the Udaya Lagna stands in for it (IX.30-31).

integer
>= 1 <= 12
number

A number 1-108 from the querent: its navamsa fixes the Arudha sign. Send arudhaSign or number, not both. KP’s 1-249 number is /v1/vedic/kp/horary.

integer
>= 1 <= 108
sphutaGulika

Which point enters Trisphuta. mandi (default): the Prasna Marga author takes Gulika by the Mandi ghatika method (translator’s note to V.14-16). gulika: the end of Saturn’s eighth part.

string
Allowed values: mandi gulika
category required

The subject of the question: relationship, career, travel, lost-item, litigation, general. It picks the house of the question and its lord (the significator). Health is not offered.

string
Allowed values: relationship career travel lost-item litigation general
Example
{
"date": "1962-11-06",
"time": "09:20:00",
"timezoneOffset": 5.5,
"latitude": 12.9716,
"longitude": 77.5946,
"ayanamsa": "raman",
"category": "relationship"
}

Successful calculation

Media type application/json
object
ok
boolean
data
object
method
string
nullable
category
string
nullable
lagna
object
sign
string
nullable
lord
string
nullable
houseOfQuestion
object
house
number
nullable
sign
string
nullable
why
string
nullable
source
string
nullable
significator
object
graha
number
nullable
name
string
nullable
house
number
nullable
sameAsLagnaLord
boolean
nullable
moon
object
waxing
boolean
nullable
house
number
nullable
afflicted
boolean
nullable
indicators
Array<object>
nullable
object
id
string
nullable
rule
string
nullable
effect
string
nullable
fired
boolean
nullable
observed
string
nullable
source
string
nullable
tally
object
favourable
number
nullable
unfavourable
number
nullable
checked
number
nullable
leaning
string
nullable
weights
string
nullable
mixedReading
string
nullable
successGrade
object
percent
number
nullable
why
string
nullable
source
string
nullable
timing
object
value
string
nullable
source
string
nullable
chart
object
udayaLagna
object
longitude
number
nullable
sign
number
nullable
signName
string
nullable
degree
number
nullable
nakshatra
number
nullable
nakshatraName
string
nullable
lord
number
nullable
lordName
string
nullable
sirshodaya
boolean
nullable
sources
object
ptIthasala
object
text
string
nullable
ref
string
nullable
status
string
nullable
notes
string
nullable
Example
{
"ok": true,
"data": {
"method": "prashna-analysis",
"category": "relationship",
"lagna": {
"sign": "Sagittarius",
"lord": "Jupiter"
},
"houseOfQuestion": {
"house": 7,
"sign": "Gemini",
"why": "7th: spouse, partner",
"source": "ptMarriage"
},
"significator": {
"graha": 2,
"name": "Mercury",
"house": 11,
"sameAsLagnaLord": false
},
"moon": {
"waxing": true,
"house": 3,
"afflicted": false
},
"indicators": [
{
"id": "ithasala-lords",
"rule": "Ithasala (applying) between the Lagna lord and the significator",
"effect": "favourable",
"fired": true,
"observed": "trine, ithasala, gap 1.1961 within orb 8",
"source": "ptIthasala"
},
{
"id": "significator-afflicted",
"rule": "The significator Mercury is joined or aspected (4th, 7th, 10th) by malefics or combust",
"effect": "unfavourable",
"fired": true,
"observed": "Mercury in Libra, combust",
"source": "ptAfflicted"
}
],
"tally": {
"favourable": 6,
"unfavourable": 2,
"checked": 18,
"leaning": "favourable",
"weights": "one point per fired indicator; equal weights are ours, the texts give none",
"mixedReading": "PT ch. II st. 2: where the influences are mixed, success comes after initial setbacks"
},
"successGrade": {
"percent": 100,
"why": "the ascendant is joined or aspected by its lord",
"source": "ptGrades"
},
"timing": {
"value": "delayed",
"source": "ptWhen"
},
"chart": {
"udayaLagna": {
"longitude": 242.8551,
"sign": 8,
"signName": "Sagittarius",
"degree": 2.8551,
"nakshatra": 19,
"nakshatraName": "Mula",
"lord": 5,
"lordName": "Jupiter",
"sirshodaya": false
}
},
"sources": {
"ptIthasala": {
"text": "Prasna Tantra of Neelakanta, tr. B.V. Raman, 2nd ed., Raman Publications, Bangalore (preface 1972)",
"ref": "ch. IV st. 54-55 and notes (the faster planet behind the slower in a Tajika aspect within orb; within a degree it is complete; speed order Saturn, Jupiter, Mars, Sun, Venus, Mercury, Moon)",
"status": "verse"
}
},
"notes": "Indicators are the classical rules with what the chart shows for each; no prediction text is written. The Udaya Lagna is used, as Prasna Tantra does; the full Prasna Marga chart is /v1/vedic/prashna/chart."
}
}

Validation error

Media type application/json
Example
{
"ok": false,
"error": {
"code": "INVALID_INPUT",
"message": "Validation failed: date: Date must be YYYY-MM-DD",
"details": [
{
"path": "date",
"message": "Date must be YYYY-MM-DD"
}
]
}
}

Missing or invalid API key

Media type application/json
Example
{
"ok": false,
"error": {
"code": "INVALID_API_KEY",
"message": "Invalid API key"
}
}