Query parameters
Query parameters append to the URL after ? — filters, search terms, dates, pagination, and flags. They are separate from path parameters embedded in the route.
Define query params
Section titled “Define query params”Add parameters with location: query in the tool schema. Chatevo URL-encodes values and builds the query string at execution time.
Schema fields
Section titled “Schema fields”| Field | Guidance |
|---|---|
| Name | Query key as your API expects (status, page, arrival) |
| Type | string, number, integer, boolean |
| Required | false for optional filters; true when the API requires the key |
| Description | Format hints — e.g. “ISO date YYYY-MM-DD for check-in” |
Example — room search
Section titled “Example — room search”URL: GET https://api.hotel.com/offers
| Query param | Type | Required | Description |
|---|---|---|---|
arrival | string | yes | Check-in date (YYYY-MM-DD) |
departure | string | yes | Check-out date (YYYY-MM-DD) |
adults | integer | yes | Number of adult guests |
currency | string | no | ISO currency code, default EUR |
Resulting request:
GET https://api.hotel.com/offers?arrival=2026-06-15&departure=2026-06-17&adults=2API key in query
Section titled “API key in query”Some APIs expect the key in the query string. Configure that on an API key credential with location: query — do not paste the secret into the param description.
Arrays and repeated keys
Section titled “Arrays and repeated keys”Document the expected format in the param description (status=open,closed vs repeated status=open&status=closed). Match what your backend accepts.
Path vs query
Section titled “Path vs query”| Path | Query |
|---|---|
/orders/{order_id} | ?status=shipped&limit=10 |
| Resource identity | Search and filters |