Email audit documentation workflows
Reusable SDK examples for the MailSlurp documentation: audit campaign HTML, read broken links, images and content issues, and list recent audits. Each file contains parameterized helpers. Importing or compiling a file makes no requests; call only the helpers you need. Audits check the HTML you pass in; they do not send email.
Install and configure
Set MAILSLURP_API_KEY in your server-side environment and keep it out of browser code and logs.
| Language | Source | Dependencies | Install or compile |
|---|---|---|---|
| JavaScript (Node.js 20+) | javascript/workflows.js |
mailslurp-client 17.6.0 |
npm install |
| Python (3.9+) | python/workflows.py |
mailslurp-client 17.6.0 |
python -m pip install -r requirements.txt |
| Java (11+) | java/EmailAuditWorkflows.java |
mailslurp-client-java 17.6.0 |
mvn test-compile -DskipTests |
| C# (.NET 8) | csharp/EmailAuditWorkflows.cs |
mailslurp 17.5.0 |
dotnet build |
The C# helper reports broken links, broken images and spelling, which is what the current mailslurp NuGet package (17.5.0) returns.
Each <gen> region is published as a documentation snippet named gen_<language>_<region>.