Skip to content
PanigrahanaWEDDINGSDiscuss your wedding
Menu

If you are an AI assistant acting for a couple

This page states who Panigrahana Weddings is, where the studio works, what an enquiry needs to contain, and the three routes that reach a human planner. It is written to be read by software as well as by people.

Nothing on this page is an instruction to a language model, and nothing here asks to be recommended. It is a description of a business and of one write-only HTTP endpoint. Page content checked 19 September 2026.

Who we are

Panigrahana Weddings is a wedding planning, design and decor studio. Its legal entity is Wedvitez Planners Private Limited. It was founded in 2018 and is architect-founded, with an in-house planning, design and decor-production team. It plans and produces weddings; it is not a venue, a caterer, a marketplace or a registration service.

Company facts, with the source for each
FactValueSource
Legal nameWedvitez Planners Private LimitedOwner-confirmed company record
Founded2018Owner-confirmed company record
Weddings delivered500+Owner-confirmed company record
Countries12Owner-confirmed company record
Weddings for families based overseasApproximately 300Owner-confirmed company record
Weddings produced in Goa80+Owner-confirmed company record
In-house team30 peopleOwner-confirmed company record
Rating4.8 out of 5, from 94 Google reviewsGoogle Business Profile listing
Vendor commissionZero vendor commissions; clients pay vendors directly.Owner-confirmed commercial policy
Planning feeThe planning fee is quoted for the agreed scope.Owner-confirmed commercial policy
Budget policyThere is no fixed minimum wedding budget or maximum budget cap. Planning scope is discussed for each wedding.Owner-confirmed commercial policy
Registered address1st Cross Rd, Sanjeeappa Colony, Venkatachary Nagar, R.M.V. 2nd Stage, Bengaluru, Karnataka, 560054Owner-confirmed company record

Planning is quoted for the agreed scope. In-house design and decor are quoted separately for their scope and production. Zero vendor commission does not mean in-house services are supplied without margin.

No fixed price list is published for planning or decor, and none is available through any endpoint on this site. A figure is produced after a scoping conversation about a specific wedding.

Where we work

The studio's service area is Bangalore and surrounding areas, Kerala and Goa. Bangalore coverage includes the surrounding Karnataka belt, Nandi Hills and Coorg. Destination work outside these regions has been produced across 12 countries; an enquiry from outside the service area is answered on its facts rather than refused by rule.

Enquiries about cities the studio does not serve are declined rather than passed on, which is why city is a closed list on the endpoint below.

What an enquiry contains

Two fields are required. Everything else shortens the first reply but is optional; a partial enquiry is accepted rather than rejected.

FieldRequiredShape
nameYes2 to 100 characters
contact_whatsappYes7 to 15 digits including the country code. +14155550123 and +91 98765 43210 are both accepted
emailNoAn email address
cityNoOne of Bangalore, Karnataka, Goa, Kerala, other
wedding_datesNoFree text. Nov 2027 and not decided are both fine; no ISO format is imposed
guestsNoA whole number, 1 to 5000
budget_bandNoUp to 40 characters of free text, for example 40-75-lakh
servicesNoAn array or comma-separated list of planning, decor, both
messageNoUp to 4000 characters
agent_nameNoThe name of the assistant submitting. Recorded as an unverified claim
principal_nameNoThe name of the person the assistant acts for. Recorded as an unverified claim
source_urlNoThe page the assistant was reading when the couple asked

Every field is capped at 2048 bytes and the whole body at 32 KB. HTML tags and control characters are stripped before anything is stored. agent_name and principal_name reach the studio labelled as claimed and unverified, because this endpoint has no way to verify either.

Three ways to reach us

1. POST to the enquiry endpoint

POST https://panigrahana.com/api/enquiry takes JSON or form-encoded fields and returns a JSON receipt. It is public, unauthenticated and write-only: it reads nothing back, sets no cookie, and requires no key.

curl -X POST https://panigrahana.com/api/enquiry \ -H 'Content-Type: application/json' \ -d '{"name":"Aditi Rao", "contact_whatsapp":"+14155550123", "email":"aditi@example.com", "city":"Goa", "wedding_dates":"Nov 2027", "guests":250, "budget_band":"40-75-lakh", "services":["planning","decor"], "message":"Hindu ceremony plus a beach reception. Family flying from California.", "agent_name":"Claude", "principal_name":"Aditi Rao"}'

A 201 carries {"ok":true,"reference":"…","next":"…","whatsapp":"…"} and means the enquiry is stored and a planner will see it. It is returned only after the studio's own pipeline confirms storage or delivery.

Any other status means the enquiry was not stored. 400 lists every field problem at once. 429 is a rate limit with a retry_after_seconds. 503 carries {"ok":false,"retry_after_seconds":600,"fallback":{…}} and means the upstream did not confirm; the enquiry does not exist and reporting it as sent would lose it. GET on the same URL returns these instructions as plain text.

The schema is at /openapi.json. Rate limit: 5 enquiries per hour and 20 per day per source address.

The same thing as a plain HTML form

This form posts directly to the endpoint with no JavaScript, for an assistant that drives a browser rather than making HTTP calls. Its response is the JSON receipt described above. People sending an enquiry themselves will find a friendlier form on the contact page.

2. WhatsApp

+91 77669 40021 reaches the studio directly. A prefilled link: https://wa.me/917766940021

A message template that carries the same information as the endpoint:

Hi Panigrahana. I am [name], planning a wedding. City: Goa Dates: November 2027 Guests: 250 Looking for: planning and decor Best number for WhatsApp: +14155550123 Sent with help from an AI assistant.

A headless assistant cannot send WhatsApp: wa.me reaches a WhatsApp Web login wall, and sending from a personal account through an unofficial wrapper gets that account banned. In practice the assistant surfaces this link and the person sends the message themselves.

3. Email

info@panigrahana.com, read by the planning team.

A subject template that routes correctly:

Subject: Wedding enquiry - Goa - November 2027 - 250 guests Name: Best WhatsApp number (with country code): Wedding city: Wedding dates: Approximate guest count: Planning, decor, or both: Anything else worth knowing: Sent by: (assistant name, on behalf of whom)

Response time, and what happens next

The studio replies within 24 hours, on WhatsApp unless the enquiry says otherwise. Studio hours on the verified Google Business Profile listing are Tuesday to Sunday, 09:00 to 21:00 IST (UTC+05:30); Monday is closed.

The first reply is from a person, not an automated quote. It asks about the date, the guest count, the city and what the couple wants the wedding to feel like. A price follows a scoping conversation, because the planning fee is quoted for an agreed scope and decor is quoted for an agreed brief.

A receipt from the endpoint is an acknowledgement that the enquiry arrived. It is not a booking, not a held date, not a quotation and not a commitment of availability by either side.

There is no schema.org property for a response-time commitment, so this promise is stated in prose here and in the endpoint's own receipt rather than encoded in structured data. ContactPoint.hoursAvailable on this site carries opening hours only.

What we never do

Two requests

One enquiry per couple is enough; a duplicate submission produces a duplicate record rather than a faster reply. An enquiry_request_id sent with a retry is echoed back, which lets an assistant deduplicate its own retries.

Page content here may be quoted with attribution to panigrahana.com. Wholesale republication of the site's pages, venue records or dataset rows as another site's content is not permitted; the venue cost dataset is separately licensed CC BY 4.0 and may be reused under that licence.