API de Astrologia

Geração de mapa natal, posições planetárias, previsões de trânsito diárias/semanais/mensais, compatibilidade sinástrica, previsões de vida, fases da lua, métricas lunares e dados do calendário lunar.

99.9 % Disponibilidade
Resposta
20 req/s
0.05 Créditos / requisição

Natal Chart


POST https://api.yeb.to/v1/astrology/natal-chart
ParâmetroTipoObrig.Descrição
api_key string sim Your API key
birth_date string sim Date of birth in YYYY-MM-DD format
birth_time string opc. Time of birth in HH:MM (24h). Enables rising sign & house placements
location string opc. Birth location (city name or coordinates). Improves time zone & latitude accuracy
language string opc. Language for the AI reading (ISO 639-1, e.g. en, es). Default: en

Exemplo

curl -X POST https://api.yeb.to/v1/astrology/natal-chart \
  -H "Content-Type: application/json" \
  -d '{
  "api_key": "YOUR_KEY",
  "birth_date": "1990-04-15",
  "birth_time": "14:30",
  "location": "New York",
  "language": "en"
}'

Exemplo de resposta

{
  "computed_data": {
    "sun": { "sign": "aries", "degree": 25.4 },
    "moon": { "sign": "cancer", "degree": 12.7 },
    "rising": { "sign": "leo", "degree": 3.2 },
    "planets": {
      "mercury": { "sign": "pisces", "degree": 18.9 },
      "venus": { "sign": "taurus", "degree": 7.3 },
      "mars": { "sign": "capricorn", "degree": 22.1 }
    },
    "aspects": [
      { "planet_a": "sun", "planet_b": "moon", "type": "square", "orb": 2.3 }
    ]
  },
  "reading": {
    "sun_sign": "Your Aries Sun gives you a pioneering spirit...",
    "moon_sign": "With Moon in Cancer, your emotional world is rich...",
    "rising_sign": "Leo rising presents a confident, warm exterior...",
    "key_aspects": "The Sun-Moon square creates dynamic tension...",
    "overall": "Your chart reveals a bold personality..."
  },
  "response_code": 200,
  "response_time_ms": 2450
}
{"error":"birth_date is required","code":422}

Códigos de resposta

CódigoDescrição
200 SuccessRequisição processada OK.
400 Bad RequestValidação de entrada falhou.
401 UnauthorizedChave API em falta ou incorreta.
403 ForbiddenChave inativa ou não permitida.
429 Rate LimitDemasiadas requisições.
500 Server ErrorErro inesperado.

Natal Chart

astrology/natal-chart 0.0500 credits

Parameters

API Key
body · string · required
Birth Date
body · string · required
Birth Time
body · string
Location
body · string
Language
body · string

Code Samples


                
                
                
            

Response

Status:
Headers

                
Body

                

Planetary Positions


POST https://api.yeb.to/v1/astrology/planetary-positions
ParâmetroTipoObrig.Descrição
api_key string sim Your API key
birth_date string opc. Date in YYYY-MM-DD format. Either birth_date or date is required
date string opc. Date in YYYY-MM-DD format. Either birth_date or date is required
birth_time string opc. Time in HH:MM (24h) for more precise positions
location string opc. City name or coordinates for latitude/longitude corrections

Exemplo

curl -X POST https://api.yeb.to/v1/astrology/planetary-positions \
  -H "Content-Type: application/json" \
  -d '{
  "api_key": "YOUR_KEY",
  "date": "2026-02-20"
}'

Exemplo de resposta

{
  "sun": { "sign": "pisces", "degree": 1.23, "retrograde": false },
  "moon": { "sign": "scorpio", "degree": 15.67, "retrograde": false },
  "mercury": { "sign": "aquarius", "degree": 28.45, "retrograde": false },
  "venus": { "sign": "aries", "degree": 5.12, "retrograde": false },
  "mars": { "sign": "gemini", "degree": 18.34, "retrograde": false },
  "jupiter": { "sign": "cancer", "degree": 11.89, "retrograde": false },
  "saturn": { "sign": "pisces", "degree": 22.56, "retrograde": false },
  "response_code": 200,
  "response_time_ms": 120
}
{"error":"birth_date or date is required","code":422}

Códigos de resposta

CódigoDescrição
200 SuccessRequisição processada OK.
400 Bad RequestValidação de entrada falhou.
401 UnauthorizedChave API em falta ou incorreta.
403 ForbiddenChave inativa ou não permitida.
429 Rate LimitDemasiadas requisições.
500 Server ErrorErro inesperado.

Planetary Positions

astrology/planetary-positions 0.0050 credits

Parameters

API Key
body · string · required
Birth Date
body · string
Date
body · string
Birth Time
body · string
Location
body · string

Code Samples


                
                
                
            

Response

Status:
Headers

                
Body

                

Daily Transit


