Virgo Horoscope - TypeScript
Daily horoscope request example, documented inputs, server-side authentication and integration checks.
Request a Virgo daily horoscope
The request below explicitly selects Virgo using the sign query parameter. This is a sign-based daily response. A birth-chart feature needs its own birth inputs and operation; do not label this result as a personalized natal reading.
Daily horoscope: request contract
This example requests a sign-based daily horoscope. Choose the documented sign value and date; this request does not produce a personalized birth-chart reading or a weekly forecast.
GET /v2/astrology/horoscope/daily · 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.
| Field | Location | Type | Schema requirement |
|---|---|---|---|
sign | query | string | Required by the request schema |
date | query | string | Optional in the request schema; provide it when your calculation needs it |
timezone | query | string | Optional 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.
TypeScript module in your Node.js project
export {};
// Run on a trusted server with Node.js 22 or later.
const key: string | undefined = 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/horoscope/daily?sign=virgo", {
method: 'GET',
headers: { 'Authorization': 'Bearer ' + key },
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
- Validate the selected date, location and relevant calculation settings before making a production request.
- Check HTTP status and the operation-specific JSON schema. Keep errors and timeouts visible instead of displaying a previous or invented result.
- 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.
- 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 →