Fill in the base URL, a path with variables such as {userId} and the query parameters. The builder encodes each part correctly, warns about variables you have not filled in, and turns the request into cURL, fetch, axios, Python, PHP or Go code. It runs in your browser; no request is sent.
https://api.example.com/v1/users/{userId}/ordersFill in the path variables: userId.
curl \
-H 'Accept: application/json' \
'https://api.example.com/v1/users/{userId}/orders'How each part is encoded
A path variable is a single segment, so a value like a/b must not create a new segment. Query values may contain & or =, which would otherwise split the parameter. The builder applies encodeURIComponent to both.
| Part | Input | In the URL |
|---|---|---|
| Path variable | reports/2026 Q1 | reports%2F2026%20Q1 |
| Query value | Tom & Jerry | Tom%20%26%20Jerry |
| Query key with brackets | filter[status] | filter%5Bstatus%5D |
Brackets in keys are percent-encoded here. Servers that use the filter[status]=active convention, such as PHP and Rails, decode the key before reading it, so both forms reach the application the same way. See nested objects in query strings for the conventions.
The parameter presets
The preset buttons add common parameter names as a starting point. They are conventions, not a standard: check the API's documentation for the names it uses, for example limit instead of per_page, or a cursor instead of a page number.