# DotMock protocols and interfaces

> DotMock preserves the interface an application already speaks while giving the development environment control over its data, state, timing, errors, streams, and outbound events.

## REST
Model payment, identity, shipping, CRM, and other HTTP dependencies with the paths, methods, schemas, state, latency, and failures your client expects.

- OpenAPI import and contract-shaped endpoints
- Conditional responses, persistent state, and proxy mode
- Traffic inspection and deterministic error paths
- Guide: https://dotmock.com/docs/quickstart

## GraphQL
Keep GraphQL operations native while controlling resolver data, partial errors, variables, mutations, and subscription events.

- Schema-aware queries and mutations
- GraphQL error envelopes and response data
- Subscription sequences for realtime tests
- Guide: https://dotmock.com/docs/guides/graphql

## SOAP
Exercise enterprise integrations against their real XML shape, operation names, namespaces, and typed SOAP faults.

- WSDL and XSD contract workflows
- SOAP envelope and operation matching
- Protocol-native fault responses
- Guide: https://dotmock.com/docs/guides/soap

## gRPC
Test Protobuf services with metadata, typed messages, status codes, and unary or streaming behavior without a live upstream.

- Service and method contracts
- Metadata and gRPC status behavior
- Unary and streaming test paths
- Guide: https://dotmock.com/docs/guides/grpc

## Realtime
Reproduce connection lifecycles and ordered message sequences, including delays, disconnects, and recovery behavior.

- WebSocket and server-sent event flows
- Timed sequences and connection state
- Disconnect and retry scenarios
- Guide: https://dotmock.com/docs/guides/realtime

## LLM APIs
Return provider-compatible chat, response, streaming, usage, tool-call, and failure payloads without spending against a model provider.

- Deterministic fixtures and tool calls
- Streaming, latency, and malformed output
- Usage and provider-shaped error responses
- Guide: https://dotmock.com/docs/features/llm-mocking

## Webhooks
Trigger signed outbound events, inspect attempts, and verify retry, delay, and failure handling as part of the same scenario.

- Signed event payloads
- Delay, retry, and failure policies
- Outbound-attempt inspection
- Guide: https://dotmock.com/docs/guides/webhook-workflows

## Related resources
- [How DotMock works](https://dotmock.com/how-it-works.md)
- [Protocol capability boundaries](https://dotmock.com/docs/reference/protocols.md)
- [Pricing](https://dotmock.com/pricing.md)

Canonical HTML: https://dotmock.com/protocols