Collections

Collections store reusable requests for HTTP, GraphQL, gRPC, and WebSocket. A saved request contains the protocol target, payload, headers or metadata, authorization, scripts, response history settings, and documentation.

Use Collections when the same request must be sent again, documented, or shared with your team.

Editor layout

The Collections workspace is split into these areas:

Common tabs

Every protocol starts with a Docs tab and ends with Scripts and Settings.

Protocol tabs

HTTP requests

HTTP requests use a method, URL, optional query params, headers, auth, and body.

Example HTTP target:

GET {{host}}/api/internal/tokens?limit={{limit}}

GraphQL requests

GraphQL requests are saved as a query or mutation plus variables and HTTP-style request options.

Example:

query Account($id: ID!) {
  account(id: $id) {
    id
    balance
  }
}

{
  "id": "{{account_id}}"
}

gRPC requests

gRPC requests use service and method selection, metadata, a JSON message, and proto or reflection settings.

Use gRPC requests for service-to-service APIs where a proto service and method define the contract.

WebSocket requests

WebSocket requests model a connection plus one or more messages.

Use WebSocket requests for realtime APIs, subscriptions, and streaming message checks.

Variables and scripts

Requests use {{variable}} templates resolved from collection and folder variables, the selected environment, and script-created values. See Environments and Scripts.

Share docs

Share docs on a collection's Overview publishes the collection's documentation as a read-only web page. Anyone with the link can read it without an account, so you can send API docs to a partner, a customer, or a teammate who doesn't use Requestarium.

The page lists every request in tree order, grouped by folder, with its method, URL, docs (Markdown), headers, and, if you keep Include request bodies as examples on, its body. Header values that look like credentials (Authorization, Cookie, API keys, tokens) are masked unless they are a {{variable}}; check bodies for secrets before you share.

• The page is a snapshot. After you change the collection, open Shared docs and click Update page: the content is replaced and the link stays the same.
• Copy link copies the address. The link is long and random, and the page asks search engines not to index it.
• Turn off link stops the page at once. Sharing again makes a new link, so the old one never works again.

Publishing and turning the link off need write access to the collection. Sharing docs is available on every plan.