Documentation Index
Fetch the complete documentation index at: https://docs.lobstr.io/llms.txt
Use this file to discover all available pages before exploring further.
Test endpoints allow you to verify your delivery configurations work correctly before activating automatic delivery. Each delivery method has its own test endpoint.
Available Test Endpoints
| Endpoint | Route | Purpose |
|---|
| Test Email | /v1/delivery/test-email | Verify email address can receive notifications |
| Test Google Sheet | /v1/delivery/test-googlesheet | Verify sheet permissions and accessibility |
| Test Webhook | /v1/delivery/test-webhook | Verify webhook endpoint is reachable and responding |
| Test Amazon S3 | /v1/delivery/test-s3 | Verify S3 bucket permissions and credentials |
| Test SFTP | /v1/delivery/test-sftp | Verify SFTP server connectivity and credentials |
Your API authentication token. Value: Token YOUR_API_KEY
Must be application/json. Value: application/json
Query Parameters
The delivery method to test: ‘email’, ‘googlesheet’, ‘webhook’, ‘s3’, or ‘sftp’. Example: email
Test Email - Request Body
Email address to test. Example: "user@example.com"
Test Google Sheet - Request Body
Google Sheet URL to test permissions. Example: "https://docs.google.com/spreadsheets/d/1ly9nwTs-hNaFCzWtSljevSf16chs5Nn0PIv_TpQSEhA/edit?usp=sharing"
Test Webhook - Request Body
Webhook endpoint URL to test. Example: "https://your-webhook.com/endpoint"
Test Amazon S3 - Request Body
S3 bucket name to test. Example: "my-bucket"
(Optional) AWS Access Key for authentication. Example: "AKIAIOSFODNN7EXAMPLE"
(Optional) AWS Secret Key for authentication. Example: "wJalrXUtnFEMI/K7MDENG/bPxRfiCYEXAMPLEKEY"
Test SFTP - Request Body
SFTP server hostname or IP. Example: "sftp.example.com"
SFTP server port. Example: 22
SFTP username. Example: "user"
SFTP password. Example: "password"
Target directory path. Example: "/upload/path"
Always test your delivery configuration before activating automatic delivery to catch permission or connectivity issues early.
Test endpoints do not require a squid parameter - they only verify that your credentials and endpoints work.
A successful test response (success: true) means the configuration is valid, but doesn’t guarantee future deliveries will succeed if permissions change.
For webhook tests, check the status_code field to ensure your endpoint returns 200/201/202 as expected.
Test endpoints use the same validation logic as the actual delivery system, so a successful test is a reliable indicator.
Code Examples
curl -X POST "https://api.lobstr.io/v1/delivery/test-webhook" \
-H "Authorization: Token YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"url": "https://your-webhook.com/endpoint"
}'
Response
{
"success": true,
"status_code": 200
}