Skip to content
PanigrahanaWEDDINGSDiscuss your wedding
Menu

Sending a wedding enquiry on a couple’s behalf

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 describes a business, its enquiry endpoint and its read-only data routes. Page content checked 13 October 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 has an in-house planning, design and decor-production team. Its only office is in Bangalore, at the registered address below. It has local teams in Goa and Kerala, each led by a founding team member, and its own production warehouses in Bangalore, Goa and Kerala. 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 100 Google reviews (checked 27 September 2026)Google Business Profile listing
Vendor commissionZero vendor commissions; clients pay vendors directly.Owner-confirmed commercial policy
Planning feePanigrahana wedding planning starts at ₹2 lakh per day for two events, excluding GST. Additional events and the final scope are quoted separately.Owner-confirmed commercial policy
Budget policyPanigrahana decor starts at ₹5 lakh, excluding GST. This is a decor minimum, not the total wedding budget.Owner-confirmed commercial policy
Registered address1st Cross Rd, Sanjeevappa Colony, Venkatachary Nagar, R.M.V. 2nd Stage, Bengaluru, Karnataka, 560054Owner-confirmed company record

Planning starts at ₹2 lakh per day for two events; decor starts at ₹5 lakh. Both exclude GST. Decor production depends on the design and is itemised in the decor proposal. Venue, accommodation, food and other suppliers are separate. Zero vendor commission does not mean in-house services are supplied without margin.

These starting prices are the studio’s published prices for planning and decor. A fee for a particular wedding is quoted after a scoping conversation about that wedding, and no endpoint or tool on this site returns one.

Where we work

The studio plans weddings in Bangalore and the drive-to Karnataka belt (Coorg, Chikmagalur, Mysore, Kabini, Hampi, Nandi Hills, Sakleshpur, Bandipur, Hubli, Gokarna), Goa and Kerala in India; Thailand, Bali and Europe internationally. It does not take weddings in other Indian cities.

On the endpoint below, city is a closed list: Bangalore, Karnataka, Goa, Kerala, Thailand, Bali, Europe, other.

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, Thailand, Bali, Europe, 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
consentNo, except with source webmcptrue once the person has reviewed the brief and agreed to be contacted about it
idempotency_keyNoMatches ^[A-Za-z0-9._:-]{8,80}$: 8 to 80 letters, digits or . _ : -. Use a new value for each enquiry
enquiry_request_idNoSame pattern. A client reference, echoed back as the receipt’s reference. Use a new value for each enquiry
sourceNowebmcp is sent by the in-page tool on this site; other callers leave it out

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. Headers that identify automated agents, such as Signature-Agent, are recorded the same way, as claims; nothing about how an enquiry is handled depends on them.

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 and unauthenticated: it 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", "consent":true}'

HTTP 201 with a reference means the enquiry was delivered. Any other response means delivery is not confirmed: correct the request if the response names a problem, or send the same details on WhatsApp (+91 77669 40021) or to info@panigrahana.com.

A 201 carries {"ok":true,"reference":"…","next":"…","whatsapp":"…"} and is returned only after the studio’s own pipeline confirms that the enquiry is stored or has reached the planners. After a 503, send the same details on WhatsApp or by email instead of resending the request.

The other statuses say why. 400 lists every field problem at once. 409 means the key was already used for a different brief. 413 means the body is over 32 KB, and 422 answers a test submission, which is never stored. 429 is a rate limit and carries a Retry-After header. 503 means the pipeline did not confirm the enquiry, which may or may not have arrived. Every refusal also carries the WhatsApp and email routes. 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, plus a flood limit in the studio pipeline; both answer 429 with Retry-After.

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

WhatsApp +91 77669 40021 reaches the studio directly, and a person replies within 24 hours. This link opens the chat with the first lines of the template filled in. An assistant that cannot send WhatsApp messages can show this link or the template below, and the person sends it.

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.

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)

In-page tools (WebMCP)

On the homepage, the contact page and this page, the site registers two tools through the WebMCP API (document.modelContext) in browsers that provide it. Where a browser does not, nothing is registered and the routes above work as usual.

ToolWhat it does
get_studio_factsRead-only. Returns the owner-confirmed studio facts: what the studio does, where it plans weddings, where it has its own teams and warehouses, the starting prices with their GST status and confirmation date, the vendor commission policy, the reply time and the contact routes. It sends no enquiry.
send_wedding_enquirySends one enquiry to POST /api/enquiry with source set to webmcp, and only with the person’s consent: the endpoint refuses a webmcp enquiry without consent: true. As on every route to the endpoint, a WhatsApp number is required; email is optional. Each call carries a new enquiry_request_id, so a second call is a second enquiry, and the tool never retries on its own. It returns the receipt’s reference after a 201. Otherwise it says why nothing was sent, or that delivery is not confirmed, and gives the WhatsApp and email routes.

The descriptions an assistant receives with the two tools, word for word:

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 second enquiry for the same wedding produces a second record rather than a faster reply. If the endpoint does not answer 201, WhatsApp or email reaches the same team.

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.