Skip to content
Splashify Pro
Email docsEmail

Submit production access request

Request your account be moved out of sandbox into full production. Submission triggers an admin review. See Sandbox vs Production for the review criteria.

POST

/api/v1/partner/email/production-access

Request body

json
{
  "use_case": "We send transactional emails for our SaaS app — signup confirmations, password resets, payment receipts, weekly digest. Recipients are our paying customers who created accounts on our app.",
  "email_volume_estimate": "5000-15000 per day",
  "has_unsubscribe_method": true,
  "has_consent_proof": true
}

use_case needs at least 30 characters and both confirmations must be true, or the request is refused. Faking them violates AUP, and our team can pause an account that lied.

You can attach a supporting compliance document — CAN-SPAM attestation, opt-in proof, signed contract, registered-business certificate, etc. — to speed up the review. Submissions that include a relevant document are typically approved faster because the reviewer doesn't need to ask follow-up questions.

To attach a document, switch the request from JSON to multipart/form-data and include the file under the legal_document field. Our reviewer opens the file from your request.

Limits: PDF, PNG, or JPEG only. 10 MB max per file.

Response

json
{
  "success": true,
  "request_id": "550e8400-...",
  "status": "PENDING",
  "domain_verified": true,
  "message": "Request submitted. Review typically takes 24 business hours.",
  "legal_document_url": "https://folder.splashifypro.com/partner_email_production_access/...pdf",
  "legal_document_filename": "compliance-attestation-2026.pdf"
}

domain_verified reflects whether you currently have at least one domain identity in VERIFIED status — flagged on the admin side as a "ready for fast approval" signal.

legal_document_url and legal_document_filename are returned only when a document was uploaded with the request. Both fields are omitted otherwise.

Common errors

cURL — JSON (no document)

bash
curl https://api.splashifypro.com/api/v1/partner/email/production-access \
  -H "Authorization: Bearer $SPLASHIFY_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "use_case": "...",
    "email_volume_estimate": "5000 per day",
    "has_unsubscribe_method": true,
    "has_consent_proof": true
  }'
bash
curl https://api.splashifypro.com/api/v1/partner/email/production-access \
  -H "Authorization: Bearer $SPLASHIFY_API_KEY" \
  -F "use_case=We send transactional emails for our SaaS app..." \
  -F "email_volume_estimate=5000 per day" \
  -F "has_unsubscribe_method=true" \
  -F "has_consent_proof=true" \
  -F "legal_document=@./compliance-attestation.pdf"

Note the absence of Content-Type — curl -F sets the multipart boundary automatically.