Every API Request tool starts with a base URL and HTTP method. Chatevo substitutes path parameters and appends query parameters at runtime.
| Method | Typical use |
|---|
| GET | Read-only lookups (order status, availability, search) |
| POST | Create resources or actions that need a body |
| PUT | Full replace of a resource |
| PATCH | Partial update |
| DELETE | Remove or cancel a resource |
Use a full HTTPS URL. Path variables use {param_name} placeholders:
https://api.example.com/v1/orders/{order_id}
https://api.example.com/v1/hotels/{hotel_id}/rooms
| Rule | Detail |
|---|
| Scheme | https:// required in production |
| Path params | Match placeholders in the URL — see Path parameters |
| Trailing slash | Match your API exactly — some servers treat /orders and /orders/ differently |
| Method | Body |
|---|
| GET, DELETE | No JSON body — use path and query params only |
| POST, PUT, PATCH | Optional or required JSON body schema |
| Tool | Method | URL |
|---|
| Order lookup | GET | https://api.store.com/orders/{order_id} |
| Room search | GET | https://api.hotel.com/offers |
| Create booking | POST | https://api.hotel.com/bookings |
| Update profile | PATCH | https://api.crm.com/contacts/{contact_id} |
- Put dynamic segments in the path when they identify a resource (
{order_id}).
- Put filters, pagination, and search terms in query params (
?status=shipped&page=2).
- Keep URLs stable — changing the URL after go-live requires updating the tool and re-testing.