POST https://api.yeb.to/v1/astrology/daily-transit
ParâmetroTipoObrig.Descrição
api_key string sim Your API key
sign string sim Zodiac sign (lowercase): aries, taurus, gemini, cancer, leo, virgo, libra, scorpio, sagittarius, capricorn, aquarius, pisces
date string opc. Date in YYYY-MM-DD format. Default: today
language string opc. Language for the AI reading (ISO 639-1). Default: en

Exemplo

curl -X POST https://api.yeb.to/v1/astrology/daily-transit \
  -H "Content-Type: application/json" \
  -d '{
  "api_key": "YOUR_KEY",
  "sign": "aries",
  "date": "2026-02-20"
}'

Exemplo de resposta

{
  "computed_data": {
    "sign": "aries",
    "period": "daily",
    "date": "2026-02-20"
  },
  "reading": {
    "overview": "Mars in your sign brings assertive energy...",
    "love": "Venus trine your Sun...",
    "career": "Mercury supports clear thinking...",
    "key_transit": "Mars conjunct natal Sun",
    "energy_level": "high"
  },
  "response_code": 200,
  "response_time_ms": 1850
}
{"error":"sign is required for generic transit forecasts","code":422}

Códigos de resposta

CódigoDescrição
200 SuccessRequisição processada OK.
400 Bad RequestValidação de entrada falhou.
401 UnauthorizedChave API em falta ou incorreta.
403 ForbiddenChave inativa ou não permitida.
429 Rate LimitDemasiadas requisições.
500 Server ErrorErro inesperado.

Daily Transit

astrology/daily-transit 0.0200 credits

Parameters

API Key
body · string · required
Zodiac Sign
body · string · required
Date
body · string
Language
body · string

Code Samples


                
                
                
            

Response

Status:
Headers

                
Body

                

Weekly Transit


POST https://api.yeb.to/v1/astrology/weekly-transit
ParâmetroTipoObrig.Descrição
api_key string sim Your API key
sign string sim Zodiac sign (lowercase): aries, taurus, gemini, cancer, leo, virgo, libra, scorpio, sagittarius, capricorn, aquarius, pisces
language string opc. Language for the AI reading (ISO 639-1). Default: en

Exemplo

curl -X POST https://api.yeb.to/v1/astrology/weekly-transit \
  -H "Content-Type: application/json" \
  -d '{
  "api_key": "YOUR_KEY",
  "sign": "aries"
}'

Exemplo de resposta

{
  "computed_data": {
    "sign": "aries",
    "period": "weekly"
  },
  "reading": {
    "overview": "This week brings a surge of creative energy as Venus enters your fifth house...",
    "highlights": [
      "Mon: Mercury trine Jupiter opens doors for negotiations",
      "Wed: Mars sextile Venus favors romantic connections",
      "Fri: Sun conjunct Neptune heightens intuition"
    ],
    "challenge_day": "Thursday",
    "best_day": "Saturday"
  },
  "response_code": 200,
  "response_time_ms": 2100
}
{"error":"sign is required for generic transit forecasts","code":422}

Códigos de resposta

CódigoDescrição
200 SuccessRequisição processada OK.
400 Bad RequestValidação de entrada falhou.
401 UnauthorizedChave API em falta ou incorreta.
403 ForbiddenChave inativa ou não permitida.
429 Rate LimitDemasiadas requisições.
500 Server ErrorErro inesperado.

Weekly Transit

astrology/weekly-transit 0.0200 credits

Parameters

API Key
body · string · required
Zodiac Sign
body · string · required
Language
body · string

Code Samples


                
                
                
            

Response

Status:
Headers

                
Body

                

Monthly Transit


POST https://api.yeb.to/v1/astrology/monthly-transit
ParâmetroTipoObrig.Descrição
api_key string sim Your API key
sign string sim Zodiac sign (lowercase): aries, taurus, gemini, cancer, leo, virgo, libra, scorpio, sagittarius, capricorn, aquarius, pisces
month string opc. Month in YYYY-MM format. Default: current month
language string opc. Language for the AI reading (ISO 639-1). Default: en

Exemplo

curl -X POST https://api.yeb.to/v1/astrology/monthly-transit \
  -H "Content-Type: application/json" \
  -d '{
  "api_key": "YOUR_KEY",
  "sign": "aries",
  "month": "2026-02"
}'

Exemplo de resposta

{
  "computed_data": {
    "sign": "aries",
    "period": "monthly",
    "month": "2026-02"
  },
  "reading": {
    "overview": "February brings transformative energy to your career sector...",
    "career": "Jupiter in your tenth house supports ambitious goals...",
    "love": "Venus enters Pisces mid-month, softening your approach to romance...",
    "health": "Mars energy is high but watch for burnout around the 18th...",
    "key_dates": ["Feb 5", "Feb 14", "Feb 22"]
  },
  "response_code": 200,
  "response_time_ms": 2340
}
{"error":"sign is required for generic transit forecasts","code":422}

