---
title: "Matching Gunmilan Report Endpoint"
method: POST
path: "/matching/gunmilan/report"
---

# Matching Gunmilan Report Endpoint

`POST /matching/gunmilan/report`

## Request

- Base URL: `https://jyotish-api.bda.ai` (the document declares no server; this is the origin it was published from)
- URL: `https://jyotish-api.bda.ai/matching/gunmilan/report`
- Auth: none declared

Gun Milan compatibility as a structured, bilingual, source-cited REPORT.

Computes the SAME deterministic Ashtakoota result as the public
`/matching/gunmilan` endpoint (no new entitlement surface — identical data,
already ungated), then renders it as a multi-channel report asset (§7): band
interpretation, per-koota breakdown, Manglik balance, §12 guidance-not-fatalism
dosha notes (no fabricated scripture), and a self-describing constraints
envelope. The LLM only narrates; this layer is pure templating.

## Request body

- MatchRequest
  - `groom` MatchPerson, required
    - `name` string, nullable
    - `gender` string, nullable
    - `date_of_birth` string, date, required
    - `time_of_birth` string, required: HH:MM:SS in local time
    - `time_accuracy` string
    - `lat` number, required
    - `lng` number, required
    - `tz` string, nullable
  - `bride` MatchPerson, required
    - `name` string, nullable
    - `gender` string, nullable
    - `date_of_birth` string, date, required
    - `time_of_birth` string, required: HH:MM:SS in local time
    - `time_accuracy` string
    - `lat` number, required
    - `lng` number, required
    - `tz` string, nullable

## Response `200`

Successful Response

- unknown

## Other responses

- `422`: Validation Error

---

[API](https://skmtc.dev/bda/apis/bda-jyotish-panchang-service.md) · [All operations](https://skmtc.dev/bda/apis/bda-jyotish-panchang-service/llms.txt) · [OpenAPI document](https://skmtc.dev/bda/apis/bda-jyotish-panchang-service/revisions/90f241bf4009?raw)