HTTP Methods

Veyak supports all standard HTTP methods, plus WebSocket connections.

Supported Methods

Method Description Body Typical Use
GET Retrieve a resource No Fetch data
POST Create a resource Yes Submit data
PUT Replace a resource Yes Full update
PATCH Partially update a resource Yes Partial update
DELETE Remove a resource Optional Delete data
QUERY Safe request with a query payload Yes Complex queries (RFC 9110)
OPTIONS Describe communication options No CORS preflight
HEAD Same as GET but without body No Check headers
WS WebSocket connection — Real-time

Selecting a Method

Click the method dropdown on the left side of the URL bar to select any method. The dropdown is color-coded for quick identification:

  • 🟢 GET — Green
  • 🟡 POST — Amber
  • 🔵 PUT — Blue
  • 🟣 PATCH — Violet
  • 🔴 DELETE — Red
  • 🟠 QUERY — Orange
  • ⬡ OPTIONS / HEAD — Gray
  • 🩵 WS — Cyan

GET

Used to retrieve data from a server. GET requests do not have a body.

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

Query parameters can be added in the Params tab and are automatically appended to the URL.

POST

Used to send data to a server to create a resource. Supports multiple body modes:

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

{
  "name": "Alice",
  "email": "alice@example.com"
}

See Request Body for all body modes.

PUT

Replaces a resource entirely. Usually requires the full resource representation.

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

{
  "id": 1,
  "name": "Alice Updated",
  "email": "alice@example.com"
}

PATCH

Partially updates a resource. Only send the fields you want to change.

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

{
  "name": "Alice Renamed"
}

DELETE

Removes a resource. May include a body (optional).

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

OPTIONS

Typically used for CORS preflight requests. Veyak supports sending OPTIONS requests for debugging CORS issues.

Identical to GET, but the server responds with headers only — no body. Useful for checking if a resource exists or inspecting metadata.

QUERY

Sends a safe, idempotent request that can include a body payload, per the IETF HTTP QUERY specification. Useful for sending complex database filter criteria without exposing sensitive data in query string URLs.

QUERY https://api.example.com/items
Content-Type: application/json

{
  "filters": {
    "status": "active",
    "created_after": "2026-01-01"
  }
}

WebSocket (WS)

Select WS to open a WebSocket connection. See the WebSocket guide for full details.

Looking for gRPC?

Veyak also supports binary RPCs via gRPC (Unary, Server Streaming, Client Streaming, and Bidirectional Streaming) with dynamic protobuf reflection. See the dedicated gRPC Client guide.