AstroApp REST APIs: Output Examples

Table of Contents

• Chart Data
• Locations
• Locations nearby
• Statistics by Sign
• Dignities
• Returns
• Progressions
• Transits to Natal Charts
• Static Values
• JSON Requests Properties
  
• JSON Response Data
  

---

Chart Data

Endpoint: apis/chart
Request: chartData

Locations

Endpoint: apis/locations/name?cityName=Sunnyv&stateCode=ca&countryID=1
Request: locations by name

Location Proximity Search

Endpoint: apis/locations/coord?lat=37.3688&lng=-122.036
Request: locations by coordinates (proximity searches)

Statistics by Sign

Endpoint: apis/stats/bysign
Request: number of planets in signs

Dignities

Endpoint: apis/stats/bysign
Request: dignities

Returns

Endpoint: apis/returns
Request: returns

Progressions

Endpoint: apis/progressions
Request: progressions

  ...

Transits to Natal

Endpoint: apis/transits/natal
Request: transits to natal chart

....


Static values:

Planets:

• 0: Sun
• 1: Moon
• 2: Mercury
• 3: Venus
• 4: Mars
• 5: Jupiter
• 6: Saturn
• 7: Uranus
• 8: Neptune
• 9: Pluto
• 10: Mean Node
• 11: True Node
• 15: Chiron
  

Zodiac:

• 100: Tropical
• 1: Fagan/Bradley
• 2: Lahiri
• 3: Raman
  

House Systems:

• 1: Placidus
• 2: Koch
• 3: Porphyrius
• 4: Regiomontanus
• 20: Whole Sign

Coordinate Systems:

• G: Geocentric (default)
• T: Topocentric
• H: Heliocentric

Aspects:

• 0 - conjunction
• 30 - semi-sextile
• 45 - semi-square
  
• 51.5 - septile
  
• 60 - sextile
• 72 - quintile
• 90 - square
• 120 - trine
• 135 - sesquisquare
  
• 150 - quincunx
• 180 - opposition
  

The APIs will accept any angle. You don't have to be limited to major aspects only.

---

JSON Request Details

        "chartData":
        {
            "chartName":"Horoscope REST API",    //Name
            "chartDate":"1964-08-05T09:00:00",       //Date in ISO format
            "lng":"15.501",                                     //Geographic Longitude of the location at birth (or chart location in general). Decimal value, negative values represent West longitude, positive values are for the East longitude
            "lat":"27.50",                                        //Geographic Latitude. Decimal value, negative values represent South latitude, positive values are for the North longitude
            "elev":1,                                               //Elevation of the location at birth. Leave as 0 if not known
            "tz":"Australia/Brisbane",                       //Time Zone
            "zodiacID":100,                                    //100 is the default value representing Tropical Zodiac
            "houseSystemID":1,                             //House System. Refer to the supported House System values above
            "coordSys":"G",                                   //Coordinates system used for calculations. Refer to the Coordinates System values above
            "version":1                                           //Chart version - use this if you want to support tracking of the chart updates.
        },


"calcRequestProps":
    {
        "needImage":"Y",                                    //Set to Y if you want APIs to generate an image of the chart. The link to the chart image will be returned in Response. For performance reasons, it's recommended to keep this as "N" if chart image is not required.
        "needAspects":"Y"                                  //Set to Y if you want aspects data to be provided in Response. Otherwise keep it as "N" (no).
    },

"params":{
        "objects": [
            0,1,2,3,4,5,6,7,8,9,11,13,15             //Object IDs to be included in calculations. Please refer to the list of Planet IDs above.
        ],
       "aspects":[                                          //Aspect angles. Integer or decimal values indicating aspects to include in Response. For example, 0 value means conjunction (0 degrees of angular separation), 180 means opposition, 120 - trine, and so on.
            {
                "angle":0,
                "orb":10                                      //Orb - is the integer or decimal value indicating precision of the aspect calculations to be considered. For example, if you specify orb as 10 for conjunctions, this means two planets will be considered in conjunction if their angular separation is 0 degrees +/- 10 degrees. So, 2 planets with 9 degrees of angular separation would still be considered conjunct in this scenario.
            },
            {
                "angle":45,
                "orb":1
            },
            {
                "angle":60,
                "orb":5
            },
            {
                "angle":90,
                "orb":8
            },
            {
                "angle":120,
                "orb":9
            },
            {
                "angle":135,
                "orb":2
            },
            {
                "angle":150,
                "orb":3
            },
            {
                "angle":180,
                "orb":10
            }
        ]
    }

JSON Response Details

Objects position/details representation

"objects": [
Statistics by Sign
Each number in the output array represents the number of planets in corresponding signs (1 - Aries, 2 - Taurus, 3 - Gemini, 4 - Cancer, 5 - Leo, 6 - Virgo, 7 - Libra, 8 - Scorpio, 9 - Sagittarius, 10 - Capricorn, 11 - Aquarius; 12 - Pisces. The signs start with index 1 in the array. For example, position with index=1 in the array corresponds to Aries and Aries has 0 planets in it; position #2 represents Taurus and Taurus contains 1 planet in it.

Events Results (Progressions, Transits, etc)
"results": [

Editions:

• The AstroApp REST APIs are available as part of the special APIs subscription. Please contact our Support Team for details and pricing.