Create Emails that are associated with a Domain Record

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…

This endpoint creates a record in the email log associated with the specified domain entity.

Note: It does not send the email. Logging and sending are separate concerns and emails must be sent through an alternate mechanism. This endpoint should be used only to record that an email was sent.

Path Params
string
required

This should match to the Domain Name in the system. It is case-sensitive. For Client Defined Entities it should start with "Custom.".

integer
required

This is the primary identifier for the parent record. For example, if my {domain} is Claim then the value provided here would be the ClaimID.

Query Params
boolean
Defaults to false

This field lets you decide whether creating this domain record should trigger a corresponding system event. If you’ve got external workflows or Data Entry Events and you don’t want them firing, be sure to set the value to false.

string
Defaults to EmailID,To,Subject,Body

This field lets you customize the shape of your response object. Just pass in a comma-separated list of the field names or attributes you want returned if the insert is successful. It’s a great way to confirm that your insert worked and get back the specific values you care about without having to make a separate API call. Think of it as a personalized snapshot of your newly created record.

Body Params
json
required
Defaults to { "To": "[email protected]", "Cc": "[email protected]", "Bcc": "[email protected]", "Subject": "Quarterly Risk Report Available", "Body": "Hello Jane,\n\nThe quarterly risk report is now available for review. Please let us know if you have any questions.\n\nRegards,\nRisk Operations", "Status": "S", "Direction": "O", "ReplyTo": "[email protected]", "Sender": "[email protected]", "SendDate": "2026-04-13T09:30:00", "ParentEmailID": 10245, "EntryUserID": 781, "EntryDate": "2026-04-13T09:25:00", "TrackReplies": true, "Priority": 0 }

Ensure the schema you provide here matches the schema of your Emails domain. View your Emails Data Dictionary here.

The example below illustrates a representative Emails payload using realistic, fictitious values.

{
  "To": "[email protected]",
  "Cc": "[email protected]",
  "Bcc": "[email protected]",
  "Subject": "Quarterly Risk Report Available",
  "Body": "Hello Jane,\n\nThe quarterly risk report is now available for review. Please let us know if you have any questions.\n\nRegards,\nRisk Operations",
  "Status": "S",
  "Direction": "O",
  "ReplyTo": "[email protected]",
  "Sender": "[email protected]",
  "SendDate": "2026-04-13T09:30:00",
  "ParentEmailID": 10245,
  "EntryUserID": 781,
  "EntryDate": "2026-04-13T09:25:00",
  "TrackReplies": true,
  "Priority": 0
}
string
enum
required
Defaults to O
Allowed:
Response

Language
Credentials
Header
URL
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json