New Numerology API

Divisional charts (vargas)

Trimsamsa (D30) in Vedic astrology

Trimsamsa (D30) is one of the 16 divisional charts. Unlike most, it uses unequal parts: each sign is split into five parts of 5°, 5°, 8°, 7° and 5° in odd signs, and in the reverse order in even signs. Each part maps to a sign of the planet that rules it, Mars, Saturn, Jupiter, Mercury or Venus, so the Sun, the Moon, Rahu and Ketu never rule a part. The API describes its use as: misfortune and evils.

Updated

More terms in Divisional charts (vargas)

© API for Astrology (apiforastrology.com). "Glossary houses chart". All rights reserved. Not to be copied or reused.123456789101112A North Indian chart has 12 houses

Trimsamsa: how the API computes it

The trimsamsa, D30, is the second divisional chart that does not use equal parts. Each sign is split into five unequal parts (VG-06). Each part belongs to the sign of a ruling planet, not to a count from the sign.

The rulers are Mars, Saturn, Jupiter, Mercury and Venus. The Sun, the Moon, Rahu and Ketu never rule a trimsamsa part. Odd signs and even signs use the parts in opposite order. So the same degree gives a different ruler in Aries than in Taurus.

Tradition reads the chart for misfortune and for hardships. The API lists misfortune and evils in the signifies field. That wording is harsh, so soften it in your app.

Present it as a part of the chart to be aware of. POST /v1/chart/D30 returns the ascendant (rising sign) and every planet with the sign and house in this chart. This chart shows why you should call the API instead of counting by hand.

There is no simple step to repeat from one part to the next.

Get it from the API

Any of the 16 divisional charts (D1 to D60). Here is the call to API for Astrology (apiforastrology.com) for our sample, John Doe, born Aug 15, 1990, 10:30 AM, New York.

POST /v1/chart/D30

# John Doe, born Aug 15, 1990, 10:30 AM, New York
curl -X POST "https://apiforastrology.com/api/astrology/v1/chart/D30" \
  -H "Authorization: Bearer $ASTROLOGY_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"year":1990,"month":8,"day":15,"hour":10,"minute":30,"second":0,"latitude":40.7128,"longitude":-74.006,"timezone":"America/New_York"}'

Where the API returns it

POST/v1/chart/{division}Any of the 16 divisional charts (D1 to D60)
GET/v1/metaSupported options and limits

Feature page: Kundli and birth charts. Who uses it: Astrologer consultation platforms. The classical rules the API follows are in the rulebook.

How we check the numbers

Every value here starts from planet positions worked out from NASA JPL planet data (DE440). We test them against NASA JPL Horizons, NASA's planet position service. On 25,571 positions from 1850 to 2149, the Sun and planets agree within 0.001 arc seconds. The Moon agrees within 0.011. On 2,000 random birth charts, the rising sign agrees with Swiss Ephemeris within 0.004 arc seconds. An arc second is 1/3,600 of a degree. A practicing astrologer reviews the rules behind these answers. See how we test.

Related terms

Astrology API

Get these values from the API

Create a free test key and call any endpoint on this page. Or try a request in the API reference first.

Get a free API keyOpen the API reference

Your first answer

John Doe, New York

POST /v1/planets200 OK
  • RisingVirgoHast
  • SunCancerAshlesha
  • MoonTaurusMrigashira
  • MarsAriesKrittika

Real API output. A free test key gets the same answer.

  1. 01

    Test key: 1,000 test calls a month to build with

  2. 02

    Free plan: 2,000 live calls a month, no card needed

  3. 03

    Open rules: every rule is published, so you can check any answer