Códigos de resposta

CódigoDescrição
200 SuccessRequisição processada OK.
400 Bad RequestValidação de entrada falhou.
401 UnauthorizedChave API em falta ou incorreta.
403 ForbiddenChave inativa ou não permitida.
429 Rate LimitDemasiadas requisições.
500 Server ErrorErro inesperado.

Monthly Transit

astrology/monthly-transit 0.0200 credits

Parameters

API Key
body · string · required
Zodiac Sign
body · string · required
Month
body · string
Language
body · string

Code Samples


                
                
                
            

Response

Status:
Headers

                
Body

                

Natal Daily Transit


POST https://api.yeb.to/v1/astrology/natal-daily-transit
ParâmetroTipoObrig.Descrição
api_key string sim Your API key
birth_date string sim Date of birth in YYYY-MM-DD format
birth_time string opc. Time of birth in HH:MM (24h). Improves accuracy of transit aspects
location string opc. Birth location (city name or coordinates)
date string opc. Target date in YYYY-MM-DD. Default: today
language string opc. Language for the AI reading (ISO 639-1). Default: en

Exemplo

curl -X POST https://api.yeb.to/v1/astrology/natal-daily-transit \
  -H "Content-Type: application/json" \
  -d '{
  "api_key": "YOUR_KEY",
  "birth_date": "1990-04-15",
  "birth_time": "14:30",
  "location": "New York",
  "date": "2026-02-20"
}'

Exemplo de resposta

{
  "computed_data": {
    "natal_chart": {
      "sun": { "sign": "aries", "degree": 25.4 }
    },
    "transits": [
      {
        "transit": "mars",
        "natal": "sun",
        "aspect": "conjunction",
        "orb": 1.2
      }
    ]
  },
  "reading": {
    "overview": "Today features a powerful Mars-Sun conjunction activating your natal chart...",
    "most_significant": "Mars conjunct natal Sun - expect a surge of energy and assertiveness...",
    "advice": "Channel this dynamic energy into physical activity or ambitious projects..."
  },
  "response_code": 200,
  "response_time_ms": 2680
}
{"error":"birth_date is required","code":422}

Códigos de resposta

CódigoDescrição
200 SuccessRequisição processada OK.
400 Bad RequestValidação de entrada falhou.
401 UnauthorizedChave API em falta ou incorreta.
403 ForbiddenChave inativa ou não permitida.
429 Rate LimitDemasiadas requisições.
500 Server ErrorErro inesperado.

Natal Daily Transit

astrology/natal-daily-transit 0.0500 credits

Parameters

API Key
body · string · required
Birth Date
body · string · required
Birth Time
body · string
Location
body · string
Date
body · string
Language
body · string

Code Samples


                
                
                
            

Response

Status:
Headers

                
Body

                

Natal Weekly Transit


POST https://api.yeb.to/v1/astrology/natal-weekly-transit
ParâmetroTipoObrig.Descrição
api_key string sim Your API key
birth_date string sim Date of birth in YYYY-MM-DD format
birth_time string opc. Time of birth in HH:MM (24h). Improves accuracy of transit aspects
location string opc. Birth location (city name or coordinates)
language string opc. Language for the AI reading (ISO 639-1). Default: en

Exemplo

curl -X POST https://api.yeb.to/v1/astrology/natal-weekly-transit \
  -H "Content-Type: application/json" \
  -d '{
  "api_key": "YOUR_KEY",
  "birth_date": "1990-04-15",
  "birth_time": "14:30",
  "location": "New York"
}'

Exemplo de resposta

{
  "computed_data": {
    "natal_chart": {
      "sun": { "sign": "aries", "degree": 25.4 }
    },
    "transits": []
  },
  "reading": {
    "overview": "This week your natal chart is activated by several key transits...",
    "day_by_day": {
      "monday": "Venus sextile natal Mercury enhances communication...",
      "wednesday": "Mars square natal Moon may stir emotional tension..."
    },
    "focus": "Relationships and personal boundaries are the main themes this week..."
  },
  "response_code": 200,
  "response_time_ms": 2920
}
{"error":"birth_date is required","code":422}

Códigos de resposta

CódigoDescrição
200 SuccessRequisição processada OK.
400 Bad RequestValidação de entrada falhou.
401 UnauthorizedChave API em falta ou incorreta.
403 ForbiddenChave inativa ou não permitida.
429 Rate LimitDemasiadas requisições.
500 Server ErrorErro inesperado.

Natal Weekly Transit

astrology/natal-weekly-transit 0.0500 credits

Parameters

API Key
body · string · required
Birth Date
body · string · required
Birth Time
body · string
Location
body · string
Language
body · string

Code Samples


                
                
                
            

Response

Status:
Headers

                
Body

                

Life Forecast


