Mars Planet - Node.js

Planetary positions request example, documented inputs, server-side authentication and integration checks.

Locate Mars in a planetary-position result

This operation calculates the documented position data for the supplied timestamp and location. Inspect the returned collection for Mars, using the field names in the response reference. A topic name in this page’s URL is an application display choice, rather than an additional request parameter.

Planetary positions: request contract

Supply the calculation timestamp and location. Keep the returned coordinates and any display conventions separate from narrative interpretations added by your application.

POST /v2/astrology/planetary-positions · OpenAPI request and response schema

The values below are synthetic examples. They describe request wiring, rather than a measured result or an accuracy claim. Production requests use your account’s published billing terms; the sandbox provides fixed mock examples for development.

Inputs documented for this operation
FieldLocationTypeSchema requirement
datetimebodystringOptional in the request schema; provide it when your calculation needs it
latitudebodynumberOptional in the request schema; provide it when your calculation needs it
longitudebodynumberOptional in the request schema; provide it when your calculation needs it
timezonebodystringOptional in the request schema; provide it when your calculation needs it

Make the request safely

Set VEDIKA_API_KEY in the trusted server or command-line environment. Keep that key out of browser bundles, mobile builds, URLs and shared logs. The example runs in a trusted process; a mobile or browser application can call your own backend to keep the production credential private.

Node.js module: example.mjs

// Run on a trusted server with Node.js 22 or later.
const key = process.env.VEDIKA_API_KEY;
if (!key) throw new Error('Set VEDIKA_API_KEY on the server');
const response = await fetch("https://api.vedika.io/v2/astrology/planetary-positions", {
  method: 'POST',
  headers: { 'Authorization': 'Bearer ' + key, 'Content-Type': 'application/json' },
  body: "{\"datetime\":\"1990-05-15T10:30:00\",\"latitude\":19.07,\"longitude\":72.87,\"timezone\":\"+05:30\"}",
  signal: AbortSignal.timeout(20000)
});
const text = await response.text();
if (!response.ok) throw new Error('Request failed: HTTP ' + response.status);
console.log(JSON.parse(text));

Check the result before displaying it

  1. Validate the selected date, location and relevant calculation settings before making a production request.
  2. Check HTTP status and the operation-specific JSON schema. Keep errors and timeouts visible instead of displaying a previous or invented result.
  3. Retain only the inputs and result fields your feature needs. Use synthetic cases in public bug reports and avoid copying private birth details into logs.
  4. When caching, include every input that affects this operation and keep private results scoped to the appropriate user.

Continue with the quickstart, supported SDKs, current billing units and published technical evidence. Create production access through API-key signup.

Try the FREE Sandbox

978 mock operations for development. Production plans from $12/month.

Explore Sandbox →
⚡
Simple Integration
REST API with JSON responses
🔒
Credential handling
Keep production keys on your server
📊
Service Status
Live service status: vedika.io/status

Related Documentation