Protocols¶
Mockly mocks 20 protocols from a single binary and config file. Each protocol section below covers its request matching options, response shaping, and any protocol-specific features (streaming, sequences, faults, etc.).
| Protocol | Typical use case |
|---|---|
| HTTP | REST APIs, webhooks, static/HTML pages, record mode |
| Outbound Webhooks | Server-initiated callbacks fired by an HTTP mock |
| WebSocket | Realtime/bidirectional messaging |
| gRPC | Unary and streaming RPCs from a .proto definition |
| GraphQL | Queries, mutations, and subscriptions |
| TCP | Raw byte-stream protocols |
| Redis | RESP-protocol commands |
| SMTP | Inbound mail capture |
| MQTT | Pub/sub messaging for IoT |
| NATS | Pub/sub and JetStream messaging |
| SNMP | Network device management (GET/GETNEXT/SET, traps) |
| DNS | Name resolution records |
| AMQP | RabbitMQ-style message queues |
| Kafka | Topic-based event streaming |
| LDAP | Directory lookups and binds |
| IMAP | Mailbox retrieval |
| FTP | File transfer |
| Memcached | Key-value caching |
| STOMP | Simple text-oriented messaging |
| CoAP | Constrained-device (IoT) messaging |
| SIP | VoIP signaling |
Every protocol shares the same core concepts — matching, templated responses, state conditions, and scenarios — documented once in Configuration; this section covers what's unique to each protocol.