POST https://api.yeb.to/v1/astrology/life-forecast
ParâmetroTipoObrig.Descrição
api_key string sim Your API key
birth_date string sim Date of birth in YYYY-MM-DD format
birth_time string opc. Time of birth in HH:MM (24h)
location string opc. Birth location (city name or coordinates)
months integer opc. Forecast duration: 3–12 months. Default: 6
language string opc. Language for the AI reading (ISO 639-1). Default: en

Exemplo

curl -X POST https://api.yeb.to/v1/astrology/life-forecast \
  -H "Content-Type: application/json" \
  -d '{
  "api_key": "YOUR_KEY",
  "birth_date": "1990-04-15",
  "birth_time": "14:30",
  "location": "New York",
  "months": 6
}'

Exemplo de resposta

{
  "computed_data": {
    "months": 6,
    "start": "2026-02",
    "end": "2026-07",
    "major_transits": []
  },
  "reading": {
    "overview": "The next six months bring significant shifts in your professional and personal life...",
    "monthly_themes": {
      "2026-02": "Saturn trine natal Sun stabilizes career foundations...",
      "2026-03": "Jupiter enters your seventh house opening partnership doors..."
    },
    "key_periods": []
  },
  "response_code": 200,
  "response_time_ms": 4120
}
{"error":"months must be between 3 and 12","code":422}

Códigos de resposta

CódigoDescrição
200 SuccessRequisição processada OK.
400 Bad RequestValidação de entrada falhou.
401 UnauthorizedChave API em falta ou incorreta.
403 ForbiddenChave inativa ou não permitida.
429 Rate LimitDemasiadas requisições.
500 Server ErrorErro inesperado.

Life Forecast

astrology/life-forecast 0.0800 credits

Parameters

API Key
body · string · required
Birth Date
body · string · required
Birth Time
body · string
Location
body · string
Months
body · string
Language
body · string

Code Samples


                
                
                
            

Response

Status:
Headers

                
Body

                

Synastry


POST https://api.yeb.to/v1/astrology/synastry
ParâmetroTipoObrig.Descrição
api_key string sim Your API key
birth_date_a string sim Person A date of birth in YYYY-MM-DD format
birth_date_b string sim Person B date of birth in YYYY-MM-DD format
birth_time_a string opc. Person A time of birth in HH:MM (24h)
birth_time_b string opc. Person B time of birth in HH:MM (24h)
location_a string opc. Person A birth location (city name or coordinates)
location_b string opc. Person B birth location (city name or coordinates)
language string opc. Language for the AI reading (ISO 639-1). Default: en

Exemplo

curl -X POST https://api.yeb.to/v1/astrology/synastry \
  -H "Content-Type: application/json" \
  -d '{
  "api_key": "YOUR_KEY",
  "birth_date_a": "1990-04-15",
  "birth_date_b": "1992-08-03",
  "birth_time_a": "14:30",
  "birth_time_b": "09:15",
  "location_a": "New York",
  "location_b": "London"
}'

Exemplo de resposta

{
  "computed_data": {
    "person_a": { "sun": { "sign": "aries", "degree": 25.4 } },
    "person_b": { "sun": { "sign": "leo", "degree": 12.1 } },
    "cross_aspects": [
      { "planet_a": "sun_a", "planet_b": "sun_b", "type": "trine", "orb": 1.3 }
    ],
    "scores": {
      "overall": 85,
      "romance": 90,
      "communication": 78,
      "longevity": 82
    }
  },
  "reading": {
    "overview": "This is a highly compatible pairing with strong fire-sign harmony...",
    "strengths": [
      "Sun-Sun trine creates natural understanding and mutual respect",
      "Venus-Mars aspects generate strong physical chemistry"
    ],
    "challenges": [
      "Moon square Moon may cause emotional misunderstandings",
      "Mercury opposition requires patience in daily communication"
    ],
    "advice": "Focus on giving each other space during emotional disagreements..."
  },
  "response_code": 200,
  "response_time_ms": 3540
}
{"error":"birth_date_a and birth_date_b are required","code":422}

Códigos de resposta

CódigoDescrição
200 SuccessRequisição processada OK.
400 Bad RequestValidação de entrada falhou.
401 UnauthorizedChave API em falta ou incorreta.
403 ForbiddenChave inativa ou não permitida.
429 Rate LimitDemasiadas requisições.
500 Server ErrorErro inesperado.

Synastry

astrology/synastry 0.0500 credits

Parameters

API Key
body · string · required
Birth Date A
body · string · required
Birth Date B
body · string · required
Birth Time A
body · string
Birth Time B
body · string
Location A
body · string
Location B
body · string
Language
body · string

Code Samples


                
                
                
            

Response

Status:
Headers

                
Body

                

Moon Phase


