⚠️ This documentation is not complete and will change. Documentation and API References are actively being updated.
curl --request POST \
--url https://api.propops.app/api/email/send \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '
{
"template_key": "job_assigned",
"recipient_email": "contractor001@example.com",
"csrf_token": "abc123def456",
"recipient_name": "Contractor_001",
"variables": {
"job_ref": "JOB-001",
"job_title": "Boiler Service - Unit 001"
}
}
'{
"success": true,
"message": "Operation completed successfully"
}Send a transactional email via the Brevo integration using a configured template. Required permission: api.email.send.manage
curl --request POST \
--url https://api.propops.app/api/email/send \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '
{
"template_key": "job_assigned",
"recipient_email": "contractor001@example.com",
"csrf_token": "abc123def456",
"recipient_name": "Contractor_001",
"variables": {
"job_ref": "JOB-001",
"job_title": "Boiler Service - Unit 001"
}
}
'{
"success": true,
"message": "Operation completed successfully"
}All API requests must include a valid Bearer token in the Authorization header.
Tokens are 64-character SHA-256 session hashes issued by the PropOps authentication system.
Example:
Authorization: Bearer a1b2c3d4e5f6..."job_assigned"
"contractor001@example.com"
"abc123def456"
"Contractor_001"
Show child attributes
{
"job_ref": "JOB-001",
"job_title": "Boiler Service - Unit 001"
}