Capablity to add dynamic fileds data in on search API

Description

Please see the flow below:

Farmer Selects Advisory Services
Farmer: Advisory Services
Bot:
Great! What would you like to know about your crops?
🦠 Pest and Disease Advisory
🌦️ Weather Advisory
📋 Government Schemes
📝 Other Queries
Farmer: Pest and Disease Advisory
Bot:
Have you already identified the pest or disease affecting your crops?
✅ Yes
❌ No
Farmer: Yes
Bot:
Great! Please enter the name of the crop you're working with. For example, “Grapes” or “Tomatoes.”
(Farmer types: “Grapes”)
Bot:
Thanks! Now, please specify the pest or disease that is affecting your grapes. For example, "Powdery Mildew" or "Downy Mildew."
(Farmer types: “Powdery Mildew”)
If the Farmer says “no”:
Farmer: No
Bot:
No worries! Please share some details about the pest or disease you're encountering.
You can:
Upload a photo of the infestation 📸
Describe the issue in text ✍️
Use voice input 🎤
(Farmer uploads a photo of the infestation)
Bot:
Thank you for sharing the image! We’ll analyze this.
Here’s a list of resources that might help you manage powdery mildew on grapes.
You’ll find videos, PDFs, text-based guides, and audiobooks from trusted service providers.

Now, for the search API, we need the whole context of what the user has selected on the Whats App bot.

So on search API, we want a dynamic JSON that can be received at the BPP webhook to take certain actions based on the user's selection.

Goals

To have context on webhook what user journey is on BAP.

Expected Outcome

Support of dynamic JSON on search API.
Taking an example from above this can be similar to:
{message: "farmer's message", "type":"Pest and Disease Advisory", "crop": "grape", "disease": "Powdery Mildew",}

Here type, crop, and disease are dynamic fields that BAP might add to the search API.

Acceptance Criteria

• [ Capability of dynamic data on search API] [Criteria 1]

Domain

[UAI] Agriculture

Start by reviewing the search API and BPP webhook flow described in the issue, including how WhatsApp bot selections are represented. Confirm the required dynamic fields and their expected webhook behavior. Done means search requests can carry context such as type, crop, and disease and the BPP webhook can receive it.