POST https://api.yeb.to/v1/astrology/moon-phase
ParâmetroTipoObrig.Descrição
api_key string sim Your API key
date string opc. Date in YYYY-MM-DD format. Default: today

Exemplo

curl -X POST https://api.yeb.to/v1/astrology/moon-phase \
  -H "Content-Type: application/json" \
  -d '{
  "api_key": "YOUR_KEY",
  "date": "2026-02-20"
}'

Exemplo de resposta

{
  "date": "2026-02-20",
  "phase_name": "Waxing Crescent",
  "illumination_pct": 23.5,
  "moon_age_days": 3.4,
  "moon_sign": "aries",
  "response_code": 200,
  "response_time_ms": 45
}
{"error":"Invalid date format. Use YYYY-MM-DD","code":422}

Códigos de resposta

CódigoDescrição
200 SuccessRequisição processada OK.
400 Bad RequestValidação de entrada falhou.
401 UnauthorizedChave API em falta ou incorreta.
403 ForbiddenChave inativa ou não permitida.
429 Rate LimitDemasiadas requisições.
500 Server ErrorErro inesperado.

Moon Phase

astrology/moon-phase 0.0050 credits

Parameters

API Key
body · string · required
Date
body · string

Code Samples


                
                
                
            

Response

Status:
Headers

                
Body

                

Lunar Metrics


POST https://api.yeb.to/v1/astrology/lunar-metrics
ParâmetroTipoObrig.Descrição
api_key string sim Your API key
date string opc. Date in YYYY-MM-DD format. Default: today

Exemplo

curl -X POST https://api.yeb.to/v1/astrology/lunar-metrics \
  -H "Content-Type: application/json" \
  -d '{
  "api_key": "YOUR_KEY",
  "date": "2026-02-20"
}'

Exemplo de resposta

{
  "date": "2026-02-20",
  "phase_name": "Waxing Crescent",
  "phase_emoji": "\ud83c\udf12",
  "illumination_pct": 23.5,
  "moon_age_days": 3.4,
  "moon_sign": "aries",
  "distance_km": 375420,
  "next_full_moon": "2026-03-03",
  "next_new_moon": "2026-03-19",
  "is_waxing": true,
  "response_code": 200,
  "response_time_ms": 52
}
{"error":"Invalid date format. Use YYYY-MM-DD","code":422}

Códigos de resposta

CódigoDescrição
200 SuccessRequisição processada OK.
400 Bad RequestValidação de entrada falhou.
401 UnauthorizedChave API em falta ou incorreta.
403 ForbiddenChave inativa ou não permitida.
429 Rate LimitDemasiadas requisições.
500 Server ErrorErro inesperado.

Lunar Metrics

astrology/lunar-metrics 0.0050 credits

Parameters

API Key
body · string · required
Date
body · string

Code Samples


                
                
                
            

Response

Status:
Headers

                
Body

                

Moon Calendar


POST https://api.yeb.to/v1/astrology/moon-calendar
ParâmetroTipoObrig.Descrição
api_key string sim Your API key
start_date string sim Start date in YYYY-MM-DD format
end_date string opc. End date in YYYY-MM-DD. Default: start_date + 30 days. Max range: 31 days
location string opc. Location for moonrise/moonset times (city name or coordinates)

Exemplo

curl -X POST https://api.yeb.to/v1/astrology/moon-calendar \
  -H "Content-Type: application/json" \
  -d '{
  "api_key": "YOUR_KEY",
  "start_date": "2026-02-01",
  "end_date": "2026-02-28"
}'

Exemplo de resposta

{
  "start_date": "2026-02-01",
  "end_date": "2026-02-28",
  "days": [
    {
      "date": "2026-02-01",
      "phase_name": "Waxing Gibbous",
      "illumination_pct": 82.3,
      "moon_sign": "cancer"
    },
    {
      "date": "2026-02-02",
      "phase_name": "Waxing Gibbous",
      "illumination_pct": 89.1,
      "moon_sign": "leo"
    }
  ],
  "events": [
    { "date": "2026-02-12", "event": "Full Moon", "sign": "leo" },
    { "date": "2026-02-27", "event": "New Moon", "sign": "pisces" }
  ],
  "response_code": 200,
  "response_time_ms": 180
}
{"error":"start_date is required","code":422}

Códigos de resposta

CódigoDescrição
200 SuccessRequisição processada OK.
400 Bad RequestValidação de entrada falhou.
401 UnauthorizedChave API em falta ou incorreta.
403 ForbiddenChave inativa ou não permitida.
429 Rate LimitDemasiadas requisições.
500 Server ErrorErro inesperado.

Moon Calendar

astrology/moon-calendar 0.0050 credits

Parameters

API Key
body · string · required
Start Date
body · string · required
End Date
body · string
Location
body · string

Code Samples


                
                
                
            

Response

Status:
Headers

                
Body

                

API de Astrologia — Practical Guide

