Advanced
Customize the built-in features and create your own gateways, methods, flows, templates, rules, routes and outcomes.
The recipes use what SendMock ships. These pages show how to change it, and how to create what it does not ship. Each one has the steps in the UI, the same in the seed file or CLI, how to undo, and what still needs code.
Everything here can also be done by an AI agent: see Build it with AI.
Payments
| Page | Create or change |
|---|---|
| Create a payment gateway | a complete gateway SendMock does not ship, from its docs to a working checkout, redirect and notification |
| Create an email provider | an email API SendMock does not ship, from its docs to a working provider |
| Create an SMS provider | a regional or smaller SMS vendor, from its docs to a working provider with its own error codes |
| Create a payment method | a wallet, bank or card method with its own test values |
| Create a payment flow | the steps a checkout asks for, with your own labels |
Webhooks
| Page | Create or change |
|---|---|
| Create and edit templates | the shape of a request: edit a built-in, clone, write your own, share with your team |
| Request editor | body modes, Strict or Lenient rendering, custom signatures |
| Variables in depth | values from the message, random values, computed values, prompts, secrets |
| Rules and filters | exact filters with groups, not, headers and regex |
| Inbound routes in depth | reply routing by ticket, store and notify, Mailgun's Routes API |
Capture
| Page | Create or change |
|---|---|
| Catcher responses | how a bin answers: rules by path, templated bodies, delays, failure rates |
| Email outcome addresses | your own addresses that bounce, defer, complain or are rejected |
| SMS outcome numbers | your own numbers that fail, arrive late or are read |
| OTP patterns | your app's code format |
| Numbers and Messaging Services | reply webhooks, fallbacks and sender pools |
| Chaos | SMTP rejections, latency and dropped connections |
Sharing and automation
| Page | Create or change |
|---|---|
| Seed file | your setup as a file in your repository, for your team and CI |
| Scenarios | multi-step tests you write once and run again |
What still needs code
Almost everything is data you can change. A few things need a change to SendMock itself: a new checkout step type, a new HTTP Catcher preset, and a provider's API calls beyond what a gateway or provider emulation already answers. Ask for them with a provider request issue (Help menu > Request a feature).
Share your setup
Export your endpoints, rules, templates, numbers and settings as a seed file, commit it, and give your team and CI the same SendMock.
Create a payment gateway
Emulate a payment provider SendMock does not ship, from its docs to a working checkout, redirect and notification, step by step.