search

Copy page

Copy page as Markdown for LLMs

View as Markdown

View this page as plain text


Open in ChatGPT

Ask ChatGPT about this page

Open in Claude

Ask Claude about this page

Planets Combustion Transit API

The Planets Combustion Transit API provides detailed insights into the combustion phases of planets — periods when a planet comes very close to the Sun, losing its apparent brightness and influence in Vedic astrology. This API returns exact timestamps when combustion starts and ends for selected planets, helping astrologers identify crucial windows of weakened planetary strength.


Step-by-Step Planets Combustion Transit API Postman Testing Integration

For detailed setup and testing instructions, visit the official guide below:
Step by Step Find Grah Gochar API Postman Testing Integration
https://support.divineapi.com/indian-astrology-apis/testing-panchang-api-find-grah-gochar-api-using-postman


Supported Language Codes

You can request responses in multiple Indian languages by specifying the lan parameter in the request body.

Reference Article:
https://support.divineapi.com/general-api-support/translating-an-indian-vedic-apis-into-a-different-language

CodeLanguage
enEnglish
hiHindi
bnBengali
maMarathi
tmTamil
tlTelugu
mlMalayalam
knKannada

Guide:
If lan is omitted, the response defaults to English (en).


Supported Planets

This API supports combustion analysis for the following planets:

mercury
venus
mars
jupiter
saturn
uranus
neptune
pluto

Pass one of these as the :planet parameter in the request URL.


API Endpoint

POST https://astroapi-3.divineapi.com/indian-api/v1/planet-combustion-transit/:planet

Replace :planet with the desired planet name.
Example:
https://astroapi-3.divineapi.com/indian-api/v1/planet-combustion-transit/mars


Headers

NameTypeDescription
Authorization*StringYour API Access Token. Example: Bearer {token}

Request Body

NameTypeRequiredDescription
api_keyStringYesYour Divine API key.
monthIntegerYesMonth of combustion transit calculation. Example: 11.
yearIntegerYesYear of combustion transit calculation. Example: 2025.
placeStringYesName of the place. Example: New Delhi.
latFloatYesLatitude of the place. Example: 28.6139.
lonFloatYesLongitude of the place. Example: 77.2090.
tzoneFloatYesTimezone offset. Example: 5.5. Refer to Timezone Guide.
lanStringNoLanguage code from the supported list. Default is en.

200: OK Nakshatra Transit successfully

{
    "success": 1,
    "data": {
        "message": "Mars have 1 transit in November 2025.",
        "transit": [
            {
                "date": "2025-11-06 23:52:00",
                "combustion": "Start"
            }
        ]
    }
}

{
    "success": 1,
    "data": {
        "message": "Mars have 1 transit in March 2026.",
        "transit": [
            {
                "date": "2026-03-26 14:08:00",
                "combustion": "End"
            }
        ]
    }
}

Response Field Description

success
Indicates whether the request was successful (1 for success).

message
Provides a summary of how many combustion events occurred for the planet during the specified month.

transit
Array containing combustion event details.

Each object inside transit includes:

FieldDescription
dateThe exact timestamp (in YYYY-MM-DD HH:MM:SS format) marking the start or end of combustion.
combustionIndicates whether the event is a Start or End of the combustion period.

Interpretation Guide

Combustion Start:
Marks the moment when the planet comes within proximity to the Sun and begins to lose visibility and power.

Combustion End:
Represents the point where the planet moves far enough from the Sun to regain its radiance and strength.

Use Case:
These periods are crucial in chart analysis, signifying when planetary effects are subdued and not suitable for auspicious activities related to that planet.


Example Code Implementations

Below are example implementations in various programming environments.


cURL

curl --location 'https://astroapi-3.divineapi.com/indian-api/v1/planet-combustion-transit/:planet' \
--header 'Authorization: Bearer {Your Auth Token}' \
--form 'api_key="{Your API Key}"' \
--form 'month="05"' \
--form 'year="2023"' \
--form 'place="New Delhi"' \
--form 'lat="28.6139"' \
--form 'lon="77.2090"' \
--form 'tzone="5.5"' \
--form 'lan="en"'

Node.js

var request = require('request');
var options = {
  'method': 'POST',
  'url': 'https://astroapi-3.divineapi.com/indian-api/v1/planet-combustion-transit/:planet',
  'headers': {
    'Authorization': 'Bearer {Your Auth Token}'
  },
  formData: {
    'api_key': '{Your API Key}',
    'month': '05',
    'year': '2023',
    'place': 'New Delhi',
    'lat': '28.6139',
    'lon': '77.2090',
    'tzone': '5.5',
    'lan': 'en'
  }
};
request(options, function (error, response) {
  if (error) throw new Error(error);
  console.log(response.body);
});

JavaScript (jQuery AJAX)

var form = new FormData();
form.append("api_key", "{Your API Key}");
form.append("month", "05");
form.append("year", "2023");
form.append("place", "New Delhi");
form.append("lat", "28.6139");
form.append("lon", "77.2090");
form.append("tzone", "5.5");
form.append("lan", "en");

var settings = {
  "url": "https://astroapi-3.divineapi.com/indian-api/v1/planet-combustion-transitplanet-combustion-transit/:planet",
  "method": "POST",
  "timeout": 0,
  "headers": {
    "Authorization": "Bearer {Your Auth Token}"
  },
  "processData": false,
  "mimeType": "multipart/form-data",
  "contentType": false,
  "data": form
};

$.ajax(settings).done(function (response) {
  console.log(response);
});

Python

import requests

url = "https://astroapi-3.divineapi.com/indian-api/v1/planet-combustion-transit/:planet"

payload = {'api_key': '{Your API Key}',
'month': '05',
'year': '2023',
'place': 'New Delhi',
'lat': '28.6139',
'lon': '77.2090',
'tzone': '5.5',
'lan': 'en'}

headers = {
  'Authorization': 'Bearer {Your Auth Token}'
}

response = requests.request("POST", url, headers=headers, data=payload,)

print(response.text)


Implementation Notes

Always include both Authorization (Bearer token) and api_key in your request.

Replace :planet in the endpoint URL with the actual planet name (e.g., mercury, venus, mars).

Ensure correct tzone, lat, and lon values for accurate astronomical calculations.

The API can return two types of records for a single planet in a given year — one for the start and another for the end of combustion.

Useful for determining favorable timelines for rituals, investments, or career decisions based on planetary strength.