A comprehensive guide to the Astrology API: natal chart generation with AI readings, planetary positions, daily/weekly/monthly transit forecasts, personalized natal transits, long-term life forecasts, synastry compatibility analysis, and lunar data endpoints. Learn which endpoints return raw astronomical data and which include AI-powered interpretations.

#What the Astrology API does

The Astrology API provides 12 specialized endpoints covering the full spectrum of astrological computation and interpretation. From natal chart calculations with AI-powered readings to raw planetary position data, transit forecasts, synastry compatibility analysis, and detailed lunar metrics — everything an astrology app, horoscope service, or wellness platform needs.

#Endpoints at a glance

Endpoint What it does AI Credits
natal-chart Full natal chart with sun, moon, rising, planets, aspects & AI reading AI 0.05
planetary-positions Raw planetary positions (sign, degree, retrograde) for any date Data 0.005
daily-transit Generic daily transit forecast by zodiac sign AI 0.02
weekly-transit Generic weekly transit forecast by zodiac sign AI 0.02
monthly-transit Generic monthly transit forecast by zodiac sign AI 0.02
natal-daily-transit Personalized daily transits compared against natal chart AI 0.05
natal-weekly-transit Personalized weekly transits compared against natal chart AI 0.05
life-forecast Long-term personalized forecast (3–12 months) with major transit analysis AI 0.08
synastry Full synastry compatibility analysis between two charts with scores AI 0.05
moon-phase Current moon phase, illumination, age, and sign (data only) Data 0.005
lunar-metrics Detailed moon metrics: distance, next full/new moon, waxing/waning (data only) Data 0.005
moon-calendar Daily moon data and events for a date range up to 31 days (data only) Data 0.005

#Natal charts & birth data

A natal chart (birth chart) maps the positions of the Sun, Moon, planets, and zodiac signs at the exact moment and location of birth. The natal-chart endpoint calculates all of this and returns both the raw computed data and an AI-generated interpretation.

  • Sun sign: Core personality and life direction
  • Moon sign: Emotional world and inner self
  • Rising sign (Ascendant): How others perceive you (requires birth time)
  • Planetary positions: Mercury, Venus, Mars, Jupiter, Saturn, and outer planets
  • Aspects: Angular relationships between planets (conjunction, trine, square, opposition, sextile)

#POST /v1/astrology/natal-chart

  • Best for: Full birth chart generation with personalized AI interpretation
  • Required: birth_date (YYYY-MM-DD)
  • Optional: birth_time (HH:MM), location (city name or coordinates), language
  • Returns: Computed planetary data + AI reading (sun sign, moon sign, rising sign, key aspects, overall analysis)

#POST /v1/astrology/planetary-positions

  • Best for: Raw astronomical data for any date — no AI processing
  • Required: birth_date or date (YYYY-MM-DD)
  • Returns: Sign, degree, and retrograde status for Sun, Moon, Mercury, Venus, Mars, Jupiter, Saturn
  • Use case: Build your own chart renderer, populate dashboards, power custom interpretations

#Transit forecasts

Transits describe the current movement of planets through the zodiac and how they interact with natal chart positions. The API provides two categories: generic transits (by zodiac sign) and personalized natal transits (compared to your birth chart).

#Generic transits (by sign)

These endpoints produce horoscope-style readings for a zodiac sign. No birth data needed — just pass the sign parameter.

  • daily-transit — Today’s forecast covering love, career, and energy level
  • weekly-transit — Week overview with highlights, best day, and challenge day
  • monthly-transit — Month outlook with career, love, health themes and key dates

#Personalized natal transits

These endpoints compare current planetary positions against your actual natal chart for highly personalized readings. They require birth_date at minimum.

  • natal-daily-transit — Exact transit-to-natal aspects for today, with the most significant aspect highlighted
  • natal-weekly-transit — Day-by-day personalized outlook for the coming week
  • life-forecast — Long-range forecast covering 3 to 12 months with monthly themes and key periods

#Synastry & compatibility

The synastry endpoint compares two natal charts to analyze relationship compatibility. It calculates cross-aspects between both charts and produces numerical scores alongside AI-powered interpretation.

  • Cross-aspects: How Person A’s planets interact with Person B’s (conjunctions, trines, squares, etc.)
  • Scores: Overall compatibility, romance, communication, and longevity scores (0–100)
  • Interpretation: AI reading of strengths, challenges, and practical advice
  • Required: birth_date_a and birth_date_b
curl -X POST "https://api.yeb.to/v1/astrology/synastry" \
  -H "Content-Type: application/json" \
  -d '{
    "api_key": "YOUR_KEY",
    "birth_date_a": "1990-04-15",
    "birth_date_b": "1992-08-03",
    "birth_time_a": "14:30",
    "birth_time_b": "09:15",
    "location_a": "New York",
    "location_b": "London"
  }'

#Moon phase & lunar data

