# Conditional responses

> Model success, validation, missing data, rate limits, faults, and upstream errors as explicit branches.

- Canonical URL: https://dotmock.com/docs/features/response-rules
- Capability status: Available
- Last verified: 2026-07-24

## Prerequisites
- A DotMock workspace you can access
- The API ID in $API_ID and its published runtime URL in $MOCK_URL when the example calls the mock

## In this guide
- A condition selects a full response
- Use conditions for domain outcomes
- Return the same error shape your client expects
- Do not use an application response to fake a broken connection
- Prove one branch at a time

## Verified boundaries
- Transport faults and application responses are distinct behaviors and should be configured separately.

Read the canonical guide for its complete examples and expected results: https://dotmock.com/docs/features/response-rules