Parameters and Body Data

​

Path Variables

https://api.example.com/users/:userId/posts/:postId

https://api.example.com/users/123/posts/456

​

Query Parameters

• Key: The parameter name
• Value: The parameter value
• Type: An enum to enforce the value type
• Description (optional): Internal documentation explaining the purpose of the parameter

• Adding uid=123 to https://app.requestly.io/echo results in: https://app.requestly.io/echo?uid=123

​

Bulk Edit Query Parameters

• Add one parameter per line
• Separate keys and values using a colon :
• Prefix any line with // to disable that parameter

page:1
limit:50
sort:desc
// filter:active

​

Request Body

​

Supported Body Types

• RAW (JSON/Text)
• x-www-form-urlencoded
• multipart/form-data
• GraphQL

Send raw data as plain text or structured JSON.When to use:

• Sending JSON data to REST APIs
• Posting XML or plain text
• Sending custom formatted data

You can select the language format:

• JSON – for structured data like API payloads
• Text – for plain string or unstructured data
• XML – for XML-based APIs
• HTML – for HTML content
• JavaScript: for JavaScript payloads

Example JSON:

{
  "name": "John Doe",
  "email": "[email protected]",
  "age": 30,
  "active": true
}

Sends data as URL-encoded key-value pairs. This format is commonly used for HTML form submissions.When to use:

• Traditional web form submissions
• Simple key-value data
• APIs that expect form data

Each field consists of:

• Key: Field name
• Value: Field value
• Description: Optional documentation

Example:

username=johndoe
password=secret123
remember=true

Used when uploading files along with form fields. Each field is sent as a separate part of the request body.When to use:

• Uploading images, documents, or files
• Sending files with metadata
• Form submissions with file attachments

Each field can be either:

• Text field: Regular key-value pair
• File field: File upload with browse button

Example use case: Uploading a user profile picture with name and bio

​

Per-field Content-Type

Each row has a Content-Type column. It sets the Content-Type header of that one part. Text rows and file rows both support it.Use it when an API needs a typed part. The common case is one JSON metadata part plus one file part in the same request:

Key	Type	Value	Content-Type
metadata	Text	{"title":"Q3 contract"}	application/json
file	File	contract.pdf	application/pdf

That request goes on the wire as:

--BOUNDARY
Content-Disposition: form-data; name="metadata"
Content-Type: application/json

{"title":"Q3 contract"}
--BOUNDARY
Content-Disposition: form-data; name="file"; filename="contract.pdf"
Content-Type: application/pdf

<file bytes>
--BOUNDARY--

BOUNDARY is the delimiter Requestly generates. It also appears in the request-level Content-Type header, as multipart/form-data; boundary=BOUNDARY.

Leave the field empty to use the default. The placeholder shows Auto. An empty value on a text row sends no Content-Type header for that part. An empty value on a file row sends application/octet-stream.

Requestly does not validate the value. You can enter any string, including an invalid MIME type, because a wrong content type is sometimes the case under test.Postman imports and exports carry this field on text rows, so the value survives a round-trip. File rows are a separate matter: Requestly cannot export the local file itself, so re-attach files after an import.Generated code snippets carry the value in curl: each typed part gains ;type=<value> in its --form argument. Other snippet languages follow their generator’s capability. python/requests keeps the type on file parts and drops it on text parts. Most other languages do the same. A few drop it on both parts, and a few keep it on both. Check the generated snippet before you rely on it for a typed part.

For GraphQL APIs, use the dedicated GraphQL request type which provides:

• Query/Mutation editor with syntax highlighting
• Variables panel
• Schema introspection, or a schema you attach yourself from a file or a URL

Learn more in our GraphQL Request guide.

​

Autogenerated Headers

​

What’s Next?