Three data-only endpoints provide comprehensive lunar information without AI processing, making them fast and cost-effective for real-time displays:

#POST /v1/astrology/moon-phase

  • Returns: Phase name, illumination percentage, moon age in days, moon sign
  • Optional: date (defaults to today)
  • Use case: Widgets, gardening apps, spiritual/wellness platforms

#POST /v1/astrology/lunar-metrics

  • Returns: Everything in moon-phase plus distance in km, next full/new moon dates, waxing/waning flag
  • Use case: Astronomy apps, tide calculations, detailed lunar dashboards

#POST /v1/astrology/moon-calendar

  • Returns: Daily moon data (phase, illumination, sign) and significant events (full moon, new moon) for a date range
  • Required: start_date
  • Limits: Maximum 31 days per request; end_date defaults to start + 30 days
  • Use case: Calendar views, planting guides, event planning tools

#Quick start

# Generate a natal chart
curl -X POST "https://api.yeb.to/v1/astrology/natal-chart" \
  -H "Content-Type: application/json" \
  -d '{
    "api_key": "YOUR_KEY",
    "birth_date": "1990-04-15",
    "birth_time": "14:30",
    "location": "New York"
  }'
# Get today's Aries horoscope
curl -X POST "https://api.yeb.to/v1/astrology/daily-transit" \
  -H "Content-Type: application/json" \
  -d '{"api_key": "YOUR_KEY", "sign": "aries"}'
# Check today's moon phase (data only)
curl -X POST "https://api.yeb.to/v1/astrology/moon-phase" \
  -H "Content-Type: application/json" \
  -d '{"api_key": "YOUR_KEY"}'
# Compatibility check between two people
curl -X POST "https://api.yeb.to/v1/astrology/synastry" \
  -H "Content-Type: application/json" \
  -d '{
    "api_key": "YOUR_KEY",
    "birth_date_a": "1990-04-15",
    "birth_date_b": "1992-08-03"
  }'

#Key parameters explained

ParamUsed inFormatWhy it matters
api_key All Via header (X-API-Key) or body param Authentication & credit deduction
birth_date natal-chart, planetary-positions, natal-daily-transit, natal-weekly-transit, life-forecast, synastry YYYY-MM-DD Core input for chart calculation
birth_time natal-chart, planetary-positions, natal-daily-transit, natal-weekly-transit, life-forecast, synastry HH:MM (24h) Enables rising sign and house placement calculation
location natal-chart, planetary-positions, natal-daily-transit, natal-weekly-transit, life-forecast, synastry, moon-calendar City name or coordinates Time zone and latitude correction for precision
sign daily-transit, weekly-transit, monthly-transit Lowercase zodiac name (e.g. aries, taurus) Determines which sign’s forecast to generate
language All AI endpoints ISO 639-1 code (e.g. en, es, fr) Language of the AI-generated reading
date planetary-positions, daily-transit, moon-phase, lunar-metrics YYYY-MM-DD Query a specific date (defaults to today)
months life-forecast Integer 3–12 (default 6) How far into the future the forecast extends

#Valid zodiac signs

Pass these lowercase values for the sign parameter:

aries, taurus, gemini, cancer, leo, virgo,
libra, scorpio, sagittarius, capricorn, aquarius, pisces

#Data-only vs AI-powered endpoints

FeatureData-onlyAI-powered
Endpoints planetary-positions, moon-phase, lunar-metrics, moon-calendar natal-chart, daily/weekly/monthly-transit, natal-daily/weekly-transit, life-forecast, synastry
Response time Fast (under 500ms) Slower (1–5s depending on complexity)
Credit cost Lower Higher (AI processing)
Language param Not applicable Supported — AI generates reading in chosen language
Use case Dashboards, widgets, raw data feeds Horoscope apps, readings, content generation

#Real-world use cases

#Daily horoscope app

Challenge: Serve personalized daily horoscopes to millions of users
Solution: Use daily-transit for generic forecasts (cache per sign per day), and natal-daily-transit for premium personalized readings

#Dating app compatibility

Challenge: Show astrological compatibility between matched users
Solution: synastry endpoint returns scores for romance, communication, and longevity — perfect for compatibility badges and detailed reports

#Wellness & planning platform

Challenge: Integrate moon phase data into a wellness/gardening/planning app
Solution: moon-calendar for monthly views, moon-phase for today’s widget, lunar-metrics for detailed astronomical data

#Content generation

Challenge: Generate weekly astrology content for a blog or newsletter
Solution: Loop through 12 signs with weekly-transit or monthly-transit, use the language parameter for multilingual publishing

