Protocols

Requests of every protocol live in collections beside HTTP requests, use the same variables and environments, and show their protocol in the tree and on their tab. To make one, open a collection or folder's add menu and choose a protocol under Other protocols.

Where an HTTP request has Send, other protocols have Invoke request, Connect or Subscribe, with Mod+Enter and the same command in the command palette. A connection that stays open ends with Disconnect or Unsubscribe. Each session's messages are kept in history as one entry, with secret values masked.

GraphQL

Write the query with completion and validation from the API's schema, which Porticol reads by introspection when you open the request or change its URL. Refresh schema reads it again, after a variable it depends on has changed. Pick the operation to run when a document has several, send a batch, attach files as uploads, and receive subscriptions over the graphql-ws protocol.

WebSocket

Connect with your own headers and subprotocols, then send text, JSON or binary messages, typed or saved with the request. The live log of messages has a filter. With reconnect on, a dropped connection is tried again up to five times, waiting from 1 to 16 seconds, and auth is refreshed before each try.

Server-sent events

Connect to an event stream and see each event with its id and type. A dropped stream reconnects and resumes from the last event it received, with Last-Event-ID.

gRPC

Read the services from server reflection, from .proto files with their import paths, or from a descriptor set. Write a message as a form or as JSON, and add metadata, a deadline, TLS and compression. Unary calls are invoked, and the server-streaming, client-streaming and bidirectional kinds run as sessions. gRPC-Web is supported too; its calls of every kind are invoked, since a gRPC-Web stream arrives as one body.

MQTT

Connect to a broker over MQTT 3.1.1 or 5, with TLS, a last will and connection properties. The user name and password come from the request's Basic auth, or from the URL. Publish with a QoS level and the retain flag, and subscribe to topics to see messages as they arrive.

SOAP

Load a WSDL to list its operations, and Porticol writes a sample envelope for the one you choose, to edit as XML. SOAP 1.1 and 1.2 are both supported. A WS-Security username token takes its credentials from the request's Basic auth. The response is shown as formatted XML.

TCP and UDP

A TCP request connects to a tcp:// or tls:// address and sends text or hex. Every message it receives is shown in hex, and as text when it is printable. A UDP request sends one datagram and lists the replies that arrive before its timeout, 2000 ms unless you change it.