Basic Syntax

Basic Syntax

Every .rext file contains one or more HTTP requests. This page covers the fundamental structure.

Request Structure

A request follows this order:

[directives]       → @name, @id, @collection, etc.
METHOD URL         → GET https://api.example.com/users
[headers]          → Content-Type: application/json
                   → (empty line)
[body]             → { "key": "value" }
                   → (empty line or @directive)
[post-directives]  → @assert, @capture

Delimiters

Requests are separated using one of three delimiters:

Delimiter	Description
###	Classic separator (can include text as comment)
---	Clean Markdown-style separator
Double empty line	Two consecutive empty lines implicitly separate requests

Example

### Auth Requests
POST https://api.example.com/auth/login
Content-Type: application/json

{
  "email": "user@example.com",
  "password": "secret"
}

---
GET https://api.example.com/users


GET https://api.example.com/profile

Supported Methods

Rext supports all standard HTTP methods:

GET · POST · PUT · PATCH · DELETE · HEAD · OPTIONS

GET https://api.example.com/users

POST https://api.example.com/users
Content-Type: application/json

{
  "name": "John",
  "email": "john@example.com"
}

DELETE https://api.example.com/users/123

Headers

Headers are defined as Key: Value pairs, one per line, immediately after the method line:

POST https://api.example.com/data
Content-Type: application/json
Authorization: Bearer {{token}}
X-Custom-Header: my-value

{
  "data": "payload"
}

Note

An empty line separates headers from the request body. If there’s no body, the empty line separates headers from the next delimiter or directive.

Request Body

The body comes after an empty line following the headers. Rext supports any content type:

JSON Body

POST https://api.example.com/users
Content-Type: application/json

{
  "name": "John",
  "email": "john@example.com"
}

Form Data

POST https://api.example.com/login
Content-Type: application/x-www-form-urlencoded

username=john&password=secret

Raw Text

POST https://api.example.com/webhook
Content-Type: text/plain

This is a raw text body

Comments

Any text after ### on the same line is treated as a comment:

### This is a comment about auth requests
POST https://api.example.com/auth/login

Next Steps

• Learn about variables and dynamic values
• Explore metadata directives like @name and @id