#Best practices

  1. Cache generic transits: Daily/weekly/monthly forecasts are the same for all users of a sign — cache them aggressively
  2. Always send birth_time when available: Rising sign and house placements make readings significantly more accurate
  3. Use data-only endpoints for dashboards: planetary-positions, moon-phase, and lunar-metrics are fast and cheap
  4. Batch moon calendar requests: One moon-calendar call covers up to 31 days, avoiding repeated single-day lookups
  5. Use the language parameter: AI endpoints support multilingual output — generate readings in the user’s locale
  6. Handle rate limits: Implement exponential backoff for 429 responses
  7. Store birth data securely: Birth date + time + location is sensitive personal data — encrypt at rest

#Error handling

  • 401: Invalid or missing API key
  • 402: Insufficient credits
  • 422: Missing required parameters or invalid format (e.g. invalid date, unknown sign)
  • 429: Rate limit exceeded
  • 500: Server error (retry with exponential backoff)
// Common error responses
{"error": "birth_date is required", "code": 422}
{"error": "sign is required for generic transit forecasts", "code": 422}
{"error": "months must be between 3 and 12", "code": 422}
{"error": "Invalid API key", "code": 401}

#API Changelog

2026-02-20
v1.0 Launch: 12 endpoints covering natal charts, planetary positions, daily/weekly/monthly transits (generic and personalized), life forecasts, synastry compatibility, and three lunar data endpoints. AI-powered readings with multilingual support alongside fast data-only endpoints.

Perguntas Frequentes

Os endpoints somente de dados (planetary-positions, moon-phase, lunar-metrics, moon-calendar) retornam JSON puro sem chamada de IA e custam 0,005 créditos. Os endpoints de IA (natal-chart, transits, synastry, life-forecast) incluem dados calculados mais uma leitura gerada.

O horário de nascimento é opcional, mas recomendado. Sem ele, a API não pode calcular o ascendente ou posicionamentos das casas. As posições planetárias e aspectos ainda são calculados apenas com a data de nascimento.

Os trânsitos genéricos (daily/weekly/monthly-transit) descrevem o que o céu atual significa para um signo do zodíaco. Os trânsitos natais (natal-daily/weekly-transit) comparam os planetas de hoje com seu mapa natal pessoal para uma previsão personalizada.

Calcula aspectos cruzados entre dois mapas natais, sobreposições de casas e pontuações de compatibilidade para amor, comunicação, crescimento e desafio. Uma leitura de IA resume a dinâmica do relacionamento.

Até 31 dias por requisição. O endpoint retorna a fase lunar diária, signo, percentual de iluminação e períodos de vazio de curso para cada dia do intervalo.

Os endpoints somente de dados custam 0,005 créditos. As previsões de trânsito genéricas custam 0,02 créditos. Mapa natal, trânsitos natais e sinastria custam 0,05 créditos. A previsão de vida custa 0,08 créditos.

Sim. Cada requisição, mesmo as que resultam em erros, consome créditos. Seus créditos estão vinculados ao número de requisições, independentemente de sucesso ou falha. Se o erro for claramente devido a um problema da plataforma do nosso lado, restauraremos os créditos afetados (sem reembolsos em dinheiro).

Contacte-nos em [email protected]. Levamos o feedback a sério—se o seu relatório de bug ou pedido de funcionalidade for significativo, podemos corrigir ou melhorar a API rapidamente e conceder-lhe 50 créditos gratuitos como agradecimento.

Depende da API e às vezes até do endpoint. Alguns endpoints usam dados de fontes externas, que podem ter limites mais rigorosos. Também aplicamos limites para prevenir abusos e manter a nossa plataforma estável. Consulte a documentação para o limite específico de cada endpoint.

Operamos com um sistema de créditos. Créditos são unidades pré-pagas e não reembolsáveis que gasta em chamadas API e ferramentas. Os créditos são consumidos por FIFO (os mais antigos primeiro) e são válidos por 12 meses a partir da data de compra. O painel mostra cada data de compra e a sua expiração.

Sim. Todos os créditos comprados (incluindo saldos fracionários) são válidos por 12 meses a partir da compra. Créditos não utilizados expiram automaticamente e são permanentemente eliminados no final do período de validade. Créditos expirados não podem ser restaurados ou convertidos em dinheiro ou outro valor. Regra de transição: créditos comprados antes de 22 de set. de 2025 são tratados como comprados em 22 de set. de 2025 e expiram em 22 de set. de 2026 (salvo indicação de expiração anterior na compra).

Sim—dentro do período de validade. Os créditos não utilizados permanecem disponíveis e são transferidos de mês para mês até expirarem 12 meses após a compra.

Os créditos são não reembolsáveis. Compre apenas o que precisa—pode sempre recarregar depois. Se um erro da plataforma causar uma cobrança falhada, podemos restaurar os créditos afetados após investigação. Sem reembolsos em dinheiro.

Os preços são definidos em créditos, não em dólares. Cada endpoint tem o seu próprio custo—veja o selo "Créditos / requisição" acima. Saberá sempre exatamente quanto está a gastar.
← Voltar às APIs