HTTP
Send REST requests with methods, parameters, headers, and bodies.
HTTP is the default mode. It supports:
- Methods:
GET,POST,PUT,PATCH,DELETE,HEAD,OPTIONS, andSSE. - Query params, path variables, and headers as editable rows.
- Auth, body, scripts, request notes, and per-request settings.
- JSON, text, XML, HTML, form-data, urlencoded, GraphQL-shaped body, and binary-file bodies.
- cURL import from the URL bar.
Use HTTP for normal REST APIs. Use the SSE method only when the endpoint keeps an event stream open.
The method menu lists the HTTP methods on the left and the other protocols on the right.
To copy the request as cURL or client code, open Code snippets.
Suggestions while you type
Section titled “Suggestions while you type”Kurlo finishes what you are typing in faded text. Press Tab to accept it, or Escape to hide it.
- URL. Start typing a URL and Kurlo offers the rest of one you have sent or saved in this workspace, newest history first. In the URL field,
→at the end of the text accepts too. Typing the start of a request’s name offers that request’s URL instead, as increate order → {{baseUrl}}/orders. Suggestions come from requests of the same kind, so an HTTP request does not offer WebSocket addresses. - JSON body. When the request has saved examples, Kurlo offers the next key at the point where one can go: inside quotes you have opened, or on a new line after a comma. It uses the example bodies of this request, including the ones an OpenAPI import created from the spec’s schemas, follows the nested object you are in, and skips keys that are already there.
Path variables
Section titled “Path variables”A path segment that starts with a colon is a path variable: type {{baseUrl}}/users/:userId/posts/:postId and the Params tab lists userId and postId under Path variables, below the query params. Fill in the values there, and Kurlo puts them into the URL when it sends the request, so /users/:userId goes out as /users/42. The URL field keeps showing :userId.
- The rows follow the URL. Adding
:nameto the path adds a row, and removing it from the path removes the row. Renaming a variable means editing the URL. - Only a whole segment counts.
/users/:idhas a variable, while/v1:betaandhttp://localhost:8080do not, and the query string and fragment are left alone. - A value can use
{{variables}}, such as{{userId}}from the environment. - Characters that would change the URL’s structure, such as
/,?,#and spaces, are percent-encoded. Sequences that are already encoded, like%2F, are kept as they are. - A variable with an empty value stays in the URL as
:name. - Pre-request scripts see the URL with
:namein it, as Postman’s do, and can read and change the values withpm.request.pathVariables. - Path variables apply to HTTP, GraphQL, and SSE requests. Copy as cURL and generated code put the values into the URL. The mock server treats
:nameas “any value” when it matches requests against saved examples.