a9be15caf3
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
2.0 KiB
2.0 KiB
title, template, taxonomy, api
| title | template | taxonomy | api | |||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Test Email | api-endpoint |
|
|
Usage Notes
Quick Configuration Check
The simplest way to verify your email setup works end-to-end:
curl -X POST "https://yoursite.com/api/v1/email/test" \
-H "X-API-Key: grav_your_key" \
-H "X-Grav-Environment: localhost" \
-H "Content-Type: application/json" \
-d '{"to": "your@email.com"}'
Default Recipient
If you omit the to field, the test email is sent to the default recipient configured in the email plugin settings (plugins.email.to). If neither is set, the endpoint returns a 422 error.
Test Email Content
The test email contains:
- Subject: "Grav API - Test Email"
- Body: A simple HTML message with the send timestamp
- From: The configured sender address from email plugin settings
This is intentionally simple to isolate transport issues from content/template problems.