Mula Nakshatra - Java

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

Using the Mula topic in an application

Request the calculated nakshatra from the user’s actual inputs, then inspect its documented name and related fields. The synthetic request below can return a different nakshatra. Keep the computed result separate from editorial content about Mula; changing a URL or label does not change the calculation.

Nakshatra: request contract

The result is calculated from the supplied timestamp and location. A nakshatra name in a documentation URL does not choose the calculated result.

POST /v2/astrology/nakshatra · Operation guide · 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.

Java 17 or later, trusted server or CLI

import java.net.URI;
import java.net.http.*;
import java.time.Duration;

class Example {
  public static void main(String[] args) throws Exception {
    String key = System.getenv("VEDIKA_API_KEY");
    if (key == null || key.isBlank()) throw new IllegalStateException("Set VEDIKA_API_KEY");
    var request = HttpRequest.newBuilder(URI.create("https://api.vedika.io/v2/astrology/nakshatra"))
        .timeout(Duration.ofSeconds(20)).header("Authorization", "Bearer " + key)
        .header("Content-Type", "application/json")
        .POST(HttpRequest.BodyPublishers.ofString("{\"datetime\":\"2026-03-23T12:00:00\",\"latitude\":28.6139,\"longitude\":77.209,\"timezone\":\"+05:30\"}")).build();
    var result = HttpClient.newHttpClient().send(request, HttpResponse.BodyHandlers.ofString());
    if (result.statusCode() < 200 || result.statusCode() >= 300) throw new IllegalStateException("HTTP " + result.statusCode());
    System.out.println(result.body());
  }
}

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