LuxSci

Authentication

authentication

In order to use any API commands, at any level, your client must first authenticate and obtain an authentication code. This authentication code can then be used to make one or more calls to API functions. our authentication "session" can also be revoked, immediately invalidating all authentication codes received for it (i.e., this is a "log out"). In order to authenticate, you will need your API Token, API Key, and your API Host name. This API request is different from authenticated request in that you do not need to send a cookie, and the way that the request is signed is different. See also [Authentication](/rest-api/mechanics.html#auth).


/auth

Parameters

Body parameters
Name Description
body

Responses

Status: 201 - Standard JSON response. No "data" keyword will be sent. See the "auth" keyword for your new authentication token.


revokeAuthentication

Revoke your authentication session and invalidate all authorization codes received. See also [Revocation](/rest-api/mechanics.html#revoke).


/auth

Parameters

Header parameters
Name Description
Cookie*

Responses

Status: 200 - Standard JSON response. No "data" keyword will be sent.


Content Library

createContentLibraryDirectory

Create a new Content Library directory.

Access control required to execute this endpoint: User Email: Content Library


/perl/api/v2/user/{username}/content_library/{directory}

Parameters

Path parameters
Name Description
username*
String
Required
directory*
String
Starting with the / following /content_library, this is the directory in {username} to create. This directory must not exist and, if it is a subdirectory, the parent directories must all exist.
Required
Header parameters
Name Description
Cookie

Responses

Status: 200 -


deleteContentLibraryDirectory

Delete an empty Content Library directory.

Access control required to execute this endpoint: User Email: Content Library


/perl/api/v2/user/{username}/content_library/{directory}

Parameters

Path parameters
Name Description
username*
String
Required
directory*
String
Starting with the / following /content_library, this is the directory in {username} to create. This directory must not exist and, if it is a subdirectory, the parent directories must all exist.
Required
Header parameters
Name Description
Cookie

Responses

Status: 200 -


deleteContentLibraryFile

Delete a file.

Access control required to execute this endpoint: User Email: Content Library


/perl/api/v2/user/{username}/content_library/{file_path}

Parameters

Path parameters
Name Description
username*
String
Required
file_path*
String
Required. Starting with the / following /content_library, this is the path of the file in {username} to delete. The path must not end in a training slash. Be sure to not use double slashes. Example: "/files/media/image.jpg".
Required
Header parameters
Name Description
Cookie

Responses

Status: 200 -


getContentLibraryDirectory

Retrieve details about the specific Content Library directory.

Access control required to execute this endpoint: User Email: Content Library


/perl/api/v2/user/{username}/content_library/{directory}

Parameters

Path parameters
Name Description
username*
String
Required
directory*
String
Starting with the / following /content_library, this is the directory in {username} to examine. The path must end in a training slash. Be sure to not use double slashes. Note, for example, that for directory "/files/media/" you would insert "files/media/" in this variable. If this value is omitted, the contents of the top-level directory will be returned.
Required
Header parameters
Name Description
Cookie

Responses

Status: 200 - The response contains two main parts. "meta" reflects details about the directory requested and "items" is a list of details about the files and directories in this directory.


getContentLibraryFile

Retrieve details about the specific Content Library file.

Access control required to execute this endpoint: User Email: Content Library


/perl/api/v2/user/{username}/content_library/{file_path}

Parameters

Path parameters
Name Description
username*
String
Required
file_path*
String
Required. Starting with the / following /content_library, this is the path of the file in {username}. The path must not end in a training slash. Be sure to not use double slashes. Example: "/files/media/image.jpg".
Required
Header parameters
Name Description
Cookie

Responses

Status: 200 -


uploadContentLibraryFile

Upload a new file to the Content Library.

Access control required to execute this endpoint: User Email: Content Library


/perl/api/v2/user/{username}/content_library/{file_path}

Parameters

Path parameters
Name Description
username*
String
Required
file_path*
String
Required. Starting with the / following /content_library, this is the path in {username} to place the file. The path must not end in a training slash. Be sure to not use double slashes. Example: "files/media/image.jpg".
Required
Header parameters
Name Description
Cookie
Body parameters
Name Description
body

Responses

Status: 200 -


Domains

createDomain

Create a new domain in your account. Note: the domain MUST be either a subdomain or have client-managed DNS. For HIPAA accounts, all new domains will be locked down for HIPAA compliance unless the account is configured as “HIPAA Flexible.” In that case, all new domains cannot be created via the API. Your API Interface looks to see how many domains were added to your account in the past 24 hours. If this number is equal or greater than your API create limit, then your API will reject additional domain creation requests until that situation changes. See your API Interface configuration page for your domain creation limit.

Access control required to execute this endpoint: Account: Domains - Manage


/perl/api/v2/account/{accountId}/domains

Parameters

Path parameters
Name Description
accountId*
String
Required
Header parameters
Name Description
Cookie
Body parameters
Name Description
body

Responses

Status: 200 - OK


deleteDomain

Remove a domain from your account. If the domain is currently in use (e.g. has users, web sites, has premium filtering or archival, has managed DNS, etc.), then it cannot be deleted. Note: the domain MUST be either a subdomain or have client-managed DNS.

Access control required to execute this endpoint: Account: Domains - Manage


/perl/api/v2/account/{accountId}/domains/{domainName}

Parameters

Path parameters
Name Description
accountId*
String
Required
domainName*
String
Required
Header parameters
Name Description
Cookie

Responses

Status: 200 - none


getDomainDetails

Get information about a specific domain. This is the same as the “Get Domain Report,” except that it returns data for 1 specific domain.

Access control required to execute this endpoint: Account: Domains - Manage


/perl/api/v2/account/{accountId}/domains/{domainName}

Parameters

Path parameters
Name Description
accountId*
String
Required
domainName*
String
Required
Header parameters
Name Description
Cookie

Responses

Status: 200 - The data will be a single object with the keys and values for the domain requested, as per the “Get Domains Report” API call, above. Note that for this call, the data is returned without an enclosing array, as there is always exactly 1 object in the response.


getDomainsReport

Get information about your domains.

Access control required to execute this endpoint: Account: Domains - Manage


/perl/api/v2/account/{accountId}/domains

Parameters

Path parameters
Name Description
accountId*
String
Required
Header parameters
Name Description
Cookie

Responses

Status: 200 - The data field of the response is an array of all domains in your account.


updateDomain

Change selected domain settings. You can change one or multiple settings via one call. Settings that are omitted will not be altered.

Access control required to execute this endpoint: Account: Domains - Manage


/perl/api/v2/account/{accountId}/domains/{domainName}

Parameters

Path parameters
Name Description
accountId*
String
Required
domainName*
String
Required
Header parameters
Name Description
Cookie
Body parameters
Name Description
body

Responses

Status: 200 - none


Email

createCustomBounceDomain

Add a new Custom Bounce Domain to the account. The bounce domain must be a subdomain of the from domain in question, have DKIM configured already, and the DNS must already be a CNAME to any of the target domains listed in the Custom Bounce Domains user interface area.

Access control required to execute this endpoint: Account: Domains - Manage


/perl/api/v2/account/{accountId}/bounce_domain

Parameters

Path parameters
Name Description
accountId*
String
Required
Header parameters
Name Description
Cookie
Body parameters
Name Description
body

Responses

Status: 200 - OK


createDkim

Create a new DKIM configuration in your account.

Access control required to execute this endpoint: Account: Domains - Manage


/perl/api/v2/account/{accountId}/dkim

Parameters

Path parameters
Name Description
accountId*
String
Required
Header parameters
Name Description
Cookie
Body parameters
Name Description
body

Responses

Status: 200 - OK


deleteDkim

Remove a DKIM definition from your account.

Access control required to execute this endpoint: Account: Domains - Manage


/perl/api/v2/account/{accountId}/dkim/{domainName}

Parameters

Path parameters
Name Description
accountId*
String
Required
domainName*
String
Required
Header parameters
Name Description
Cookie

Responses

Status: 200 - none


deleteEmailAutoResponder

Delete an email auto-responder number `id` that belongs to the user.

Access control required to execute this endpoint: User Email - Auto-Responders


/perl/api/v2/user/{username}/email/ar/{id}

Parameters

Path parameters
Name Description
username*
String
Required
id*
String
Required
Header parameters
Name Description
Cookie

Responses

Status: 200 - ""


getDkimDetails

Get information about a specific DKIM configuration. This is the same as the “Get DKIM Report,” except that it returns data for 1 specific domain.

Access control required to execute this endpoint: Account: Domains - Manage


/perl/api/v2/account/{accountId}/dkim/{domainName}

Parameters

Path parameters
Name Description
accountId*
String
Required
domainName*
String
Required
Header parameters
Name Description
Cookie

Responses

Status: 200 - The data will be a single object with the keys and values for the domain requested, as per the “Get DKIM Report” API call, above. Note that for this call, the data is returned without an enclosing array, as there is always exactly 1 object in the response'


getDkimReport

Get information about your DKIM configurations.

Access control required to execute this endpoint: Account: Domains - Manage


/perl/api/v2/account/{accountId}/dkim

Parameters

Path parameters
Name Description
accountId*
String
Required
Header parameters
Name Description
Cookie

Responses

Status: 200 - The data field of the response is an array of all DKIM definitions in your account.


getEmailAutoResponders

Return all email auto-responders owned by this user.

Access control required to execute this endpoint: User Email - Auto-Responders


/perl/api/v2/user/{username}/email/ar

Parameters

Path parameters
Name Description
username*
String
Required
Header parameters
Name Description
Cookie

Responses

Status: 200 - A successful response will return an array of objects, one for each auto-responder owned by this user.


newEmailAutoResponder

Create a new email auto-responer.

Access control required to execute this endpoint: User Email - Auto-Responders


/perl/api/v2/user/{username}/email/ar

Parameters

Path parameters
Name Description
username*
String
Required
Body parameters
Name Description
body

Responses

Status: 200 - A successful response will return the unique ID of the created auto-responder.


retrieveSecureLineRecipientListEncryptionData

When composing an email message, you may have a list of recipients and want to know what kind of encryption, if any, would be used for each recipient when it is finally sent out with SecureLine encryption. E.g. this can be used to (a) inform the sender of what encryption will be used, and (b) to discover ahead of time if there are some recipients for which a message cannot yet be encrypted (possible, for example, if SecureLine Escrow is setup to use question and answer authentication without a default fall-back question and answer). It is good to use this method before sending an encrypted message – so you can modify your recipient list and/or add additional required encryption information before sending. Note: This is a RPC-style call and hence uses a POST method even though we are “getting data”. We are interacting with the system rather than querying a specific resource.

Access control required to execute this endpoint: User Email - Sending


/perl/api/v2/user/{username}/email/compose/secureline/recipients

Parameters

Path parameters
Name Description
username*
String
Required
Header parameters
Name Description
Cookie
Body parameters
Name Description
body

Responses

Status: 200 - The response body for a successful request will contain a hash in the “data” field with one keyword, “recipients”. The value of “recipients” is a list. Each list element will be another list corresponding to one of your queried recipients.


updateEmailForwarding

This function allows you to alter the email forwarding (and denial/deletion) settings for the user.

Access control required to execute this endpoint: User Email - Forwarding


/perl/api/v2/user/{username}/email/forwarding

Parameters

Path parameters
Name Description
username*
String
Required
Header parameters
Name Description
Cookie
Body parameters
Name Description
body

Responses

Status: 200 - ""


Email Aliases

createAlias

Create new alias(es) in your account. Your API Interface looks to see how many aliases were added to your account in the past 24 hours. If this number is equal or greater than your API create limit, then your API will reject additional alias creation requests until that situation changes. See your API Interface configuration page for your alias creation limit. Note also that accounts are limited in the maximum number of email aliases permitted per domain. By default, this is 100 + 10 aliases per user in the domain. So, for a domain with 20 users, this would be 100 + 10x20 = 300 aliases.

Access control required to execute this endpoint: Account: Email Aliases - Manage


/perl/api/v2/account/{accountId}/aliases

Parameters

Path parameters
Name Description
accountId*
String
Required
Header parameters
Name Description
Cookie
Body parameters
Name Description
body

Responses

Status: 200 - OK


deleteAlias

Remove an alias with the specified alias email address from your account.

Access control required to execute this endpoint: Account: Email Aliases - Manage


/perl/api/v2/account/{accountId}/aliases/{aliasAddress}

Parameters

Path parameters
Name Description
accountId*
String
Required
aliasAddress*
String
Required
Header parameters
Name Description
Cookie

Responses

Status: 200 - none


getAliasDetails

Get information about a specific email alias.

Access control required to execute this endpoint: Account: Email Aliases - Manage


/perl/api/v2/account/{accountId}/aliases/{aliasAddress}

Parameters

Path parameters
Name Description
accountId*
String
Required
aliasAddress*
String
Required
Header parameters
Name Description
Cookie

Responses

Status: 200 - The data field of the response is an on object whose keywords and values correspond to those in the “Get Aliases Report”. This is the same as that function, except that it is targeted at a specific alias and thus instead of returning a list of alias detail objects, it simply returns the single alias detail object.


getAliasesReport

Get information about your email aliases including regular aliases user forwards, domain catchalls, and WebAide Group distribution lists.

Access control required to execute this endpoint: Account: Email Aliases - Manage


/perl/api/v2/account/{accountId}/aliases

Parameters

Path parameters
Name Description
accountId*
String
Required
Header parameters
Name Description
Cookie

Responses

Status: 200 - The data field of the response is an array of all aliases in your account.


updateAlias

Modify an existing alias in your account. This function allows you to modify regular email aliases in your account. It does not permit modification of “catch all” aliases, “user forwards,” and system aliases such as WebAide Group Distribution Lists. You can use this function to enable and disable aliases; however, you must use a separate API call to actually delete them.

Access control required to execute this endpoint: Account: Email Aliases - Manage


/perl/api/v2/account/{accountId}/aliases/{aliasAddress}

Parameters

Path parameters
Name Description
accountId*
String
Required
aliasAddress*
String
Required
Header parameters
Name Description
Cookie
Body parameters
Name Description
body

Responses

Status: 200 - None


Email Sending

createAccountSuppression

Add new email suppressions at the account level.

Access control required to execute this endpoint: User Email: Suppression


/perl/api/v2/account/{accountId}/suppression/

Parameters

Path parameters
Name Description
accountId*
Integer
Required
Header parameters
Name Description
Cookie
Body parameters
Name Description
body

Responses

Status: 200 - None


createCustomField

Create a Custom Field. These Custom Fields are useful for Secure Marketing v3 and for Advanced Secure High Volume. Note that for users in Teams, only Team Administrators are permitted to make new Custom Fields.

Access control required to execute this endpoint: User Email: Custom Fields


/perl/api/v2/user/{username}/fields

Parameters

Path parameters
Name Description
username*
String
Required
Header parameters
Name Description
Cookie
Body parameters
Name Description
body

Responses

Status: 200 -


createEmailContentTag

Define a new static email content tag.

Access control required to execute this endpoint: User Email: Templates


/perl/api/v2/user/{username}/content_tags

Parameters

Path parameters
Name Description
username*
String
Required
Header parameters
Name Description
Cookie
Body parameters
Name Description
body

Responses

Status: 200 - Results in the “data” component of the response.


createEmailTemplate

Create a new email template. Note, templates created via the API will be required to use the WYSIWYG template editor if edited in the user interface.

Access control required to execute this endpoint: User Email: Templates


/perl/api/v2/user/{username}/templates

Parameters

Path parameters
Name Description
username*
String
Required
Header parameters
Name Description
Cookie
Body parameters
Name Description
body

Responses

Status: 200 - Results in the “data” component of the response.


createEmailTemplateGroup

Create a new email template group.

Access control required to execute this endpoint: User Email: Templates


/perl/api/v2/user/{username}/template_group/{template_group_id}

Parameters

Path parameters
Name Description
username*
String
Required
Header parameters
Name Description
Cookie
Body parameters
Name Description
body

Responses

Status: 200 - Results in the data component of the response.


createUserSuppression

Add new email suppressions at the user level.

Access control required to execute this endpoint: User Email: Suppression


/perl/api/v2/user/{username}/suppression/

Parameters

Path parameters
Name Description
username*
String
Required
Header parameters
Name Description
Cookie
Body parameters
Name Description
body

Responses

Status: 200 - None


deleteAccountSuppression

Delete a specific account-level email suppression.

Access control required to execute this endpoint: User Email: Suppression


/perl/api/v2/account/{accountId}/suppression/{email}

Parameters

Path parameters
Name Description
accountId*
String
Required
email*
String
Suppression email address to be deleted.
Required
Header parameters
Name Description
Cookie

Responses

Status: 200 - none


deleteEmailContentTag

Delete a specific email content tag.

Access control required to execute this endpoint: User Email: Templates


/perl/api/v2/user/{username}/content_tags/{tag_id}

Parameters

Path parameters
Name Description
username*
String
Required
tag_id*
String
tag_id can be either the unique numerical tag_id or the text code_word
Required
Header parameters
Name Description
Cookie

Responses

Status: 200 - none


deleteEmailTemplate

Delete a specific email template.

Access control required to execute this endpoint: User Email: Templates


/perl/api/v2/user/{username}/template/{template_id}

Parameters

Path parameters
Name Description
username*
String
Required
template_id*
String
template_id can be either the unique numerical template_id or the text code_word
Required
Header parameters
Name Description
Cookie

Responses

Status: 200 - none


deleteEmailTemplateGroup

Delete a specific email template group.

Access control required to execute this endpoint: User Email: Templates


/perl/api/v2/user/{username}/template_group/{template_group_id}

Parameters

Path parameters
Name Description
username*
String
Required
template_group_id*
String
Unique Id for this template group.
Required
Header parameters
Name Description
Cookie

Responses

Status: 200 - none


deleteUserSuppression

Delete a specific user-level email suppression.

Access control required to execute this endpoint: User Email: Suppression


/perl/api/v2/user/{username}/suppression/{email}

Parameters

Path parameters
Name Description
username*
String
Required
email*
String
Suppression email address to be deleted.
Required
Header parameters
Name Description
Cookie

Responses

Status: 200 - none


getAccountSuppression

Retrieve a specific email suppression at the account level.

Access control required to execute this endpoint: User Email: Suppression


/perl/api/v2/account/{accountId}/suppression/{email}

Parameters

Path parameters
Name Description
accountId*
Integer
Required
email*
String
Suppression email address to be retrieved. You are returning all suppression entries that contain the string 'email'. Note that even if you specify a full email address for 'email,' you can get multiple matches.
Required
Header parameters
Name Description
Cookie

Responses

Status: 200 - The data will be a single object that is a list containing one entry for each match. Each entry will itself be a list of the form: `[email, expires, account_id, domain_id, user_id]`. "email" is the email address suppressed. "expires" is the number of days until it expires, or zero if it does not expire. account_id is the customer account id. domain_id is zero for account-level entries or the domain name id for domain and user-level entries. user_id is zero except for user-level suppression entries, in which case it is the end user id number.


getAccountSuppressionList

Retrieve all email suppressions at the account level. See also the newer and more general function: getAccountSuppressionReport.

Access control required to execute this endpoint: User Email: Suppression


/perl/api/v2/account/{accountId}/suppression/

Parameters

Path parameters
Name Description
accountId*
String
Required
Header parameters
Name Description
Cookie

Responses

Status: 200 - The data will be a single object that is a list containing one entry for each match. Each entry will itself be a list of the form: `[email, expires, account_id, domain_id, user_id]`. "email" is the email address suppressed. "expires" is the number of days until it expires, or zero if it does not expire. account_id is the customer account id. domain_id is zero for account-level entries, or the domain name id for domain and user-level entries. user_id is zero except for user-level suppression entries, in which case it is the end user id number.


getCustomFields

Retrieve a list of all Custom Fields visible to user {username}. These Custom Fields are useful for Secure Marketing v3 and for Advanced Secure High Volume.

Access control required to execute this endpoint: User Email: Custom Fields


/perl/api/v2/user/{username}/fields

Parameters

Path parameters
Name Description
username*
String
Required
Header parameters
Name Description
Cookie

Responses

Status: 200 -


getDomainSmtpTlsCapability

This function checks if a specific domain name supports “good” SMTP TLS for email delivery to its users. This means: - All MX records are working - SMTP TLS is supported by all MX records - TLS support includes TLS v1.0+ and strong (NIST 800-52 recommended) ciphers like AES256. For more background, see: - [About SMTP TLS](https://luxsci.com/blog/smtp-tls-all-about-secure-email-delivery-over-tls.html) - [What Level of SSL/TLS is needed for HIPAA?](https://luxsci.com/blog/level-ssl-tls-required-hipaa.html)

Access control required to execute this endpoint: User Email - Sending


/perl/api/v2/user/{username}/email/compose/secureline/tls/{domain}

Parameters

Path parameters
Name Description
username*
String
Required
domain*
String
Required
Header parameters
Name Description
Cookie

Responses

Status: 200 - The response body for a successful request will have a keywords and data in the “data” in the JSON response.


getEmailContentTag

The call returns the specific details around a specific Email Content Tag

Access control required to execute this endpoint: User Email: Templates


/perl/api/v2/user/{username}/content_tags/{tag_id}

Parameters

Path parameters
Name Description
username*
String
Required
tag_id*
String
can either be the numerical unique ID of the Cotent Tag, or its 'code_word'
Required
Header parameters
Name Description
Cookie

Responses

Status: 200 - Results in the “data” component of the response.


getEmailContentTagList

This function returns a list of all content tags accessible to you.

Access control required to execute this endpoint: User Email: Templates


/perl/api/v2/user/{username}/content_tags

Parameters

Path parameters
Name Description
username*
String
Required
Header parameters
Name Description
Cookie

Responses

Status: 200 - Results in the “data” component of the response. The data component is a list of associated arrays. Each associate array corresponds to a single content tag


getEmailTemplate

The call returns the specific details around a specific Email Template.

Access control required to execute this endpoint: User Email: Templates


/perl/api/v2/user/{username}/template/{template_id}

Parameters

Path parameters
Name Description
username*
String
Required
template_id*
String
can either be the numerical unique ID of the template, or the textual “code_word”
Required
Header parameters
Name Description
Cookie

Responses

Status: 200 - Results in the “data” component of the response.


getEmailTemplateGroups

This function returns a list of all templates groups accessible to you.

Access control required to execute this endpoint: User Email: Templates


/perl/api/v2/user/{username}/template_groups

Parameters

Path parameters
Name Description
username*
String
Required
Header parameters
Name Description
Cookie

Responses

Status: 200 - Results in the data component of the response. The data component is a list of associated arrays. Each associate array corresponds to a single template group.


getEmailTemplateList

This function returns a list of all templates accessible to you.

Access control required to execute this endpoint: User Email: Templates


/perl/api/v2/user/{username}/templates

Parameters

Path parameters
Name Description
username*
String
Required
Header parameters
Name Description
Cookie
Query parameters
Name Description
user_id
Integer
Restricts the templates returned to only those owned by a specific user, [user_id]. This is relevent when [username] used belongs to a Team. In that case, all non-private Templates of all Team members are returned by this call unless this parameter is specified.

Responses

Status: 200 - Results in the “data” component of the response. The data component is a list of associated arrays. Each associate array corresponds to a single template.


getUserSuppression

Retrieve a specific email suppression at the user level.

Access control required to execute this endpoint: User Email: Suppression

. See also the newer and more general function: getUserSuppressionReport.


/perl/api/v2/user/{username}/suppression/{email}

Parameters

Path parameters
Name Description
username*
String
Required
email*
String
Suppression email address to be retrieved. You are returning all suppression entries that contain the string 'email'. Note that even if you specify a full email address for 'email,' you can get multiple matches.
Required
Header parameters
Name Description
Cookie

Responses

Status: 200 - The data will be a single object that is a list containing one entry for each match. Each entry will itself be a list of the form: [email, expires, account_id, domain_id, user_id, date_time_created, notes]. "email" is the email address suppressed. "expires" is the number of days until it expires, or zero if it does not expire. account_id is the customer account id. domain_id is zero for account-level entries, or the domain name id for domain and user-level entries. user_id is zero except for user-level suppression entries, in which case it is the end user id number. "date_time_created" is in GMT.


getUserSuppressionList

Retrieve all email suppressions at the user level in a simple list.

Access control required to execute this endpoint: User Email: Suppression


/perl/api/v2/user/{username}/suppression/

Parameters

Path parameters
Name Description
username*
String
Required
Header parameters
Name Description
Cookie

Responses

Status: 200 - The data will be a single object that is a list containing one entry for each match. Each entry will itself be a list of the form: [email, expires, account_id, domain_id, user_id, date_time_created, notes]. "email" is the email address suppressed. "expires" is the number of days until it expires, or zero if it does not expire. account_id is the customer account id. domain_id is zero for account-level entries, or the domain name id for domain and user-level entries. user_id is zero except for user-level suppression entries, in which case it is the end user id number. "date_time_created" is in GMT.


sendEmail

This API call is a generic outbound email sending interface that is designed to enable efficient large-scale email sending through your account’s email servers. It is ideal for Secure High Volume email sending. See - [sendEmail vs sendSecureEmailOrSecureText endpoints](/rest-api/sending-email.html) for sending email via the LuxSci API. This API function is used to send message(s) through your account’s SMTP server(s). You can think of it as an API-based proxy to SMTP, used for cases where direct use of SMTP is not an option. Generally speaking, direct use of SMTP is overall faster and more efficient; however, the API does include some things that you cannot get through direct SMTP connections. For example, the API includes support for failover, load-balanced SMTP servers; this can be done with direct SMTP only if you have a load balancer in front of your servers. You can also hand off messages to LuxSci (into the outbound queues) faster through the API than you can through direct SMTP. As this is a proxy for SMTP, the majority of the email message processing actually happens on the SMTP servers themselves (just like it would if you had actually used direct SMTP to send the message). The API call accepts the message, vets your ability to send the message, queues the message, and the moves it to the appropriate SMTP servers for delivery. This API process is designed to be very safe and efficient and works well for customers with very large SMTP sending limits (e.g., millions of messages per month). This API function allows you to optionally include attachments. If you wish to include attachments, you must format your request as a `multipart/form-data` request as discussed in the [API Mechanics Guide](/rest-api/mechanics.html). If the API call 'fails' it may be because more information is needed to encrypt the message to your recipients, if the request is malformed, or if your sending has exceeded some limit. Here are some limits to be aware of 1. The sending user must have an SMTP license. 2. The sending user must have a SecureLine license to use SecureLine-specific parameters. 3. You have to send to at least 1 recipient, but no more than 100 recipients per message. This limit can be increased on dedicated servers. 4. Your API call can contain 1 to 1000 messages. This limit can be increased on dedicated servers. 5. The total number of recipients across all messages in your API call cannot exceed 1000. This limit can be increased on dedicated servers. 6. The messages sent by a user through this API call count towards the users’ daily and monthly SMTP sending (just as if the user had actually used direct SMTP to send) totals. So, messages will be rejected if a user exceeds any of these limits. Please contact support if you need to upgrade these limits. 7. While SecureLine-encrypted emails sending is supported through this API call, SecureText sending is not. 8. If there are restrictions configured in the Domain Administration control panel on to whom the sending user can send messages, these restrictions also apply to messages sent through the API. 9. The total size of the message subject, body, and all attachments (raw size) must be less than or equal to 66% the sender’s SMTP message sending size limit. This limit can be affected by use of Email Archival, custom domain-level size limits, and general global limits. The current value of this limit can be found in the “Maximum Message Size Limit” for the sender’s domain in your domain administration settings area. 66% is used because, when the attachments are encoded into an actual email message, the size can bloat to 140-150% of the raw size; the SMTP message size limit looks at the size of the encoded messages passing through your SMTP servers. Note that once messages sent via this API arrive on your SMTP server for processing and delivery, those messages are subject to any server delivery rate limiting settings currently enabled on the SMTP server. For example, if your SMTP server is “warming up” its IP address by slowly increasing its outbound email delivery rate, messages sent by the API through that server may be delayed by that warmup rate limit. **Maximizing your sending rate:** To deposit email messages in the outbound queues as fast as possible using the API, we recommend 1. Send as many messages as you can in each API call. This “pipelining” greatly reduces the number of API calls you need to execute and greatly speeds up processing of your messages. 2. When sending same attachments in multiple messages, use the API’s feature for including the attachment once and referencing it in each of the actual messages. This will greatly speed up the uploading/posting of your message information to the API server. 3. Keep the messages as small as possible. 4. If appropriate for your use case, send fewer messages. Have more recipients per message (using the `bcc` field if needed). 5. Ask support about dedicated API servers. If all of the server resources are dedicated to your account, your throughput can be higher. You can also use multiple load-balanced dedicated API sending servers to scale your throughput capacity. 6. Use the `priority` field to ensure that more important messages are processed and delivered before less important messages. Under ideal conditions, you should be able to deposit outbound email messages in the API queues much faster that your email servers can actually deliver those messages to the actual recipients (unless you have a number of powerful dedicated email servers). That is OK, your email servers will just process and delivery them as fast as they can. The actual rate of message delivery to the recipients will be a function of how many email servers you have, what their specs are, how busy they are, and many other factors involved in SMTP email delivery – such as the recipients’ DNS response time, the recipient’s inbound email server speeds, etc.

Access control required to execute this endpoint: User Email: Sending


/perl/api/v2/user/{username}/email/send

Parameters

Path parameters
Name Description
username*
String
Required
Header parameters
Name Description
Cookie
Body parameters
Name Description
body
Form parameters
Name Description
json
userusernameemailsend_json
files
array[byte[]] (binary)

Responses

Status: 200 - The response body for a successful request will contain a hash in the “data” field. The value of this data field is an array which lists the unique sendmail_id codes for each of the messages sent. These codes can be used in the reporting API functions to look up delivery status and other message details. If multiple messages were sent in a single API call, multiple sendmail_id codes will be returned and the order of the codes in the array will exactly match the order of the messages in the API call.


sendSecureEmailOrSecureText

Send Secure Email and/or SecureText messages through your WebMail servers. This API endpoint is deprecated; use the sendEmail endpoint instead. See [sendEmail vs sendSecureEmailOrSecureText endpoints](/rest-api/sending-email.html) for sending email via the LuxSci API.

Access control required to execute this endpoint: User Email: Sending


/perl/api/v2/user/{username}/email/compose/secureline/send

Parameters

Path parameters
Name Description
username*
String
Required
Header parameters
Name Description
Cookie
Body parameters
Name Description
body

Responses

Status: 200 - ""


updateEmailContentTag

This content tag update call will update/replace ALL FIELDS. So, include all fields, as omitted fields will be treated as if you are updating them with empty or false values. This is effectively just like deleting the old tag with this `tag_id` and replacing it with the new data. Note, this call does not allow you to change the type of a Contet Tag or alter the inclusion rules for Dynamic Content Tags.

Access control required to execute this endpoint: User Email: Templates


/perl/api/v2/user/{username}/content_tags/{tag_id}

Parameters

Path parameters
Name Description
username*
String
Required
tag_id*
String
tag_id can be either the unique numerical tag_id or the code_word.
Required
Header parameters
Name Description
Cookie
Body parameters
Name Description
body

Responses

Status: 200 - None


updateEmailTemplate

This template update call will update/replace ALL FIELDS. So, include all fields, as omitted fields will be treated as if you are updating them with empty or false values. This is effectively just like deleting the old template with this `template_id` and replacing it with the new data. Note, any template updated from the API will be required to use the WYSIWYG template editor when edited in the user interface.

Access control required to execute this endpoint: User Email: Templates


/perl/api/v2/user/{username}/template/{template_id}

Parameters

Path parameters
Name Description
username*
String
Required
template_id*
String
template_id can be either the unique numerical template_id or the text code_word.
Required
Header parameters
Name Description
Cookie
Body parameters
Name Description
body

Responses

Status: 200 - None


updateEmailTemplateGroup

Update the Template Group name.

Access control required to execute this endpoint: User Email: Templates


/perl/api/v2/user/{username}/template_group/{template_group_id}

Parameters

Path parameters
Name Description
username*
String
Required
template_group_id*
String
Unique Id for this template group.
Required
Header parameters
Name Description
Cookie
Body parameters
Name Description
body

Responses

Status: 200 - None


Legacy Marketing

addMarketingCampaign

Create a new email broadcast campaign.

Access control required to execute this endpoint: Marketing - Campaign Management


/perl/api/v2/account/{accountId}/marketing/addCampaign

Parameters

Path parameters
Name Description
accountId*
String
Required
Header parameters
Name Description
Cookie
Body parameters
Name Description
body

Responses

Status: 200 - OK


addMarketingContact

Add New Contact.

Access control required to execute this endpoint: Marketing - Contact Management


/perl/api/v2/account/{accountId}/marketing/addContact

Parameters

Path parameters
Name Description
accountId*
String
Required
Header parameters
Name Description
Cookie
Body parameters
Name Description
body

Responses

Status: 200 - OK


addMarketingContacts

Add New Contacts.

Access control required to execute this endpoint: Marketing - Contact Management

This is a bulk wrapper around addContact. You specify multiple contacts in the contacts list element. The response contains a list of API response call results for each API add request. Use of addContacts is the same as calling addContact multiple times; however, it is somewhat more efficient.


/perl/api/v2/account/{accountId}/marketing/addContacts

Parameters

Path parameters
Name Description
accountId*
String
Required
Header parameters
Name Description
Cookie
Body parameters
Name Description
body

Responses

Status: 200 - OK


addMarketingList

Add New Contact List.

Access control required to execute this endpoint: Marketing - List Management


/perl/api/v2/account/{accountId}/marketing/addList

Parameters

Path parameters
Name Description
accountId*
String
Required
Header parameters
Name Description
Cookie
Body parameters
Name Description
body

Responses

Status: 200 - Includes ID and fields matching those sent in the request or which you would normally get from contact list queries. Ses the getLists.


addNewMarketingSuppression

Add New Suppression.

Access control required to execute this endpoint: Marketing - Suppression


/perl/api/v2/account/{accountId}/marketing/suppress

Parameters

Path parameters
Name Description
accountId*
String
Required
Header parameters
Name Description
Cookie
Body parameters
Name Description
body

Responses

Status: 200 - The response is an associative array


deleteMarketingCampaign

Delete a Campaign.

Access control required to execute this endpoint: Marketing - Campaign Management


/perl/api/v2/account/{accountId}/marketing/deleteCampaign/{id}

Parameters

Path parameters
Name Description
accountId*
String
Required
id*
Integer
Required
Header parameters
Name Description
Cookie

Responses

Status: 200 - OK


deleteMarketingContactById

Delete Contact By ID.

Access control required to execute this endpoint: Marketing - Contact Management


/perl/api/v2/account/{accountId}/marketing/deleteContact/{id}

Parameters

Path parameters
Name Description
accountId*
String
Required
id*
Integer
Required
Header parameters
Name Description
Cookie

Responses

Status: 200 - ""


deleteMarketingList

Note: deleting a contact list will delete any contacts in that list.

Access control required to execute this endpoint: Marketing - List Management


/perl/api/v2/account/{accountId}/marketing/deleteList/{id}

Parameters

Path parameters
Name Description
accountId*
String
Required
id*
String
List Id.
Required
Header parameters
Name Description
Cookie

Responses

Status: 200 - OK


deleteMarketingListGroup

Note: deleting a contact list group will NOT delete any contact lists in that group; they will merely become unassociated with any group.

Access control required to execute this endpoint: Marketing - List Management


/perl/api/v2/account/{accountId}/deleteListGroup/{id}

Parameters

Path parameters
Name Description
accountId*
String
Required
id*
String
List group Id.
Required
Header parameters
Name Description
Cookie

Responses

Status: 200 - OK


deleteMarketingSuppression

Delete Suppression.

Access control required to execute this endpoint: Marketing - Suppression


/perl/api/v2/account/{accountId}/marketing/deleteSuppressed/{type}

Parameters

Path parameters
Name Description
accountId*
String
Required
type*
String
email, domain, ip Select type of suppression
Required
Header parameters
Name Description
Cookie
Query parameters
Name Description
id
Integer
id of the suppressed entry
reference
String
Select suppressed records according to this reference you want to delete

Responses

Status: 200 - OK


getMarketingCampaignBouncedStatistics

Get Campaign bounced statistics.

Access control required to execute this endpoint: Marketing - Statistics


/perl/api/v2/account/{accountId}/marketing/getCampaignStatsBounced/{schedule_id}

Parameters

Path parameters
Name Description
accountId*
String
Required
schedule_id*
Integer
Schedule id of schedule to get bounced stats
Required
Header parameters
Name Description
Cookie
Query parameters
Name Description
limit_start
Integer
Starting row of result. Default: 0
limit_count
Integer
Number of records to get. Default: 25

Responses

Status: 200 - OK


getMarketingCampaignClickedStatistics

Get Campaign email link clicked statistics.

Access control required to execute this endpoint: Marketing - Statistics


/perl/api/v2/account/{accountId}/marketing/getCampaignStatsClicked/{schedule_id}

Parameters

Path parameters
Name Description
accountId*
String
Required
schedule_id*
Integer
Schedule id of schedule to get clicked stats
Required
Header parameters
Name Description
Cookie
Query parameters
Name Description
limit_start
Integer
Starting row of result. Default: 0
limit_count
Integer
Number of records to get. Default: 25

Responses

Status: 200 - OK


getMarketingCampaignGroups

Get Campaign Groups.

Access control required to execute this endpoint: Marketing - Campaign Management


/perl/api/v2/account/{accountId}/marketing/getMarketingCampaignGroups

Parameters

Path parameters
Name Description
accountId*
String
Required
Query parameters
Name Description
id
Integer
id of the campaign group to fetch details for.
user_id
Integer
Get campaign groups of a particular user.
limit_start
Integer
Starting row of result. Default: 0
limit_count
Integer
Number of records to get. Default: 25

Responses

Status: 200 - OK


getMarketingCampaignOpenedStatistics

Get Campaign email opened statistics.

Access control required to execute this endpoint: Marketing - Statistics


/perl/api/v2/account/{accountId}/marketing/getCampaignStatsOpened/{schedule_id}

Parameters

Path parameters
Name Description
accountId*
String
Required
schedule_id*
Integer
Schedule id of schedule to get open stats
Required
Header parameters
Name Description
Cookie
Query parameters
Name Description
limit_start
Integer
Starting row of result. Default: 0
limit_count
Integer
Number of records to get. Default: 25

Responses

Status: 200 - OK


getMarketingCampaignStatisticsSummary

Get Campaign statistics summary.

Access control required to execute this endpoint: Marketing - Statistics


/perl/api/v2/account/{accountId}/marketing/getCampaignStatsSummary/{schedule_id}

Parameters

Path parameters
Name Description
accountId*
String
Required
schedule_id*
String
Schedule id of schedule to get its statatistics summary.
Required
Header parameters
Name Description
Cookie

Responses

Status: 200 - OK


getMarketingCampaignUnsubscribedStatistics

Get Campaign email unsubscribed statistics.

Access control required to execute this endpoint: Marketing - Statistics


/perl/api/v2/account/{accountId}/marketing/getCampaignStatsUnsubscribed/{schedule_id}

Parameters

Path parameters
Name Description
accountId*
String
Required
schedule_id*
Integer
Schedule id of schedule to get unsubscribe stats
Required
Header parameters
Name Description
Cookie
Query parameters
Name Description
limit_start
Integer
Starting row of result. Default: 0
limit_count
Integer
Number of records to get. Default: 25

Responses

Status: 200 - OK


getMarketingCampaigns

This call allows you to retrieve details on your campaigns.

Access control required to execute this endpoint: Marketing - Campaign Management


/perl/api/v2/account/{accountId}/marketing/getCampaigns

Parameters

Path parameters
Name Description
accountId*
String
Required
Header parameters
Name Description
Cookie
Query parameters
Name Description
id*
Integer
Use if you want to restrict details to specific Campaign id. If left blank, all your campaigns’ details will be returned.
Required
group_id*
Integer
Group id of the campaigns you want to get.
Required
limit_start*
Integer
Starting row of result. Default: 0
Required
limit_count*
Integer
Number of records to get. Default: 25
Required

Responses

Status: 200 - The response is an array of associated arrays


getMarketingContactById

This function allows you to get the details for specific contact using his/her contact ID.

Access control required to execute this endpoint: Marketing - Contact Management


/perl/api/v2/account/{accountId}/marketing/getContact/{id}

Parameters

Path parameters
Name Description
accountId*
String
Required
id*
Integer
Required
Header parameters
Name Description
Cookie
Query parameters
Name Description
full_details
Integer
If specified and set to 1, add contact details will be returned, including the values of all additional fields.

Responses

Status: 200 - OK


getMarketingContacts

This call permits you to get your contacts’ data from the system by specific list or in aggregate. None of the request body parameters are required, and if you leave them blank, the call will return all contacts’ data from all your lists.

Access control required to execute this endpoint: Marketing - Contact Management


/perl/api/v2/account/{accountId}/marketing/getContacts

Parameters

Path parameters
Name Description
accountId*
String
Required
Header parameters
Name Description
Cookie
Query parameters
Name Description
full_details
Integer
If specified and set to 1, add contact details will be returned, including the values of all additional fields.
list_id*
Integer
Contact list id for the contacts you want to get.
Required
limit_start*
Integer
Starting row of result. Default: 0
Required
limit_count*
Integer
Number of records to get. Default: 25
Required

Responses

Status: 200 - OK


getMarketingListGroups

Get Campaign List Groups.

Access control required to execute this endpoint: Marketing - Campaign Management


/perl/api/v2/account/{accountId}/marketing/getMarketingListGroups

Parameters

Path parameters
Name Description
accountId*
String
Required
Query parameters
Name Description
id
Integer
id of the List Group to fetch details for.
user_id
Integer
Get list groups of a particular user.
limit_start
Integer
Starting row of result. Default: 0
limit_count
Integer
Number of records to get. Default: 25

Responses

Status: 200 - OK


getMarketingLists

Return details about one or more specific Contact List(s). If you omit all parameters, all lists should be returned.

Access control required to execute this endpoint: Marketing - List Management


/perl/api/v2/account/{accountId}/marketing/getLists

Parameters

Path parameters
Name Description
accountId*
String
Required
Header parameters
Name Description
Cookie
Query parameters
Name Description
list_id
Integer
List id for the specific contact list you want details for.
group_id
Integer
Group id for all getting lists in a specific group

Responses

Status: 200 - This will return a list of associated arrays each containing standard list details.


getMarketingScheduledCampaigns

Get Scheduled Campaigns.

Access control required to execute this endpoint: Marketing - Campaign Management


/perl/api/v2/account/{accountId}/marketing/getMarketingScheduledCampaigns

Parameters

Path parameters
Name Description
accountId*
String
Required
Query parameters
Name Description
id
Integer
id of the campaign to fetch details for.
user_id
Integer
Get campaigns of a particular user.
limit_start
Integer
Number of records to get. Default: 25.
limit_count
Integer
Number of records to get. Default: 25.
t_start
Integer
The start time from when to fetch the scheduled campaign. Supported format (dd-mm-yyyy_hh-mm-ss)
t_end
Integer
The end time from when to fetch the scheduled campaign. Supported format (dd-mm-yyyy_hh-mm-ss)

Responses

Status: 200 - OK


getMarketingSuppressions

Get Suppressions.

Access control required to execute this endpoint: Marketing - Suppression


/perl/api/v2/account/{accountId}/marketing/getSuppressed

Parameters

Path parameters
Name Description
accountId*
String
Required
Header parameters
Name Description
Cookie
Query parameters
Name Description
type*
String
email, domain, ip Select type of suppression list you want to get
Required
id
Integer
id of the suppressed entry
reference
String
Get suppressed records according to this reference
limit_start
Integer
Starting row of result. Default: 0
limit_count
Integer
Number of records to get. Default: 25

Responses

Status: 200 - The response is an array of associative arrays.


markContactAsUnsubscribed

Changes a contact’s status to “unsubscribed.” This is more efficient than calling updateContact to make this change.

Access control required to execute this endpoint: Marketing - Contact Management


/perl/api/v2/account/{accountId}/markAsUnsubscribed/{id}

Parameters

Path parameters
Name Description
accountId*
String
Required
id*
String
Required
Header parameters
Name Description
Cookie

Responses

Status: 200 - OK


scheduleMarketingCampaign

Schedule Campaign.

Access control required to execute this endpoint: Marketing - Scheduling


/perl/api/v2/account/{accountId}/marketing/campaignSchedule

Parameters

Path parameters
Name Description
accountId*
String
Required
Header parameters
Name Description
Cookie
Body parameters
Name Description
body

Responses

Status: 200 - OK


updateMarketingCampaign

Update a Campaign.

Access control required to execute this endpoint: Marketing - Campaign Management


/perl/api/v2/account/{accountId}/marketing/updateCampaign/{id}

Parameters

Path parameters
Name Description
accountId*
String
Required
id*
String
Required
Header parameters
Name Description
Cookie
Body parameters
Name Description
body

Responses

Status: 200 - OK


updateMarketingContactByEmail

Update the details, including custom field values, of contacts with the specified email address.

Access control required to execute this endpoint: Marketing - Contact Management


/perl/api/v2/account/{accountId}/marketing/updateContact/{email}

Parameters

Path parameters
Name Description
accountId*
String
Required
email*
String
Required
Header parameters
Name Description
Cookie
Body parameters
Name Description
body

Responses

Status: 200 - OK


updateMarketingContactById

Update the details, including custom field values, of a contact, using their contact ID.

Access control required to execute this endpoint: Marketing - Contact Management


/perl/api/v2/account/{accountId}/marketing/updateContact/{id}

Parameters

Path parameters
Name Description
accountId*
String
Required
id*
String
Required
Header parameters
Name Description
Cookie
Body parameters
Name Description
body

Responses

Status: 200 - OK


updateMarketingList

Update information for existing Contact Lists such as From Name or From Address. This can also be used to assign custom fields to specific lists, but the custom field must exist in the platform in advance. Return contact information and other general metadata for the user.

Access control required to execute this endpoint: Marketing - List Management


/perl/api/v2/account/{accountId}/marketing/updateList/{id}

Parameters

Path parameters
Name Description
accountId*
String
Required
id*
String
List Id.
Required
Header parameters
Name Description
Cookie
Body parameters
Name Description
body

Responses

Status: 200 - Includes ID and fields matching those sent in the request or which you would normally get from contact list queries. Ses the getLists.


Legacy Marketing

addCampaign

Add New Campaign.

Access control required to execute this endpoint: User Marketing - Campaign Management


/perl/api/v2/user/{username}/marketing/campaigns

Parameters

Path parameters
Name Description
username*
String
Required
Header parameters
Name Description
Cookie
Body parameters
Name Description
body

Responses

Status: 200 - Includes new campaign ID.


addContact

Add New Contact List.

Access control required to execute this endpoint: User Marketing - Contact Management


/perl/api/v2/user/{username}/marketing/contact

Parameters

Path parameters
Name Description
username*
String
Required
Header parameters
Name Description
Cookie
Body parameters
Name Description
body

Responses

Status: 200 - Includes ID and fields matching those sent in the request or which you would normally get from contact list queries. Ses the getLists.


addContacts

Add New Contacts in Bulk.

Access control required to execute this endpoint: User Marketing - Contact Management


/perl/api/v2/user/{username}/marketing/contacts

Parameters

Path parameters
Name Description
username*
String
Required
Header parameters
Name Description
Cookie
Body parameters
Name Description
body *

Responses

Status: 200 - Returns the number of contacts added plus an array of hashes, one per contact posted. The order of contacts in the response array matches the order in the request array.


addList

Add New Contact List.

Access control required to execute this endpoint: User Marketing - List Management


/perl/api/v2/user/{username}/marketing/list

Parameters

Path parameters
Name Description
username*
String
Required
Header parameters
Name Description
Cookie
Body parameters
Name Description
body *

Responses

Status: 200 - Includes ID and fields matching those sent in the request or which you would normally get from contact list queries. Ses the getLists.


addListGroup

Create a new email list group.

Access control required to execute this endpoint: Marketing - List Management


/perl/api/v2/user/{username}/marketing/list_group/{list_group_id}

Parameters

Path parameters
Name Description
username*
String
Required
Header parameters
Name Description
Cookie
Body parameters
Name Description
body

Responses

Status: 200 - Results in the data component of the response.


deleteCampaign

Delete a campaign. Note that deleing a campaign will also delete logs and statistics and other data related to that campaign.

Access control required to execute this endpoint: Marketing - Campaign Management


/perl/api/v2/user/{username}/marketing/campaign/{campaign_id}

Parameters

Path parameters
Name Description
username*
String
Required
campaign_id*
String
Campaign Id.
Required
Header parameters
Name Description
Cookie

Responses

Status: 200 - OK


deleteContact

Delete a contact.

Access control required to execute this endpoint: Marketing - Contact Management


/perl/api/v2/user/{username}/marketing/contact/{contact_id}

Parameters

Path parameters
Name Description
username*
String
Required
contact_id*
String
List Id.
Required
Header parameters
Name Description
Cookie

Responses

Status: 200 - OK


deleteList

Note: deleting a contact list will delete any contacts in that list.

Access control required to execute this endpoint: Marketing - List Management


/perl/api/v2/user/{username}/marketing/list/{list_id}

Parameters

Path parameters
Name Description
username*
String
Required
id*
String
List Id.
Required
Header parameters
Name Description
Cookie
Query parameters
Name Description
contacts_only
Integer
If passed and true, this call will delete all contacts in the list, but the list itself will not be deleted.

Responses

Status: 200 - OK


deleteListGroup

Delete a specific email list group.

Access control required to execute this endpoint: Marketing - List Management


/perl/api/v2/user/{username}/marketing/list_group/{list_group_id}

Parameters

Path parameters
Name Description
username*
String
Required
list_group_id*
String
Unique Id for this list group.
Required
Header parameters
Name Description
Cookie

Responses

Status: 200 - none


getCampaign

Return details about the specified Campaign.

Access control required to execute this endpoint: User: Marketing - Campaign Management


/perl/api/v2/user/{username}/marketing/campaign/{campaign_id}

Parameters

Path parameters
Name Description
username*
String
Required
campaign_id*
Integer
Campaign id for the specific campaign you want details for.
Required
Header parameters
Name Description
Cookie

Responses

Status: 200 - This will return the specified Campign containing standard campaign details.


getCampaigns

Return summary data of all visible Campaigns. The Campaign creation date is used with date matching criteria. See also [API Reporting Basics](/rest-api/reporting.html) and [report header columns in the response.](/rest-api/report-responses.html#sm3_campaigns)

Access control required to execute this endpoint: User: Marketing - Reporting


/perl/api/v2/user/{username}/marketing/campaigns

Parameters

Path parameters
Name Description
username*
String
Required
Header parameters
Name Description
Cookie
Query parameters
Name Description
user_id
Integer
Select campaigns owned by the given user ID.
status
String
Campaign Status Enum.
use_date
String
This report uses the Campaign created date by default for all date-related filtering and sorting. Set this parameter to "modified" to instead used the modified date. Set it to "send_at" to use the date/time that the Campaign is scheduled to be sent. Any other value passed in this parameter will cause the "created" date to be used.
after_date
String
DATETIME. Return only matches dated after this date time. Format “YYYY-MM-DD HH:MM:SS” in GMT
before_date
String
DATETIME. Return only matches dated before this date time.
first_row
Integer
(Default value 0). All of the matches are sorted and numbered starting from 0. E.g. if you have 100,000 matches, these are rows 0 through 99,999. If you specify a first_row, then the returned matches will be those rows starting from that row. E.g. without a specification (or if you specify 0), you might get rows 0 through 49,999. In your next request you might specify first_row=50000 to get rows 50000 to 99,999.
from_date
String
DATETIME. Return only matches dated on or after this date time.
matches
Integer
(Default value 50000). You can set matches to any value from 0 to 50000. This sets the maximum number of matches that will be returned in response to your request. Note that if the response size starts to exceed 50MB, then the response can still include fewer than your “matches” number, to keep the response size reasonable. If you specify “0” here, then no matches will be returned; however, you will still get the information on the number of matches that there were. For asynchronous reports (ones where a destination is specified), the matches parameter is not limited to 50000, but it still defaults to 50000 if not specified. If you expect a larger number of rows, then you must explicitly approve the maximum size of the result set by setting matches appropriately. This helps prevent accidental queries that produce very larger result sets.
through_date
String
DATETIME. Return only matches dated before or on this date time.
destination
String
For reporting requests. Specifying a destination makes the report "asynchronous." This means that a background job will be created to run the report and upload the final CSV file to the requested destination. The API request to start the report will return immediately with a background "job number" and the filename that will be uploaded. The supported value of "destination" is currently only "sftp" for a Secure FTP upload over SSH (as opposed to ftps, which would be a Secure FTP upload over SSL). When "destination" is specified, additional destination parameters are also required. Note that for SFTP uploads, there is a 15-minute upload timeout -- uploads that take longer (e.g., due to slow SFTP servers) will be aborted. WARNING: Multiple concurrent large asynchronous report requests will impact your database performance: reports will take longer to generate and your LuxSci services will experience degraded/slower performance.
destination_directory
String
For asynchronous reporting requests. This optional parameter will be the subdirectory to change to on the SFTP server before uploading the report CSV file. Technically speaking, this will be the argument provided to the SFTP "chdir" command.
destination_hostname
String
For asynchronous reporting requests. This will be the hostname of the SFTP server to which the report CSV file should be uploaded.
destination_password
String
For asynchronous reporting requests. This will be the password to be used for the login to the SFTP server to which the report CSV file should be uploaded.
destination_username
String
For asynchronous reporting requests. This will be the username to be used for the login to the SFTP server to which the report CSV file should be uploaded.

Responses

Status: 200 - This will return a list of associated arrays each containing campaign summary data.


getContact

Return the specified Contact.

Access control required to execute this endpoint: Marketing - Contact Management


/perl/api/v2/user/{username}/marketing/contact/{contact_id}

Parameters

Path parameters
Name Description
username*
String
Required
contact_id*
Integer
Contact id for the specific contact list you want details for.
Required
Header parameters
Name Description
Cookie
Query parameters
Name Description
details
Integer
If details=1 (default) return custom fields.

Responses

Status: 200 - This will return the specified Contact containing standard contact details.


getContacts

Return all Contacts in the specified List. If no list is specified, then all contacts across all lists will be returned. The contact creation date is used with date matching criteria. See also [API Reporting Basics](/rest-api/reporting.html) and [report header columns in the response.](/rest-api/report-responses.html#sm3_contacts)

Access control required to execute this endpoint: Marketing - Reports


/perl/api/v2/user/{username}/marketing/contacts

Parameters

Path parameters
Name Description
username*
String
Required
Header parameters
Name Description
Cookie
Query parameters
Name Description
use_date
String
This report uses the created date by default for all date-related filtering and sorting. Set this parameter to "modified" to instead used the modified date. Any other value passed in this parameter will cause the "created" date to be used.
after_date
String
DATETIME. Return only matches dated after this date time. Format “YYYY-MM-DD HH:MM:SS” in GMT
before_date
String
DATETIME. Return only matches dated before this date time.
first_row
Integer
(Default value 0). All of the matches are sorted and numbered starting from 0. E.g. if you have 100,000 matches, these are rows 0 through 99,999. If you specify a first_row, then the returned matches will be those rows starting from that row. E.g. without a specification (or if you specify 0), you might get rows 0 through 49,999. In your next request you might specify first_row=50000 to get rows 50000 to 99,999.
from_date
String
DATETIME. Return only matches dated on or after this date time.
matches
Integer
(Default value 50000). You can set matches to any value from 0 to 50000. This sets the maximum number of matches that will be returned in response to your request. Note that if the response size starts to exceed 50MB, then the response can still include fewer than your “matches” number, to keep the response size reasonable. If you specify “0” here, then no matches will be returned; however, you will still get the information on the number of matches that there were. For asynchronous reports (ones where a destination is specified), the matches parameter is not limited to 50000, but it still defaults to 50000 if not specified. If you expect a larger number of rows, then you must explicitly approve the maximum size of the result set by setting matches appropriately. This helps prevent accidental queries that produce very larger result sets.
through_date
String
DATETIME. Return only matches dated before or on this date time.
destination
String
For reporting requests. Specifying a destination makes the report "asynchronous." This means that a background job will be created to run the report and upload the final CSV file to the requested destination. The API request to start the report will return immediately with a background "job number" and the filename that will be uploaded. The supported value of "destination" is currently only "sftp" for a Secure FTP upload over SSH (as opposed to ftps, which would be a Secure FTP upload over SSL). When "destination" is specified, additional destination parameters are also required. Note that for SFTP uploads, there is a 15-minute upload timeout -- uploads that take longer (e.g., due to slow SFTP servers) will be aborted. WARNING: Multiple concurrent large asynchronous report requests will impact your database performance: reports will take longer to generate and your LuxSci services will experience degraded/slower performance.
destination_directory
String
For asynchronous reporting requests. This optional parameter will be the subdirectory to change to on the SFTP server before uploading the report CSV file. Technically speaking, this will be the argument provided to the SFTP "chdir" command.
destination_hostname
String
For asynchronous reporting requests. This will be the hostname of the SFTP server to which the report CSV file should be uploaded.
destination_password
String
For asynchronous reporting requests. This will be the password to be used for the login to the SFTP server to which the report CSV file should be uploaded.
destination_username
String
For asynchronous reporting requests. This will be the username to be used for the login to the SFTP server to which the report CSV file should be uploaded.
list_id
Integer
List id to get all contacts in a specific List. If this is omitted, then all contacts across all Lists will be returned.
segment_id
Integer
Segment id to get all contacts in a specific Segment. Note that you can specify both a segment_id and a list_id to get contacts in a specific List that are also in a specific Segment.
details
Integer
Whe nset to true (1), data for all custom fields will also be included in the response.

Responses

Status: 200 - This will return a CSV style list of headers and list of associative arrays each containing standard contact details including custom fields.


getList

Return details about the specified Contact List.

Access control required to execute this endpoint: Marketing - List Management


/perl/api/v2/user/{username}/marketing/list/{list_id}

Parameters

Path parameters
Name Description
username*
String
Required
list_id*
Integer
List id for the specific contact list you want details for.
Required
Header parameters
Name Description
Cookie

Responses

Status: 200 - This will return the specified list containing standard list details.


getListGroups

This function returns a list of all lists groups accessible to you.

Access control required to execute this endpoint: Marketing - List Management


/perl/api/v2/user/{username}/marketing/list_groups

Parameters

Path parameters
Name Description
username*
String
Required
Header parameters
Name Description
Cookie

Responses

Status: 200 - Results in the data component of the response. The data component is a list of associated arrays. Each associate array corresponds to a single list group.


getLists

Return all Contact Lists. The list creation date is used with date matching criteria. See also [API Reporting Basics](/rest-api/reporting.html) and [report header columns in the response.](/rest-api/report-responses.html#sm3_lists)

Access control required to execute this endpoint: Marketing - Reports


/perl/api/v2/user/{username}/marketing/lists

Parameters

Path parameters
Name Description
username*
String
Required
Header parameters
Name Description
Cookie
Query parameters
Name Description
list_group_id
Integer
Group id getting all lists in a specific group
use_date
String
This report uses the created date by default for all date-related filtering and sorting. Set this parameter to "modified" to instead used the modified date. Any other value passed in this parameter will cause the "created" date to be used.
after_date
String
DATETIME. Return only matches dated after this date time. Format “YYYY-MM-DD HH:MM:SS” in GMT
before_date
String
DATETIME. Return only matches dated before this date time.
first_row
Integer
(Default value 0). All of the matches are sorted and numbered starting from 0. E.g. if you have 100,000 matches, these are rows 0 through 99,999. If you specify a first_row, then the returned matches will be those rows starting from that row. E.g. without a specification (or if you specify 0), you might get rows 0 through 49,999. In your next request you might specify first_row=50000 to get rows 50000 to 99,999.
from_date
String
DATETIME. Return only matches dated on or after this date time.
matches
Integer
(Default value 50000). You can set matches to any value from 0 to 50000. This sets the maximum number of matches that will be returned in response to your request. Note that if the response size starts to exceed 50MB, then the response can still include fewer than your “matches” number, to keep the response size reasonable. If you specify “0” here, then no matches will be returned; however, you will still get the information on the number of matches that there were. For asynchronous reports (ones where a destination is specified), the matches parameter is not limited to 50000, but it still defaults to 50000 if not specified. If you expect a larger number of rows, then you must explicitly approve the maximum size of the result set by setting matches appropriately. This helps prevent accidental queries that produce very larger result sets.
through_date
String
DATETIME. Return only matches dated before or on this date time.
destination
String
For reporting requests. Specifying a destination makes the report "asynchronous." This means that a background job will be created to run the report and upload the final CSV file to the requested destination. The API request to start the report will return immediately with a background "job number" and the filename that will be uploaded. The supported value of "destination" is currently only "sftp" for a Secure FTP upload over SSH (as opposed to ftps, which would be a Secure FTP upload over SSL). When "destination" is specified, additional destination parameters are also required. Note that for SFTP uploads, there is a 15-minute upload timeout -- uploads that take longer (e.g., due to slow SFTP servers) will be aborted. WARNING: Multiple concurrent large asynchronous report requests will impact your database performance: reports will take longer to generate and your LuxSci services will experience degraded/slower performance.
destination_directory
String
For asynchronous reporting requests. This optional parameter will be the subdirectory to change to on the SFTP server before uploading the report CSV file. Technically speaking, this will be the argument provided to the SFTP "chdir" command.
destination_hostname
String
For asynchronous reporting requests. This will be the hostname of the SFTP server to which the report CSV file should be uploaded.
destination_password
String
For asynchronous reporting requests. This will be the password to be used for the login to the SFTP server to which the report CSV file should be uploaded.
destination_username
String
For asynchronous reporting requests. This will be the username to be used for the login to the SFTP server to which the report CSV file should be uploaded.

Responses

Status: 200 - This will return a list of associated arrays each containing standard list details.


getReportBounced

Return bounce data/email delivery failure data of all selected Campaigns. Uses delivery_status_updated as the date matching criteria. See also [API Reporting Basics](/rest-api/reporting.html) and [report header columns in the response.](/rest-api/report-responses.html#sm3_campaign_report_bounces)

Access control required to execute this endpoint: User: Marketing - Reporting


/perl/api/v2/user/{username}/marketing/report/bounced

Parameters

Path parameters
Name Description
username*
String
Required
Header parameters
Name Description
Cookie
Query parameters
Name Description
campaign_ids
String
Select campaigns as string of comma-separated campaign ids. If omitted, all campaigns are selected.
detail
String
Boolean. If 1, include the values of all Contact Custom Fields in the report. Default is 0.
email
String
Filter results by matching any Contact email address containing the given string.
domain
String
Filter results by matching any Contact email address in a domain name containing the given string.
after_date
String
DATETIME. Return only matches dated after this date time. Format “YYYY-MM-DD HH:MM:SS” in GMT
before_date
String
DATETIME. Return only matches dated before this date time.
first_row
Integer
(Default value 0). All of the matches are sorted and numbered starting from 0. E.g. if you have 100,000 matches, these are rows 0 through 99,999. If you specify a first_row, then the returned matches will be those rows starting from that row. E.g. without a specification (or if you specify 0), you might get rows 0 through 49,999. In your next request you might specify first_row=50000 to get rows 50000 to 99,999.
from_date
String
DATETIME. Return only matches dated on or after this date time.
matches
Integer
(Default value 50000). You can set matches to any value from 0 to 50000. This sets the maximum number of matches that will be returned in response to your request. Note that if the response size starts to exceed 50MB, then the response can still include fewer than your “matches” number, to keep the response size reasonable. If you specify “0” here, then no matches will be returned; however, you will still get the information on the number of matches that there were. For asynchronous reports (ones where a destination is specified), the matches parameter is not limited to 50000, but it still defaults to 50000 if not specified. If you expect a larger number of rows, then you must explicitly approve the maximum size of the result set by setting matches appropriately. This helps prevent accidental queries that produce very larger result sets.
through_date
String
DATETIME. Return only matches dated before or on this date time.
destination
String
For reporting requests. Specifying a destination makes the report "asynchronous." This means that a background job will be created to run the report and upload the final CSV file to the requested destination. The API request to start the report will return immediately with a background "job number" and the filename that will be uploaded. The supported value of "destination" is currently only "sftp" for a Secure FTP upload over SSH (as opposed to ftps, which would be a Secure FTP upload over SSL). When "destination" is specified, additional destination parameters are also required. Note that for SFTP uploads, there is a 15-minute upload timeout -- uploads that take longer (e.g., due to slow SFTP servers) will be aborted. WARNING: Multiple concurrent large asynchronous report requests will impact your database performance: reports will take longer to generate and your LuxSci services will experience degraded/slower performance.
destination_directory
String
For asynchronous reporting requests. This optional parameter will be the subdirectory to change to on the SFTP server before uploading the report CSV file. Technically speaking, this will be the argument provided to the SFTP "chdir" command.
destination_hostname
String
For asynchronous reporting requests. This will be the hostname of the SFTP server to which the report CSV file should be uploaded.
destination_password
String
For asynchronous reporting requests. This will be the password to be used for the login to the SFTP server to which the report CSV file should be uploaded.
destination_username
String
For asynchronous reporting requests. This will be the username to be used for the login to the SFTP server to which the report CSV file should be uploaded.

Responses

Status: 200 - This will return a list of associated arrays each containing campaign bounce data.


getReportClicked

Return click data of all selected Campaigns. The click date is used with date matching criteria unless the "use_date" parameter is set to "sent". See also [API Reporting Basics](/rest-api/reporting.html) and [report header columns in the response.](/rest-api/report-responses.html#sm3_campaign_report_clicked)

Access control required to execute this endpoint: User: Marketing - Reporting


/perl/api/v2/user/{username}/marketing/report/clicked

Parameters

Path parameters
Name Description
username*
String
Required
Header parameters
Name Description
Cookie
Query parameters
Name Description
campaign_ids
String
Select campaigns as string of comma-separated campaign ids. If omitted, all campaigns are selected.
use_date
String
If set to "sent", use the date the message was sent, instead of the date of the open event, for date selections.
detail
String
Boolean. If 1, include the values of all Contact Custom Fields in the report. Default is 0.
email
String
Filter results by matching any Contact email address containing the given string.
domain
String
Filter results by matching any Contact email address in a domain name containing the given string.
after_date
String
DATETIME. Return only matches dated after this date time. Format “YYYY-MM-DD HH:MM:SS” in GMT
before_date
String
DATETIME. Return only matches dated before this date time.
first_row
Integer
(Default value 0). All of the matches are sorted and numbered starting from 0. E.g. if you have 100,000 matches, these are rows 0 through 99,999. If you specify a first_row, then the returned matches will be those rows starting from that row. E.g. without a specification (or if you specify 0), you might get rows 0 through 49,999. In your next request you might specify first_row=50000 to get rows 50000 to 99,999.
from_date
String
DATETIME. Return only matches dated on or after this date time.
matches
Integer
(Default value 50000). You can set matches to any value from 0 to 50000. This sets the maximum number of matches that will be returned in response to your request. Note that if the response size starts to exceed 50MB, then the response can still include fewer than your “matches” number, to keep the response size reasonable. If you specify “0” here, then no matches will be returned; however, you will still get the information on the number of matches that there were. For asynchronous reports (ones where a destination is specified), the matches parameter is not limited to 50000, but it still defaults to 50000 if not specified. If you expect a larger number of rows, then you must explicitly approve the maximum size of the result set by setting matches appropriately. This helps prevent accidental queries that produce very larger result sets.
through_date
String
DATETIME. Return only matches dated before or on this date time.
destination
String
For reporting requests. Specifying a destination makes the report "asynchronous." This means that a background job will be created to run the report and upload the final CSV file to the requested destination. The API request to start the report will return immediately with a background "job number" and the filename that will be uploaded. The supported value of "destination" is currently only "sftp" for a Secure FTP upload over SSH (as opposed to ftps, which would be a Secure FTP upload over SSL). When "destination" is specified, additional destination parameters are also required. Note that for SFTP uploads, there is a 15-minute upload timeout -- uploads that take longer (e.g., due to slow SFTP servers) will be aborted. WARNING: Multiple concurrent large asynchronous report requests will impact your database performance: reports will take longer to generate and your LuxSci services will experience degraded/slower performance.
destination_directory
String
For asynchronous reporting requests. This optional parameter will be the subdirectory to change to on the SFTP server before uploading the report CSV file. Technically speaking, this will be the argument provided to the SFTP "chdir" command.
destination_hostname
String
For asynchronous reporting requests. This will be the hostname of the SFTP server to which the report CSV file should be uploaded.
destination_password
String
For asynchronous reporting requests. This will be the password to be used for the login to the SFTP server to which the report CSV file should be uploaded.
destination_username
String
For asynchronous reporting requests. This will be the username to be used for the login to the SFTP server to which the report CSV file should be uploaded.

Responses

Status: 200 - This will return a list of associated arrays each containing campaign click data.


getReportComplaints

Return spam complaint data from all selected Campaigns. The message delivery status updated date is used by default for date selections, unless "use_date" is set to "sent". See also [API Reporting Basics](/rest-api/reporting.html) and [report header columns in the response.](/rest-api/report-responses.html#sm3_campaign_report_complaints)

Access control required to execute this endpoint: User: Marketing - Reporting


/perl/api/v2/user/{username}/marketing/report/complaints

Parameters

Path parameters
Name Description
username*
String
Required
Header parameters
Name Description
Cookie
Query parameters
Name Description
campaign_ids
String
Select campaigns as string of comma-separated campaign ids. If omitted, all campaigns are selected.
use_date
String
If set to "sent", use the date the message was sent, instead of the date of the open event, for date selections.
detail
String
Boolean. If 1, include the values of all Contact Custom Fields in the report. Default is 0.
email
String
Filter results by matching any Contact email address containing the given string.
domain
String
Filter results by matching any Contact email address in a domain name containing the given string.
after_date
String
DATETIME. Return only matches dated after this date time. Format “YYYY-MM-DD HH:MM:SS” in GMT
before_date
String
DATETIME. Return only matches dated before this date time.
first_row
Integer
(Default value 0). All of the matches are sorted and numbered starting from 0. E.g. if you have 100,000 matches, these are rows 0 through 99,999. If you specify a first_row, then the returned matches will be those rows starting from that row. E.g. without a specification (or if you specify 0), you might get rows 0 through 49,999. In your next request you might specify first_row=50000 to get rows 50000 to 99,999.
from_date
String
DATETIME. Return only matches dated on or after this date time.
matches
Integer
(Default value 50000). You can set matches to any value from 0 to 50000. This sets the maximum number of matches that will be returned in response to your request. Note that if the response size starts to exceed 50MB, then the response can still include fewer than your “matches” number, to keep the response size reasonable. If you specify “0” here, then no matches will be returned; however, you will still get the information on the number of matches that there were. For asynchronous reports (ones where a destination is specified), the matches parameter is not limited to 50000, but it still defaults to 50000 if not specified. If you expect a larger number of rows, then you must explicitly approve the maximum size of the result set by setting matches appropriately. This helps prevent accidental queries that produce very larger result sets.
through_date
String
DATETIME. Return only matches dated before or on this date time.
destination
String
For reporting requests. Specifying a destination makes the report "asynchronous." This means that a background job will be created to run the report and upload the final CSV file to the requested destination. The API request to start the report will return immediately with a background "job number" and the filename that will be uploaded. The supported value of "destination" is currently only "sftp" for a Secure FTP upload over SSH (as opposed to ftps, which would be a Secure FTP upload over SSL). When "destination" is specified, additional destination parameters are also required. Note that for SFTP uploads, there is a 15-minute upload timeout -- uploads that take longer (e.g., due to slow SFTP servers) will be aborted. WARNING: Multiple concurrent large asynchronous report requests will impact your database performance: reports will take longer to generate and your LuxSci services will experience degraded/slower performance.
destination_directory
String
For asynchronous reporting requests. This optional parameter will be the subdirectory to change to on the SFTP server before uploading the report CSV file. Technically speaking, this will be the argument provided to the SFTP "chdir" command.
destination_hostname
String
For asynchronous reporting requests. This will be the hostname of the SFTP server to which the report CSV file should be uploaded.
destination_password
String
For asynchronous reporting requests. This will be the password to be used for the login to the SFTP server to which the report CSV file should be uploaded.
destination_username
String
For asynchronous reporting requests. This will be the username to be used for the login to the SFTP server to which the report CSV file should be uploaded.

Responses

Status: 200 - This will return a list of associated arrays each containing campaign complaint data.


getReportLogs

Return sending log data of all selected Campaigns. This includes all metadata for each recipient, including the delivery status, open status, click staus, etc. The delivery status last updated date is used with date matching criteria. See also [API Reporting Basics](/rest-api/reporting.html) and [report header columns in the response.](/rest-api/report-responses.html#sm3_campaign_report_logs)

Access control required to execute this endpoint: User: Marketing - Reporting


/perl/api/v2/user/{username}/marketing/report/logs

Parameters

Path parameters
Name Description
username*
String
Required
Header parameters
Name Description
Cookie
Query parameters
Name Description
campaign_ids
String
Select campaigns as string of comma-separated campaign ids. If omitted, all campaigns are selected.
detail
String
Boolean. If 1, include the values of all Contact Custom Fields in the report. Default is 0.
email
String
Filter results by matching any Contact email address containing the given string.
domain
String
Filter results by matching any Contact email address in a domain name containing the given string.
after_date
String
DATETIME. Return only matches dated after this date time. Format “YYYY-MM-DD HH:MM:SS” in GMT
before_date
String
DATETIME. Return only matches dated before this date time.
first_row
Integer
(Default value 0). All of the matches are sorted and numbered starting from 0. E.g. if you have 100,000 matches, these are rows 0 through 99,999. If you specify a first_row, then the returned matches will be those rows starting from that row. E.g. without a specification (or if you specify 0), you might get rows 0 through 49,999. In your next request you might specify first_row=50000 to get rows 50000 to 99,999.
from_date
String
DATETIME. Return only matches dated on or after this date time.
matches
Integer
(Default value 50000). You can set matches to any value from 0 to 50000. This sets the maximum number of matches that will be returned in response to your request. Note that if the response size starts to exceed 50MB, then the response can still include fewer than your “matches” number, to keep the response size reasonable. If you specify “0” here, then no matches will be returned; however, you will still get the information on the number of matches that there were. For asynchronous reports (ones where a destination is specified), the matches parameter is not limited to 50000, but it still defaults to 50000 if not specified. If you expect a larger number of rows, then you must explicitly approve the maximum size of the result set by setting matches appropriately. This helps prevent accidental queries that produce very larger result sets.
through_date
String
DATETIME. Return only matches dated before or on this date time.
destination
String
For reporting requests. Specifying a destination makes the report "asynchronous." This means that a background job will be created to run the report and upload the final CSV file to the requested destination. The API request to start the report will return immediately with a background "job number" and the filename that will be uploaded. The supported value of "destination" is currently only "sftp" for a Secure FTP upload over SSH (as opposed to ftps, which would be a Secure FTP upload over SSL). When "destination" is specified, additional destination parameters are also required. Note that for SFTP uploads, there is a 15-minute upload timeout -- uploads that take longer (e.g., due to slow SFTP servers) will be aborted. WARNING: Multiple concurrent large asynchronous report requests will impact your database performance: reports will take longer to generate and your LuxSci services will experience degraded/slower performance.
destination_directory
String
For asynchronous reporting requests. This optional parameter will be the subdirectory to change to on the SFTP server before uploading the report CSV file. Technically speaking, this will be the argument provided to the SFTP "chdir" command.
destination_hostname
String
For asynchronous reporting requests. This will be the hostname of the SFTP server to which the report CSV file should be uploaded.
destination_password
String
For asynchronous reporting requests. This will be the password to be used for the login to the SFTP server to which the report CSV file should be uploaded.
destination_username
String
For asynchronous reporting requests. This will be the username to be used for the login to the SFTP server to which the report CSV file should be uploaded.

Responses

Status: 200 - This will return a list of associated arrays each containing sending event data.


getReportOpened

Return open event data of all selected Campaigns. The open date is used with date matching criteria, unless the "use_date" parameter is set to "sent". See also [API Reporting Basics](/rest-api/reporting.html) and [report header columns in the response.](/rest-api/report-responses.html#sm3_campaign_report_opened)

Access control required to execute this endpoint: User: Marketing - Reporting


/perl/api/v2/user/{username}/marketing/report/opened

Parameters

Path parameters
Name Description
username*
String
Required
Header parameters
Name Description
Cookie
Query parameters
Name Description
campaign_ids
String
Select campaigns as string of comma-separated campaign ids. If omitted, all campaigns are selected.
use_date
String
If set to "sent", use the date the message was sent, instead of the date of the open event, for date selections.
detail
String
Boolean. If 1, include the values of all Contact Custom Fields in the report. Default is 0.
email
String
Filter results by matching any Contact email address containing the given string.
domain
String
Filter results by matching any Contact email address in a domain name containing the given string.
after_date
String
DATETIME. Return only matches dated after this date time. Format “YYYY-MM-DD HH:MM:SS” in GMT
before_date
String
DATETIME. Return only matches dated before this date time.
first_row
Integer
(Default value 0). All of the matches are sorted and numbered starting from 0. E.g. if you have 100,000 matches, these are rows 0 through 99,999. If you specify a first_row, then the returned matches will be those rows starting from that row. E.g. without a specification (or if you specify 0), you might get rows 0 through 49,999. In your next request you might specify first_row=50000 to get rows 50000 to 99,999.
from_date
String
DATETIME. Return only matches dated on or after this date time.
matches
Integer
(Default value 50000). You can set matches to any value from 0 to 50000. This sets the maximum number of matches that will be returned in response to your request. Note that if the response size starts to exceed 50MB, then the response can still include fewer than your “matches” number, to keep the response size reasonable. If you specify “0” here, then no matches will be returned; however, you will still get the information on the number of matches that there were. For asynchronous reports (ones where a destination is specified), the matches parameter is not limited to 50000, but it still defaults to 50000 if not specified. If you expect a larger number of rows, then you must explicitly approve the maximum size of the result set by setting matches appropriately. This helps prevent accidental queries that produce very larger result sets.
through_date
String
DATETIME. Return only matches dated before or on this date time.
destination
String
For reporting requests. Specifying a destination makes the report "asynchronous." This means that a background job will be created to run the report and upload the final CSV file to the requested destination. The API request to start the report will return immediately with a background "job number" and the filename that will be uploaded. The supported value of "destination" is currently only "sftp" for a Secure FTP upload over SSH (as opposed to ftps, which would be a Secure FTP upload over SSL). When "destination" is specified, additional destination parameters are also required. Note that for SFTP uploads, there is a 15-minute upload timeout -- uploads that take longer (e.g., due to slow SFTP servers) will be aborted. WARNING: Multiple concurrent large asynchronous report requests will impact your database performance: reports will take longer to generate and your LuxSci services will experience degraded/slower performance.
destination_directory
String
For asynchronous reporting requests. This optional parameter will be the subdirectory to change to on the SFTP server before uploading the report CSV file. Technically speaking, this will be the argument provided to the SFTP "chdir" command.
destination_hostname
String
For asynchronous reporting requests. This will be the hostname of the SFTP server to which the report CSV file should be uploaded.
destination_password
String
For asynchronous reporting requests. This will be the password to be used for the login to the SFTP server to which the report CSV file should be uploaded.
destination_username
String
For asynchronous reporting requests. This will be the username to be used for the login to the SFTP server to which the report CSV file should be uploaded.

Responses

Status: 200 - This will return a list of associated arrays each containing campaign opened data.


getReportUnsubscribed

Return unsubscribe data of all selected Campaigns. The unsubscribe date is used with date matching criteria, unless the "use_date" parameter is set to "sent". See also [API Reporting Basics](/rest-api/reporting.html) and [report header columns in the response.](/rest-api/report-responses.html#sm3_campaign_report_unsubscribed)

Access control required to execute this endpoint: User: Marketing - Reporting


/perl/api/v2/user/{username}/marketing/report/unsubscribed

Parameters

Path parameters
Name Description
username*
String
Required
Header parameters
Name Description
Cookie
Query parameters
Name Description
campaign_ids
String
Select campaigns as string of comma-separated campaign ids. If omitted, all campaigns are selected.
use_date
String
If set to "sent", use the date the message was sent, instead of the date of the open event, for date selections.
detail
String
Boolean. If 1, include the values of all Contact Custom Fields in the report. Default is 0.
email
String
Filter results by matching any Contact email address containing the given string.
domain
String
Filter results by matching any Contact email address in a domain name containing the given string.
after_date
String
DATETIME. Return only matches dated after this date time. Format “YYYY-MM-DD HH:MM:SS” in GMT
before_date
String
DATETIME. Return only matches dated before this date time.
first_row
Integer
(Default value 0). All of the matches are sorted and numbered starting from 0. E.g. if you have 100,000 matches, these are rows 0 through 99,999. If you specify a first_row, then the returned matches will be those rows starting from that row. E.g. without a specification (or if you specify 0), you might get rows 0 through 49,999. In your next request you might specify first_row=50000 to get rows 50000 to 99,999.
from_date
String
DATETIME. Return only matches dated on or after this date time.
matches
Integer
(Default value 50000). You can set matches to any value from 0 to 50000. This sets the maximum number of matches that will be returned in response to your request. Note that if the response size starts to exceed 50MB, then the response can still include fewer than your “matches” number, to keep the response size reasonable. If you specify “0” here, then no matches will be returned; however, you will still get the information on the number of matches that there were. For asynchronous reports (ones where a destination is specified), the matches parameter is not limited to 50000, but it still defaults to 50000 if not specified. If you expect a larger number of rows, then you must explicitly approve the maximum size of the result set by setting matches appropriately. This helps prevent accidental queries that produce very larger result sets.
through_date
String
DATETIME. Return only matches dated before or on this date time.
destination
String
For reporting requests. Specifying a destination makes the report "asynchronous." This means that a background job will be created to run the report and upload the final CSV file to the requested destination. The API request to start the report will return immediately with a background "job number" and the filename that will be uploaded. The supported value of "destination" is currently only "sftp" for a Secure FTP upload over SSH (as opposed to ftps, which would be a Secure FTP upload over SSL). When "destination" is specified, additional destination parameters are also required. Note that for SFTP uploads, there is a 15-minute upload timeout -- uploads that take longer (e.g., due to slow SFTP servers) will be aborted. WARNING: Multiple concurrent large asynchronous report requests will impact your database performance: reports will take longer to generate and your LuxSci services will experience degraded/slower performance.
destination_directory
String
For asynchronous reporting requests. This optional parameter will be the subdirectory to change to on the SFTP server before uploading the report CSV file. Technically speaking, this will be the argument provided to the SFTP "chdir" command.
destination_hostname
String
For asynchronous reporting requests. This will be the hostname of the SFTP server to which the report CSV file should be uploaded.
destination_password
String
For asynchronous reporting requests. This will be the password to be used for the login to the SFTP server to which the report CSV file should be uploaded.
destination_username
String
For asynchronous reporting requests. This will be the username to be used for the login to the SFTP server to which the report CSV file should be uploaded.

Responses

Status: 200 - This will return a list of associated arrays each containing campaign unsubscribe data.


getReportUrls

Return clicked-on urls of all selected Campaigns. The click date is used with date matching criteria unless the "use_date" parameter is set to "sent". See also [API Reporting Basics](/rest-api/reporting.html) and [report header columns in the response.](/rest-api/report-responses.html#sm3_campaign_report_urls)

Access control required to execute this endpoint: User: Marketing - Reporting


/perl/api/v2/user/{username}/marketing/report/urls

Parameters

Path parameters
Name Description
username*
String
Required
Header parameters
Name Description
Cookie
Query parameters
Name Description
campaign_ids
String
Select campaigns as string of comma-separated campaign ids. If omitted, all campaigns are selected.
use_date
String
If set to "sent", use the date the message was sent, instead of the date of the open event, for date selections.
detail
String
Boolean. If 1, include the values of all Contact Custom Fields in the report. Default is 0.
email
String
Filter results by matching any Contact email address containing the given string.
domain
String
Filter results by matching any Contact email address in a domain name containing the given string.
after_date
String
DATETIME. Return only matches dated after this date time. Format “YYYY-MM-DD HH:MM:SS” in GMT
before_date
String
DATETIME. Return only matches dated before this date time.
first_row
Integer
(Default value 0). All of the matches are sorted and numbered starting from 0. E.g. if you have 100,000 matches, these are rows 0 through 99,999. If you specify a first_row, then the returned matches will be those rows starting from that row. E.g. without a specification (or if you specify 0), you might get rows 0 through 49,999. In your next request you might specify first_row=50000 to get rows 50000 to 99,999.
from_date
String
DATETIME. Return only matches dated on or after this date time.
matches
Integer
(Default value 50000). You can set matches to any value from 0 to 50000. This sets the maximum number of matches that will be returned in response to your request. Note that if the response size starts to exceed 50MB, then the response can still include fewer than your “matches” number, to keep the response size reasonable. If you specify “0” here, then no matches will be returned; however, you will still get the information on the number of matches that there were. For asynchronous reports (ones where a destination is specified), the matches parameter is not limited to 50000, but it still defaults to 50000 if not specified. If you expect a larger number of rows, then you must explicitly approve the maximum size of the result set by setting matches appropriately. This helps prevent accidental queries that produce very larger result sets.
through_date
String
DATETIME. Return only matches dated before or on this date time.
destination
String
For reporting requests. Specifying a destination makes the report "asynchronous." This means that a background job will be created to run the report and upload the final CSV file to the requested destination. The API request to start the report will return immediately with a background "job number" and the filename that will be uploaded. The supported value of "destination" is currently only "sftp" for a Secure FTP upload over SSH (as opposed to ftps, which would be a Secure FTP upload over SSL). When "destination" is specified, additional destination parameters are also required. Note that for SFTP uploads, there is a 15-minute upload timeout -- uploads that take longer (e.g., due to slow SFTP servers) will be aborted. WARNING: Multiple concurrent large asynchronous report requests will impact your database performance: reports will take longer to generate and your LuxSci services will experience degraded/slower performance.
destination_directory
String
For asynchronous reporting requests. This optional parameter will be the subdirectory to change to on the SFTP server before uploading the report CSV file. Technically speaking, this will be the argument provided to the SFTP "chdir" command.
destination_hostname
String
For asynchronous reporting requests. This will be the hostname of the SFTP server to which the report CSV file should be uploaded.
destination_password
String
For asynchronous reporting requests. This will be the password to be used for the login to the SFTP server to which the report CSV file should be uploaded.
destination_username
String
For asynchronous reporting requests. This will be the username to be used for the login to the SFTP server to which the report CSV file should be uploaded.

Responses

Status: 200 - This will return a list of associated arrays each containing campaign url data.


updateCampaign

Update information for existing Campaign.

Access control required to execute this endpoint: Marketing - Campaign Management


/perl/api/v2/user/{username}/marketing/campaign/{campaign_id}

Parameters

Path parameters
Name Description
username*
String
Required
campaign_id*
String
Campaign Id.
Required
Header parameters
Name Description
Cookie
Body parameters
Name Description
body

Responses

Status: 200 - OK


updateContact

Update information for existing Contact such as E-mail address or custom fields attached to the parent List.

Access control required to execute this endpoint: Marketing - Contact Management


/perl/api/v2/user/{username}/marketing/contact/{contact_id}

Parameters

Path parameters
Name Description
username*
String
Required
contact_id*
String
Contact Id.
Required
Header parameters
Name Description
Cookie
Body parameters
Name Description
body *

Responses

Status: 200 - Includes ID and fields matching those sent in the request or which you would normally get from contact queries. See the getContacts.


updateList

Update information for existing Contact Lists such as From Name or From Address. This can also be used to assign custom fields to specific lists, but the custom field must exist in the platform in advance. Return contact information and other general metadata for the user.

Access control required to execute this endpoint: Marketing - List Management


/perl/api/v2/user/{username}/marketing/list/{list_id}

Parameters

Path parameters
Name Description
username*
String
Required
id*
String
List Id.
Required
Header parameters
Name Description
Cookie
Body parameters
Name Description
body *

Responses

Status: 200 - Includes ID and fields matching those sent in the request or which you would normally get from contact list queries. Ses the getLists.


updateListGroup

Update the List Group name.

Access control required to execute this endpoint: Marketing - List Management


/perl/api/v2/user/{username}/marketing/list_group/{list_group_id}

Parameters

Path parameters
Name Description
username*
String
Required
list_group_id*
String
Unique Id for this list group.
Required
Header parameters
Name Description
Cookie
Body parameters
Name Description
body

Responses

Status: 200 - None


Reports

getAccountJob

Return the details of a specific asynchronous reporting job. If the job_id is not found, a not found API error will be emitted.


/perl/api/v2/account/{accountId}/job/{job_id}

Parameters

Path parameters
Name Description
accountId*
String
Required
job_id*
Integer
Required
Header parameters
Name Description
Cookie

Responses

Status: 200 - This will return an associated array containing standard job description details.


getAccountJobs

Return a list of all asynchronous reporting jobs submitted by this account in the past 7 days.


/perl/api/v2/account/{accountId}/jobs

Parameters

Path parameters
Name Description
accountId*
String
Required
Header parameters
Name Description
Cookie

Responses

Status: 200 - This will return a list of associated arrays each containing standard job description details.


getAccountSuppressionReport

Retrieve all email suppressions at the account level (only) using a report-style call. See also [API Reporting Basics](/rest-api/reporting.html) and [report header columns in the response.](/rest-api/report-responses.html#sup).

Access control required to execute this endpoint: User Email: Suppression


/perl/api/v2/account/{accountId}/suppression_v2/

Parameters

Path parameters
Name Description
accountId*
String
Required
Header parameters
Name Description
Cookie
Query parameters
Name Description
email
String
Restrict the report to suppressions of this specific email address.
after_date
String
DATETIME. Return only matches dated after this date time. Format “YYYY-MM-DD HH:MM:SS” in GMT
before_date
String
DATETIME. Return only matches dated before this date time.
first_row
Integer
(Default value 0). All of the matches are sorted and numbered starting from 0. E.g. if you have 100,000 matches, these are rows 0 through 99,999. If you specify a first_row, then the returned matches will be those rows starting from that row. E.g. without a specification (or if you specify 0), you might get rows 0 through 49,999. In your next request you might specify first_row=50000 to get rows 50000 to 99,999.
from_date
String
DATETIME. Return only matches dated on or after this date time.
matches
Integer
(Default value 50000). You can set matches to any value from 0 to 50000. This sets the maximum number of matches that will be returned in response to your request. Note that if the response size starts to exceed 50MB, then the response can still include fewer than your “matches” number, to keep the response size reasonable. If you specify “0” here, then no matches will be returned; however, you will still get the information on the number of matches that there were. For asynchronous reports (ones where a destination is specified), the matches parameter is not limited to 50000, but it still defaults to 50000 if not specified. If you expect a larger number of rows, then you must explicitly approve the maximum size of the result set by setting matches appropriately. This helps prevent accidental queries that produce very larger result sets.
through_date
String
DATETIME. Return only matches dated before or on this date time.
destination
String
For reporting requests. Specifying a destination makes the report "asynchronous." This means that a background job will be created to run the report and upload the final CSV file to the requested destination. The API request to start the report will return immediately with a background "job number" and the filename that will be uploaded. The supported value of "destination" is currently only "sftp" for a Secure FTP upload over SSH (as opposed to ftps, which would be a Secure FTP upload over SSL). When "destination" is specified, additional destination parameters are also required. Note that for SFTP uploads, there is a 15-minute upload timeout -- uploads that take longer (e.g., due to slow SFTP servers) will be aborted. WARNING: Multiple concurrent large asynchronous report requests will impact your database performance: reports will take longer to generate and your LuxSci services will experience degraded/slower performance.
destination_directory
String
For asynchronous reporting requests. This optional parameter will be the subdirectory to change to on the SFTP server before uploading the report CSV file. Technically speaking, this will be the argument provided to the SFTP "chdir" command.
destination_hostname
String
For asynchronous reporting requests. This will be the hostname of the SFTP server to which the report CSV file should be uploaded.
destination_password
String
For asynchronous reporting requests. This will be the password to be used for the login to the SFTP server to which the report CSV file should be uploaded.
destination_username
String
For asynchronous reporting requests. This will be the username to be used for the login to the SFTP server to which the report CSV file should be uploaded.

Responses

Status: 200 - Report of suppressions


getAccountSuppressionSummaryReport

Retrieve a count of the matching email suppressions at the account level (only) using a report-style call. Dates are based on the date that the suppression was added. See also [API Reporting Basics](/rest-api/reporting.html) and [report header columns in the response](/rest-api/report-responses.html#sup_count)

Access control required to execute this endpoint: User Email: Suppression


/perl/api/v2/account/{accountId}/suppression_count/

Parameters

Path parameters
Name Description
accountId*
String
Required
Header parameters
Name Description
Cookie
Query parameters
Name Description
after_date
String
DATETIME. Return only matches dated after this date time. Format “YYYY-MM-DD HH:MM:SS” in GMT
before_date
String
DATETIME. Return only matches dated before this date time.
first_row
Integer
(Default value 0). All of the matches are sorted and numbered starting from 0. E.g. if you have 100,000 matches, these are rows 0 through 99,999. If you specify a first_row, then the returned matches will be those rows starting from that row. E.g. without a specification (or if you specify 0), you might get rows 0 through 49,999. In your next request you might specify first_row=50000 to get rows 50000 to 99,999.
from_date
String
DATETIME. Return only matches dated on or after this date time.
matches
Integer
(Default value 50000). You can set matches to any value from 0 to 50000. This sets the maximum number of matches that will be returned in response to your request. Note that if the response size starts to exceed 50MB, then the response can still include fewer than your “matches” number, to keep the response size reasonable. If you specify “0” here, then no matches will be returned; however, you will still get the information on the number of matches that there were. For asynchronous reports (ones where a destination is specified), the matches parameter is not limited to 50000, but it still defaults to 50000 if not specified. If you expect a larger number of rows, then you must explicitly approve the maximum size of the result set by setting matches appropriately. This helps prevent accidental queries that produce very larger result sets.
through_date
String
DATETIME. Return only matches dated before or on this date time.
destination
String
For reporting requests. Specifying a destination makes the report "asynchronous." This means that a background job will be created to run the report and upload the final CSV file to the requested destination. The API request to start the report will return immediately with a background "job number" and the filename that will be uploaded. The supported value of "destination" is currently only "sftp" for a Secure FTP upload over SSH (as opposed to ftps, which would be a Secure FTP upload over SSL). When "destination" is specified, additional destination parameters are also required. Note that for SFTP uploads, there is a 15-minute upload timeout -- uploads that take longer (e.g., due to slow SFTP servers) will be aborted. WARNING: Multiple concurrent large asynchronous report requests will impact your database performance: reports will take longer to generate and your LuxSci services will experience degraded/slower performance.
destination_directory
String
For asynchronous reporting requests. This optional parameter will be the subdirectory to change to on the SFTP server before uploading the report CSV file. Technically speaking, this will be the argument provided to the SFTP "chdir" command.
destination_hostname
String
For asynchronous reporting requests. This will be the hostname of the SFTP server to which the report CSV file should be uploaded.
destination_password
String
For asynchronous reporting requests. This will be the password to be used for the login to the SFTP server to which the report CSV file should be uploaded.
destination_username
String
For asynchronous reporting requests. This will be the username to be used for the login to the SFTP server to which the report CSV file should be uploaded.
filter1
String
Control when a summary report returns values (for use with automated reports). See https://luxsci.com/rest-api/reporting.html#filters
filter2
String
Control when a summary report returns values (for use with automated reports). See https://luxsci.com/rest-api/reporting.html#filters
filter3
String
Control when a summary report returns values (for use with automated reports). See https://luxsci.com/rest-api/reporting.html#filters

Responses

Status: 200 - Report the count of matching suppressions. The returned field name for this count is suppressions.


getEmailFeedBackLoopsReportAccount

This report allows to see what messages that you have sent successfully have been “marked as spam” by recipients and this information has come back to us via one of our feedback loops. See also [API Reporting Basics](/rest-api/reporting.html) and [report header columns in the response](/rest-api/report-responses.html#fbl).

Access control required to execute this endpoint: Account: View Reports


/perl/api/v2/account/{accountId}/report/email/fbl

Parameters

Path parameters
Name Description
accountId*
String
Required
Header parameters
Name Description
Cookie
Query parameters
Name Description
after_date
String
DATETIME. Return only matches dated after this date time. Format “YYYY-MM-DD HH:MM:SS” in GMT
before_date
String
DATETIME. Return only matches dated before this date time.
first_row
Integer
(Default value 0). All of the matches are sorted and numbered starting from 0. E.g. if you have 100,000 matches, these are rows 0 through 99,999. If you specify a first_row, then the returned matches will be those rows starting from that row. E.g. without a specification (or if you specify 0), you might get rows 0 through 49,999. In your next request you might specify first_row=50000 to get rows 50000 to 99,999.
from_date
String
DATETIME. Return only matches dated on or after this date time.
matches
Integer
(Default value 50000). You can set matches to any value from 0 to 50000. This sets the maximum number of matches that will be returned in response to your request. Note that if the response size starts to exceed 50MB, then the response can still include fewer than your “matches” number, to keep the response size reasonable. If you specify “0” here, then no matches will be returned; however, you will still get the information on the number of matches that there were. For asynchronous reports (ones where a destination is specified), the matches parameter is not limited to 50000, but it still defaults to 50000 if not specified. If you expect a larger number of rows, then you must explicitly approve the maximum size of the result set by setting matches appropriately. This helps prevent accidental queries that produce very larger result sets.
through_date
String
DATETIME. Return only matches dated before or on this date time.
destination
String
For reporting requests. Specifying a destination makes the report "asynchronous." This means that a background job will be created to run the report and upload the final CSV file to the requested destination. The API request to start the report will return immediately with a background "job number" and the filename that will be uploaded. The supported value of "destination" is currently only "sftp" for a Secure FTP upload over SSH (as opposed to ftps, which would be a Secure FTP upload over SSL). When "destination" is specified, additional destination parameters are also required. Note that for SFTP uploads, there is a 15-minute upload timeout -- uploads that take longer (e.g., due to slow SFTP servers) will be aborted. WARNING: Multiple concurrent large asynchronous report requests will impact your database performance: reports will take longer to generate and your LuxSci services will experience degraded/slower performance.
destination_directory
String
For asynchronous reporting requests. This optional parameter will be the subdirectory to change to on the SFTP server before uploading the report CSV file. Technically speaking, this will be the argument provided to the SFTP "chdir" command.
destination_hostname
String
For asynchronous reporting requests. This will be the hostname of the SFTP server to which the report CSV file should be uploaded.
destination_password
String
For asynchronous reporting requests. This will be the password to be used for the login to the SFTP server to which the report CSV file should be uploaded.
destination_username
String
For asynchronous reporting requests. This will be the username to be used for the login to the SFTP server to which the report CSV file should be uploaded.
from
String
Case-insensitive substring search of the message “From” email address
subject
String
Case-insensitive substring search of the message subject (in UTF-8).
to
String
Case-insensitive substring search of all recipient email addresses.
user_id
Integer
Restrict the report to the user with this specific User ID number.

Responses

Status: 200 - Report content


getEmailFeedBackLoopsSummaryReportAccount

This report allows to see how many messages have been marked as spam. The date of the compliant is used for date filters. See also [API Reporting Basics](/rest-api/reporting.html) and [report header columns in the response](/rest-api/report-responses.html#fbl_count).

Access control required to execute this endpoint: Account: View Reports


/perl/api/v2/account/{accountId}/report/email/fbl_count

Parameters

Path parameters
Name Description
accountId*
String
Required
Header parameters
Name Description
Cookie
Query parameters
Name Description
after_date
String
DATETIME. Return only matches dated after this date time. Format “YYYY-MM-DD HH:MM:SS” in GMT
before_date
String
DATETIME. Return only matches dated before this date time.
first_row
Integer
(Default value 0). All of the matches are sorted and numbered starting from 0. E.g. if you have 100,000 matches, these are rows 0 through 99,999. If you specify a first_row, then the returned matches will be those rows starting from that row. E.g. without a specification (or if you specify 0), you might get rows 0 through 49,999. In your next request you might specify first_row=50000 to get rows 50000 to 99,999.
from_date
String
DATETIME. Return only matches dated on or after this date time.
matches
Integer
(Default value 50000). You can set matches to any value from 0 to 50000. This sets the maximum number of matches that will be returned in response to your request. Note that if the response size starts to exceed 50MB, then the response can still include fewer than your “matches” number, to keep the response size reasonable. If you specify “0” here, then no matches will be returned; however, you will still get the information on the number of matches that there were. For asynchronous reports (ones where a destination is specified), the matches parameter is not limited to 50000, but it still defaults to 50000 if not specified. If you expect a larger number of rows, then you must explicitly approve the maximum size of the result set by setting matches appropriately. This helps prevent accidental queries that produce very larger result sets.
through_date
String
DATETIME. Return only matches dated before or on this date time.
destination
String
For reporting requests. Specifying a destination makes the report "asynchronous." This means that a background job will be created to run the report and upload the final CSV file to the requested destination. The API request to start the report will return immediately with a background "job number" and the filename that will be uploaded. The supported value of "destination" is currently only "sftp" for a Secure FTP upload over SSH (as opposed to ftps, which would be a Secure FTP upload over SSL). When "destination" is specified, additional destination parameters are also required. Note that for SFTP uploads, there is a 15-minute upload timeout -- uploads that take longer (e.g., due to slow SFTP servers) will be aborted. WARNING: Multiple concurrent large asynchronous report requests will impact your database performance: reports will take longer to generate and your LuxSci services will experience degraded/slower performance.
destination_directory
String
For asynchronous reporting requests. This optional parameter will be the subdirectory to change to on the SFTP server before uploading the report CSV file. Technically speaking, this will be the argument provided to the SFTP "chdir" command.
destination_hostname
String
For asynchronous reporting requests. This will be the hostname of the SFTP server to which the report CSV file should be uploaded.
destination_password
String
For asynchronous reporting requests. This will be the password to be used for the login to the SFTP server to which the report CSV file should be uploaded.
destination_username
String
For asynchronous reporting requests. This will be the username to be used for the login to the SFTP server to which the report CSV file should be uploaded.
filter1
String
Control when a summary report returns values (for use with automated reports). See https://luxsci.com/rest-api/reporting.html#filters
filter2
String
Control when a summary report returns values (for use with automated reports). See https://luxsci.com/rest-api/reporting.html#filters
filter3
String
Control when a summary report returns values (for use with automated reports). See https://luxsci.com/rest-api/reporting.html#filters
from
String
String Case-insensitive substring search of the message “From” email address
subject
String
String Case-insensitive substring search of the message subject (in UTF-8).
to
String
String. Case-insensitive substring search of all recipient email addresses.
user_id
Integer
Integer Restrict the report to the user with this specific User ID number.

Responses

Status: 200 - Report content. The summary header field is named compliants.


getEmailSMTPClickReportAccount

This report allows you to query on the “URL click” events (or lack thereof) for email messages sent via SMTP that have email click tracking enabled. Using this command, it is possible to get a report of all individual clicks or to get reports about messages that have not yet been clicked on or for which click tracking was not enabled. See the query parameters for more detail. *Note: if you are using LuxSci Secure Marketing v2 to send your email messages, then normal LuxSci click and open reporting is disabled (and you will not see click and open data in this report). The LuxSci Secure Marketing v2 platform his its own click and open tracking and reporting system and you should look in that interface for reports.* See also [API Reporting Basics](/rest-api/reporting.html) and [report header columns in the response](/rest-api/report-responses.html#click). Dates, for the purposes of narrowing results, refer to the date the message was sent. This corresponds to the “date_sent” output field. However, if you set the “click_date” input parameter to true, then the “click_date” field will be used for date selections.

Access control required to execute this endpoint: Account: View Reports


/perl/api/v2/account/{accountId}/report/email/smtp/clicks

Parameters

Path parameters
Name Description
accountId*
String
Required
Header parameters
Name Description
Cookie
Query parameters
Name Description
after_date
String
DATETIME. Return only matches dated after this date time. Format “YYYY-MM-DD HH:MM:SS” in GMT
before_date
String
DATETIME. Return only matches dated before this date time.
first_row
Integer
(Default value 0). All of the matches are sorted and numbered starting from 0. E.g. if you have 100,000 matches, these are rows 0 through 99,999. If you specify a first_row, then the returned matches will be those rows starting from that row. E.g. without a specification (or if you specify 0), you might get rows 0 through 49,999. In your next request you might specify first_row=50000 to get rows 50000 to 99,999.
from_date
String
DATETIME. Return only matches dated on or after this date time.
matches
Integer
(Default value 50000). You can set matches to any value from 0 to 50000. This sets the maximum number of matches that will be returned in response to your request. Note that if the response size starts to exceed 50MB, then the response can still include fewer than your “matches” number, to keep the response size reasonable. If you specify “0” here, then no matches will be returned; however, you will still get the information on the number of matches that there were. For asynchronous reports (ones where a destination is specified), the matches parameter is not limited to 50000, but it still defaults to 50000 if not specified. If you expect a larger number of rows, then you must explicitly approve the maximum size of the result set by setting matches appropriately. This helps prevent accidental queries that produce very larger result sets.
through_date
String
DATETIME. Return only matches dated before or on this date time.
destination
String
For reporting requests. Specifying a destination makes the report "asynchronous." This means that a background job will be created to run the report and upload the final CSV file to the requested destination. The API request to start the report will return immediately with a background "job number" and the filename that will be uploaded. The supported value of "destination" is currently only "sftp" for a Secure FTP upload over SSH (as opposed to ftps, which would be a Secure FTP upload over SSL). When "destination" is specified, additional destination parameters are also required. Note that for SFTP uploads, there is a 15-minute upload timeout -- uploads that take longer (e.g., due to slow SFTP servers) will be aborted. WARNING: Multiple concurrent large asynchronous report requests will impact your database performance: reports will take longer to generate and your LuxSci services will experience degraded/slower performance.
destination_directory
String
For asynchronous reporting requests. This optional parameter will be the subdirectory to change to on the SFTP server before uploading the report CSV file. Technically speaking, this will be the argument provided to the SFTP "chdir" command.
destination_hostname
String
For asynchronous reporting requests. This will be the hostname of the SFTP server to which the report CSV file should be uploaded.
destination_password
String
For asynchronous reporting requests. This will be the password to be used for the login to the SFTP server to which the report CSV file should be uploaded.
destination_username
String
For asynchronous reporting requests. This will be the username to be used for the login to the SFTP server to which the report CSV file should be uploaded.
from
String
Case-insensitive substring search of the message “From” email address
clicked
Integer
If specified, the results are restricted as follows:
clicked < 0 – select messages where click tracking was not enabled.
clicked = 0 – select messages where click tracking was enabled, but where no URLs have yet been clicked by the recipient.
clicked > 0 – select messages where one or more URLs have been clicked by the recipient. When “clicked” is positive, you will get one row back for each click; so,you can get multiple rows per message.

If a value for “clicked” is not specified, a value of “1” will be assumed.
click_date
String
If true, the ”click_date” field will be used for all date selections. If false or not specified, the sent date (“date_sent”) will be used.
header1
String
Case-insensitive name of the custom email header field to match against in the “header 1” column. I.e., if you were matching against “X-My-Header” and saving this in header 1, you would enter “X-My-Header” as the value here.

NOTE: Data is only stored in the customer header capturing fields/columns if you have explicitly enabled this feature in the “Account Administration > Email” area of the LuxSci user interface.
header1_operator
String
If this is present and one of the following 4 values, then the query will only return messages that included “header1” when “header1” was being tracked, and which also satisfy the follow the criteria:
  • is --- The value of the email header named “header1” in the send email must have been exactly the same as header1_value
  • not – The value of the email header named “header1” in the send email must not be exactly the same as header1_value
  • like – The value of the email header named “header1” in the send email must contain (case insensitive) the value in header1_value
  • notlike – The value of the email header named “header1” in the send email must not contain (case insensitive) the value in header1_value
I.e., if you configured your account to capture the value of the header “X-My-Header” and saving this in “header column 1” and an email was sent with the header “X-My-Header: gh6577hh-abc”. This would have been stored in the database. You could then find this message by passing to this API function:
  • header1 = “X-My-Header”
  • header1_operator = “is”
  • header1_value = “gh6577hh-abc”
Or by passing:
  • header1 = “X-My-Header”,/li>
  • header1_operator = “like”
  • header1_value = “abc”
header1_value
String
Text used with “header1_operator” for matching the value of the email header specified in the “header1” parameter in the original sent message.
header2
String
Like “header1” but applies to searching the header 2 column.
header2_operator
String
Like “header1_operator” but applies to searching the header 2 column.
header2_value
String
Like “header1_value” but applies to searching the header 2 column.
header3
String
Like “header1” but applies to searching the header 3 column.
header3_operator
String
Like “header1_operator” but applies to searching the header 3 column.
header3_value
String
Like “header1_value” but applies to searching the header 2 column.
opened
Integer
If specified, the results are restricted as follows:
opened < 0 – select messages where open tracking was not enabled.
opened = 0 – select messages where open tracking was enabled, but which have not yet been opened.
opened > 0 – select messages where open tracking was enabled, and which have been opened at least once.
sendmail_id
String
String. Return only the messages with the specified sendmail_id
sendmail_ids
String
Comma-delimited list of up to 100 sendmail ids. Returns any matching messages.
status
String
Values:
delivered – Accepted by the recipient’s email servers and presumed delivered. If bounce processing is enabled, then this status could change later to ba_soft_fail or ba_hard_fail.
perm_fail – Messages that have permanently failed to be delivered to the recipient’s servers. If bounce processing is on, this status could change shortly to ba_soft_fail, depending on the nature of the failure message.
lost – Messages where the tracking was lost and it is unclear if it was delivered or lost from the queue.
queued – Message is in the email server queue still waiting to be delivered to the recipient.
not_queued -- all statuses except "queued".
ba_soft_fail – Soft failure bounces received (when talking to the recipient’s servers or after successful delivery to the recipient’s servers).
ba_hard_fail – Hard failure bounces received after successful delivery to the recipient’s servers,
any_hard_fail – Results for ba_hard_fail OR perm_fail. I.e., all hard/permanent failures.
subject
String
Case-insensitive substring search of the message subject (in UTF8).
template_id
Integer
Optional template ID to select results only for those messages sent using the specified template. A value of 0 selects all.
to
String
Case-insensitive substring search of all recipient email addresses.
tracked_headers
String
If true and this report is for messages sent vis SMTP, then the results will include the six additional fields (header1, header2, header3, header1_value, header2_value, header3_value) which are used to track custom email message header data.
user_id
String
Restrict the report to the user with this specific User ID number
url
String
Substring match on the URL clicked.

Responses

Status: 200 - Report content


getEmailSMTPClickSummaryReportAccount

This report allows you to query the number of clicks on tracked links during the specified date period. *Note that if you are using LuxSci Secure Marketing v2 to send your email messages, then normal LuxSci click and open reporting is disabled (and you will not see click and open data in this report). The LuxSci Secure Marketing v2 platform his its own click and open tracking and reporting system and you should look in that interface for reports.* See also [API Reporting Basics](/rest-api/reporting.html) and [report header columns in the response](/rest-api/report-responses.html#clicks_count). Dates, for the purposes of narrowing results, refer to the date the link was clicked on.

Access control required to execute this endpoint: Account: View Reports


/perl/api/v2/account/{accountId}/report/email/smtp/clicks_count

Parameters

Path parameters
Name Description
accountId*
String
Required
Header parameters
Name Description
Cookie
Query parameters
Name Description
after_date
String
DATETIME. Return only matches dated after this date time. Format “YYYY-MM-DD HH:MM:SS” in GMT
before_date
String
DATETIME. Return only matches dated before this date time.
first_row
Integer
(Default value 0). All of the matches are sorted and numbered starting from 0. E.g. if you have 100,000 matches, these are rows 0 through 99,999. If you specify a first_row, then the returned matches will be those rows starting from that row. E.g. without a specification (or if you specify 0), you might get rows 0 through 49,999. In your next request you might specify first_row=50000 to get rows 50000 to 99,999.
from_date
String
DATETIME. Return only matches dated on or after this date time.
matches
Integer
(Default value 50000). You can set matches to any value from 0 to 50000. This sets the maximum number of matches that will be returned in response to your request. Note that if the response size starts to exceed 50MB, then the response can still include fewer than your “matches” number, to keep the response size reasonable. If you specify “0” here, then no matches will be returned; however, you will still get the information on the number of matches that there were. For asynchronous reports (ones where a destination is specified), the matches parameter is not limited to 50000, but it still defaults to 50000 if not specified. If you expect a larger number of rows, then you must explicitly approve the maximum size of the result set by setting matches appropriately. This helps prevent accidental queries that produce very larger result sets.
through_date
String
DATETIME. Return only matches dated before or on this date time.
destination
String
For reporting requests. Specifying a destination makes the report "asynchronous." This means that a background job will be created to run the report and upload the final CSV file to the requested destination. The API request to start the report will return immediately with a background "job number" and the filename that will be uploaded. The supported value of "destination" is currently only "sftp" for a Secure FTP upload over SSH (as opposed to ftps, which would be a Secure FTP upload over SSL). When "destination" is specified, additional destination parameters are also required. Note that for SFTP uploads, there is a 15-minute upload timeout -- uploads that take longer (e.g., due to slow SFTP servers) will be aborted. WARNING: Multiple concurrent large asynchronous report requests will impact your database performance: reports will take longer to generate and your LuxSci services will experience degraded/slower performance.
destination_directory
String
For asynchronous reporting requests. This optional parameter will be the subdirectory to change to on the SFTP server before uploading the report CSV file. Technically speaking, this will be the argument provided to the SFTP "chdir" command.
destination_hostname
String
For asynchronous reporting requests. This will be the hostname of the SFTP server to which the report CSV file should be uploaded.
destination_password
String
For asynchronous reporting requests. This will be the password to be used for the login to the SFTP server to which the report CSV file should be uploaded.
destination_username
String
For asynchronous reporting requests. This will be the username to be used for the login to the SFTP server to which the report CSV file should be uploaded.
filter1
String
Control when a summary report returns values (for use with automated reports). See https://luxsci.com/rest-api/reporting.html#filters
filter2
String
Control when a summary report returns values (for use with automated reports). See https://luxsci.com/rest-api/reporting.html#filters
filter3
String
Control when a summary report returns values (for use with automated reports). See https://luxsci.com/rest-api/reporting.html#filters
from
String
Case-insensitive substring search of the message “From” email address
header1
String
Case-insensitive name of the custom email header field to match against in the “header 1” column. I.e., if you were matching against “X-My-Header” and saving this in header 1, you would enter “X-My-Header” as the value here.

NOTE: Data is only stored in the customer header capturing fields/columns if you have explicitly enabled this feature in the “Account Administration > Email” area of the LuxSci user interface.
header1_operator
String
If this is present and one of the following 4 values, then the query will only return messages that included “header1” when “header1” was being tracked, and which also satisfy the follow the criteria:
  • is --- The value of the email header named “header1” in the send email must have been exactly the same as header1_value
  • not – The value of the email header named “header1” in the send email must not be exactly the same as header1_value
  • like – The value of the email header named “header1” in the send email must contain (case insensitive) the value in header1_value
  • notlike – The value of the email header named “header1” in the send email must not contain (case insensitive) the value in header1_value
I.e., if you configured your account to capture the value of the header “X-My-Header” and saving this in “header column 1” and an email was sent with the header “X-My-Header: gh6577hh-abc”. This would have been stored in the database. You could then find this message by passing to this API function:
  • header1 = “X-My-Header”
  • header1_operator = “is”
  • header1_value = “gh6577hh-abc”
Or by passing:
  • header1 = “X-My-Header”,/li>
  • header1_operator = “like”
  • header1_value = “abc”
header1_value
String
Text used with “header1_operator” for matching the value of the email header specified in the “header1” parameter in the original sent message.
header2
String
Like “header1” but applies to searching the header 2 column.
header2_operator
String
Like “header1_operator” but applies to searching the header 2 column.
header2_value
String
Like “header1_value” but applies to searching the header 2 column.
header3
String
Like “header1” but applies to searching the header 3 column.
header3_operator
String
Like “header1_operator” but applies to searching the header 3 column.
header3_value
String
Like “header1_value” but applies to searching the header 2 column.
subject
String
Case-insensitive substring search of the message subject (in UTF8).
tracked_headers
String
If true and this report is for messages sent vis SMTP, then the results will include the six additional fields (header1, header2, header3, header1_value, header2_value, header3_value) which are used to track custom email message header data.
template_id
Integer
Optional template ID to select results only for those messages sent using the specified template. A value of 0 selects all.
user_id
String
Restrict the report to the user with this specific User ID number
url
String
Substring match on the URL clicked.

Responses

Status: 200 - Report content


getEmailSMTPDeliveryStatusReportAccount

This report allows you to see how each SMTP message was sent to each recipient and what the delivery status is for each of these recipients. Note that delivery status changes over time as messages progress to the recipient’s servers and as bounce messages are sent back and processed. As the delivery status changes, the “last_update” date is also updated. See also [API Reporting Basics](/rest-api/reporting.html) and [report header columns in the response](/rest-api/report-responses.html#delivery). Dates, for the purposes of narrowing results, refer to the *date the row was last updated*. This corresponds to the last_update output field. This can be changed to the date the message was sent using the "sent_date" parameter or the date of the last delivery status update using the "delivery_date" parameter.

Access control required to execute this endpoint: Account: View Reports


/perl/api/v2/account/{accountId}/report/email/smtp/delivery

Parameters

Path parameters
Name Description
accountId*
String
Required
Header parameters
Name Description
Cookie
Query parameters
Name Description
after_date
String
DATETIME. Return only matches dated after this date time. Format “YYYY-MM-DD HH:MM:SS” in GMT
before_date
String
DATETIME. Return only matches dated before this date time.
first_row
Integer
(Default value 0). All of the matches are sorted and numbered starting from 0. E.g. if you have 100,000 matches, these are rows 0 through 99,999. If you specify a first_row, then the returned matches will be those rows starting from that row. E.g. without a specification (or if you specify 0), you might get rows 0 through 49,999. In your next request you might specify first_row=50000 to get rows 50000 to 99,999.
from_date
String
DATETIME. Return only matches dated on or after this date time.
matches
Integer
(Default value 50000). You can set matches to any value from 0 to 50000. This sets the maximum number of matches that will be returned in response to your request. Note that if the response size starts to exceed 50MB, then the response can still include fewer than your “matches” number, to keep the response size reasonable. If you specify “0” here, then no matches will be returned; however, you will still get the information on the number of matches that there were. For asynchronous reports (ones where a destination is specified), the matches parameter is not limited to 50000, but it still defaults to 50000 if not specified. If you expect a larger number of rows, then you must explicitly approve the maximum size of the result set by setting matches appropriately. This helps prevent accidental queries that produce very larger result sets.
through_date
String
DATETIME. Return only matches dated before or on this date time.
destination
String
For reporting requests. Specifying a destination makes the report "asynchronous." This means that a background job will be created to run the report and upload the final CSV file to the requested destination. The API request to start the report will return immediately with a background "job number" and the filename that will be uploaded. The supported value of "destination" is currently only "sftp" for a Secure FTP upload over SSH (as opposed to ftps, which would be a Secure FTP upload over SSL). When "destination" is specified, additional destination parameters are also required. Note that for SFTP uploads, there is a 15-minute upload timeout -- uploads that take longer (e.g., due to slow SFTP servers) will be aborted. WARNING: Multiple concurrent large asynchronous report requests will impact your database performance: reports will take longer to generate and your LuxSci services will experience degraded/slower performance.
destination_directory
String
For asynchronous reporting requests. This optional parameter will be the subdirectory to change to on the SFTP server before uploading the report CSV file. Technically speaking, this will be the argument provided to the SFTP "chdir" command.
destination_hostname
String
For asynchronous reporting requests. This will be the hostname of the SFTP server to which the report CSV file should be uploaded.
destination_password
String
For asynchronous reporting requests. This will be the password to be used for the login to the SFTP server to which the report CSV file should be uploaded.
destination_username
String
For asynchronous reporting requests. This will be the username to be used for the login to the SFTP server to which the report CSV file should be uploaded.
clicked
Integer
Integer. If specified, the results are restricted as follows:
clicked < 0 – select messages where URL click tracking was not enabled.
clicked = 0 – select messages where URL click tracking was enabled, but where there have as yet been no clicks on any clinks in the messages.
clicked > 0 – select messages where URL click tracking was enabled and where there have been N or more clicks on links in the same message to the same recipient. N, in this case, is the number that you have specified as the value of the “clicked” parameter. I.e., using a value of “1” matches all messages that have had a link clicked on.
from
String
String. Case-insensitive substring search of the message “From” email Address
ip
String
String. Case-insensitive substring search of the sender IP address (for SMTP reports only).
header1
String
Case-insensitive name of the custom email header field to match against in the “header 1” column. I.e., if you were matching against “X-My-Header” and saving this in header 1, you would enter “X-My-Header” as the value here.

NOTE: Data is only stored in the customer header capturing fields/columns if you have explicitly enabled this feature in the “Account Administration > Email” area of the LuxSci user interface.
header1_operator
String
If this is present and one of the following 4 values, then the query will only return messages that included “header1” when “header1” was being tracked, and which also satisfy the follow the criteria:
  • is --- The value of the email header named “header1” in the send email must have been exactly the same as header1_value
  • not – The value of the email header named “header1” in the send email must not be exactly the same as header1_value
  • like – The value of the email header named “header1” in the send email must contain (case insensitive) the value in header1_value
  • notlike – The value of the email header named “header1” in the send email must not contain (case insensitive) the value in header1_value
I.e., if you configured your account to capture the value of the header “X-My-Header” and saving this in “header column 1” and an email was sent with the header “X-My-Header: gh6577hh-abc”. This would have been stored in the database. You could then find this message by passing to this API function:
  • header1 = “X-My-Header”
  • header1_operator = “is”
  • header1_value = “gh6577hh-abc”
Or by passing:
  • header1 = “X-My-Header”,/li>
  • header1_operator = “like”
  • header1_value = “abc”
header1_value
String
Text used with “header1_operator” for matching the value of the email header specified in the “header1” parameter in the original sent message.
header2
String
Like “header1” but applies to searching the header 2 column.
header2_operator
String
Like “header1_operator” but applies to searching the header 2 column.
header2_value
String
Like “header1_value” but applies to searching the header 2 column.
header3
String
Like “header1” but applies to searching the header 3 column.
header3_operator
String
Like “header1_operator” but applies to searching the header 3 column.
header3_value
String
Like “header1_value” but applies to searching the header 2 column.
opened
Integer
Integer. If specified, the results are restricted as follows:
opened < 0 – select messages where open tracking was not enabled.
opened = 0 – select messages where open tracking was enabled, but which have not yet been opened.
opened > 0 – select messages where open tracking was enabled and which have been opened at least N times. N, in this case, is the number that you have specified as the value of the “opened” parameter. I.e., using a value of “1” matches all messages that have been opened.
secureline
String
Enum. Value:
u - message to this recipient did not use SecureLine (or Opt Out was used)
e - message did use SecureLine
-2 - SecureLine was not used due to Opt Out being selected
-1 - SecureLine usage not recorded for some reason
1 - SecureLine:PGP was used
2 - SecureLine:S/MIME was used
3 - SecureLine:Escrow was used
4 - SecureLine:TLS was used
sendmail_id
String
String. Return only the messages with the specified sendmail_id
sent_date
Integer
If set to true (i.e., 1), the email message sent date will be used for date/time selections, instead of the date of the last update of the row.
state
String
Optionally, match only messages with specific delivery states. This is a comma-delimited list of one or more states to match. The possible states include:
delivered - Successful delivery.
perm_fail - Message immediately rejected by recipient servers.
ba_hard_fail - Post-delivery hard bounce.
ba_soft_fail - Post-delivery soft bounce.
temp_fail - Message still queued after 1+ temporary delivery failures.
queued - Message queued -- includes the "temp_fail" state.
lost - Message delivery status unknown.
any_hard_fail - "perm_fail" or "ba_hard_fail".
failed - "perm_fail" or "ba_hard_fail" or "ba_soft_fail".
not_queued - "delivered" or "lost" or any of the "failed" states.
state_detail
String
Optionally, match only messages where the "state_detail" delivery status description contains the specified text (case insensitive).
delivery_date
Integer
If set to true (i.e., 1), the email message last delivery status updated date will be used for date/time selections, instead of the date of the last update of the row.
sendmail_ids
String
Comma-delimited list of up to 100 sendmail ids. Returns any matching messages.
spam
Integer
Enum. Value:
0 – Message was not marked as spam by a recipient and returned in a Feed Back Loop.
1 – Message was marked as spam by a recipient and returned in a Feed Back Loop
unsubscribed
Integer
Enum. Value:
0 – Recipient did not unsubscribe based on this email message.
1 – Recipeient did unsubscribe based on this email message.
smtp_code
String
String. 1-3 characters. Substring match to the beginning of the smtp_code field. E.g., 5 matches all codes starting with 5.
tls
Integer
Enum. Value:
0 – TLS was NOT used in the successful delivery of this message to the recipient server
1 – TLS was used in the successful delivery of this message to the recipient server
tracked_headers
String
If true and this report is for messages sent vis SMTP, then the results will include the six additional fields (header1, header2, header3, header1_value, header2_value, header3_value) which are used to track custom email message header data.
template_id
Integer
Optional template ID to select results only for those messages sent using the specified template. A value of 0 selects all.
to
String
Case-insensitive substring search of all recipient email addresses.
user_id
Integer
Integer. Restrict the report to the user with this specific User ID number

Responses

Status: 200 - Report content


getEmailSMTPDeliveryStatusSummaryReportAccount

This report allows you to retrieve a summary of the delivery status (and other statistics) across all messages in a given time range. See also [API Reporting Basics](/rest-api/reporting.html) and [report header columns in the response](/rest-api/report-responses.html#delivery_count). Dates, for the purposes of narrowing results, refer to the *date the message delivery status was last updated*. This can be changed to the date the message was sent using the "sent_date" parameter.

Access control required to execute this endpoint: Account: View Reports


/perl/api/v2/account/{accountId}/report/email/smtp/delivery_count

Parameters

Path parameters
Name Description
accountId*
String
Required
Header parameters
Name Description
Cookie
Query parameters
Name Description
after_date
String
DATETIME. Return only matches dated after this date time. Format “YYYY-MM-DD HH:MM:SS” in GMT
before_date
String
DATETIME. Return only matches dated before this date time.
first_row
Integer
(Default value 0). All of the matches are sorted and numbered starting from 0. E.g. if you have 100,000 matches, these are rows 0 through 99,999. If you specify a first_row, then the returned matches will be those rows starting from that row. E.g. without a specification (or if you specify 0), you might get rows 0 through 49,999. In your next request you might specify first_row=50000 to get rows 50000 to 99,999.
from_date
String
DATETIME. Return only matches dated on or after this date time.
matches
Integer
(Default value 50000). You can set matches to any value from 0 to 50000. This sets the maximum number of matches that will be returned in response to your request. Note that if the response size starts to exceed 50MB, then the response can still include fewer than your “matches” number, to keep the response size reasonable. If you specify “0” here, then no matches will be returned; however, you will still get the information on the number of matches that there were. For asynchronous reports (ones where a destination is specified), the matches parameter is not limited to 50000, but it still defaults to 50000 if not specified. If you expect a larger number of rows, then you must explicitly approve the maximum size of the result set by setting matches appropriately. This helps prevent accidental queries that produce very larger result sets.
through_date
String
DATETIME. Return only matches dated before or on this date time.
destination
String
For reporting requests. Specifying a destination makes the report "asynchronous." This means that a background job will be created to run the report and upload the final CSV file to the requested destination. The API request to start the report will return immediately with a background "job number" and the filename that will be uploaded. The supported value of "destination" is currently only "sftp" for a Secure FTP upload over SSH (as opposed to ftps, which would be a Secure FTP upload over SSL). When "destination" is specified, additional destination parameters are also required. Note that for SFTP uploads, there is a 15-minute upload timeout -- uploads that take longer (e.g., due to slow SFTP servers) will be aborted. WARNING: Multiple concurrent large asynchronous report requests will impact your database performance: reports will take longer to generate and your LuxSci services will experience degraded/slower performance.
destination_directory
String
For asynchronous reporting requests. This optional parameter will be the subdirectory to change to on the SFTP server before uploading the report CSV file. Technically speaking, this will be the argument provided to the SFTP "chdir" command.
destination_hostname
String
For asynchronous reporting requests. This will be the hostname of the SFTP server to which the report CSV file should be uploaded.
destination_password
String
For asynchronous reporting requests. This will be the password to be used for the login to the SFTP server to which the report CSV file should be uploaded.
destination_username
String
For asynchronous reporting requests. This will be the username to be used for the login to the SFTP server to which the report CSV file should be uploaded.
filter1
String
Control when a summary report returns values (for use with automated reports). See https://luxsci.com/rest-api/reporting.html#filters
filter2
String
Control when a summary report returns values (for use with automated reports). See https://luxsci.com/rest-api/reporting.html#filters
filter3
String
Control when a summary report returns values (for use with automated reports). See https://luxsci.com/rest-api/reporting.html#filters
clicked
Integer
Integer. If specified, the results are restricted as follows:
clicked < 0 – select messages where URL click tracking was not enabled.
clicked = 0 – select messages where URL click tracking was enabled, but where there have as yet been no clicks on any clinks in the messages.
clicked > 0 – select messages where URL click tracking was enabled and where there have been N or more clicks on links in the same message to the same recipient. N, in this case, is the number that you have specified as the value of the “clicked” parameter. I.e., using a value of “1” matches all messages that have had a link clicked on.
from
String
String. Case-insensitive substring search of the message “From” email Address
ip
String
String. Case-insensitive substring search of the sender IP address (for SMTP reports only).
header1
String
Case-insensitive name of the custom email header field to match against in the “header 1” column. I.e., if you were matching against “X-My-Header” and saving this in header 1, you would enter “X-My-Header” as the value here.

NOTE: Data is only stored in the customer header capturing fields/columns if you have explicitly enabled this feature in the “Account Administration > Email” area of the LuxSci user interface.
header1_operator
String
If this is present and one of the following 4 values, then the query will only return messages that included “header1” when “header1” was being tracked, and which also satisfy the follow the criteria:
  • is --- The value of the email header named “header1” in the send email must have been exactly the same as header1_value
  • not – The value of the email header named “header1” in the send email must not be exactly the same as header1_value
  • like – The value of the email header named “header1” in the send email must contain (case insensitive) the value in header1_value
  • notlike – The value of the email header named “header1” in the send email must not contain (case insensitive) the value in header1_value
I.e., if you configured your account to capture the value of the header “X-My-Header” and saving this in “header column 1” and an email was sent with the header “X-My-Header: gh6577hh-abc”. This would have been stored in the database. You could then find this message by passing to this API function:
  • header1 = “X-My-Header”
  • header1_operator = “is”
  • header1_value = “gh6577hh-abc”
Or by passing:
  • header1 = “X-My-Header”,/li>
  • header1_operator = “like”
  • header1_value = “abc”
header1_value
String
Text used with “header1_operator” for matching the value of the email header specified in the “header1” parameter in the original sent message.
header2
String
Like “header1” but applies to searching the header 2 column.
header2_operator
String
Like “header1_operator” but applies to searching the header 2 column.
header2_value
String
Like “header1_value” but applies to searching the header 2 column.
header3
String
Like “header1” but applies to searching the header 3 column.
header3_operator
String
Like “header1_operator” but applies to searching the header 3 column.
header3_value
String
Like “header1_value” but applies to searching the header 2 column.
opened
Integer
Integer. If specified, the results are restricted as follows:
opened < 0 – select messages where open tracking was not enabled.
opened = 0 – select messages where open tracking was enabled, but which have not yet been opened.
opened > 0 – select messages where open tracking was enabled and which have been opened at least N times. N, in this case, is the number that you have specified as the value of the “opened” parameter. I.e., using a value of “1” matches all messages that have been opened.
secureline
String
Enum. Value:
u – Message to this recipient did not use SecureLine (or Opt Out was used)
e – Message did use SecureLine
-2 – SecureLine was not used due to Opt Out being selected
-1 – SecureLine usage not recorded for some reason
1 – SecureLine:PGP was used
2 – SecureLine:S/MIME was used
3 – SecureLine:Escrow was used
4 – SecureLine:TLS was used
sent_date
Integer
If set to true (i.e., 1), the email message sent date will be used for date/time selections, instead of the date of the last update of the delivery status.
queue_age_sec
Integer
If provided, then the "queued" and "pct_queued" results will reflect only those messages that have been not delivered for at least this number of seconds. I.e., use this to eliminate very recently sent messages from your analysis or how mange messages were queued and not yet delivered.
unsubscribed
Integer
Enum. Value: 0 – The recipient did not unsubscribe based on this email message. 1 – The recipient did unsubscribe based on this email message.
tls
Integer
Enum. Value:
0 – TLS was NOT used in the successful delivery of this message to the recipient server
1 – TLS was used in the successful delivery of this message to the recipient server.
tracked_headers
String
If true and this report is for messages sent vis SMTP, then the results will include the six additional fields (header1, header2, header3, header1_value, header2_value, header3_value) which are used to track custom email message header data.
template_id
Integer
Optional template ID to select results only for those messages sent using the specified template. A value of 0 selects all.
to
String
Case-insensitive substring search of all recipient email addresses.
user_id
Integer
Integer. Restrict the report to the user with this specific User ID number

Responses

Status: 200 -


getEmailSMTPOpenReportAccount

This report allows you to query on the “opened” events (or lack thereof) for email messages sent via SMTP that have email open tracking enabled. Using this command, it is possible to get a report of all individual opens for messages or to get reports about messages that have not yet been opened or for which open tracking was not enabled. See the query parameters for more detail. *Note: if you are using LuxSci Secure Marketing v2 to send your email messages, then normal LuxSci click and open reporting is disabled (and you will not see click and open data in this report). The LuxSci Secure Marketing v2 platform his its own click and open tracking and reporting system and you should look in that interface for reports.* See also [API Reporting Basics](/rest-api/reporting.html) and [report header columns in the response](/rest-api/report-responses.html#open). Dates, for the purposes of narrowing results, refer to the date the message was sent. This corresponds to the “date_sent” output field. However, if you set the “open_date” input parameter to true, then the “open_date” field will be used for date selections.

Access control required to execute this endpoint: Account: View Reports


/perl/api/v2/account/{accountId}/report/email/smtp/opens

Parameters

Path parameters
Name Description
accountId*
String
Required
Header parameters
Name Description
Cookie
Query parameters
Name Description
after_date
String
DATETIME. Return only matches dated after this date time. Format “YYYY-MM-DD HH:MM:SS” in GMT
before_date
String
DATETIME. Return only matches dated before this date time.
first_row
Integer
(Default value 0). All of the matches are sorted and numbered starting from 0. E.g. if you have 100,000 matches, these are rows 0 through 99,999. If you specify a first_row, then the returned matches will be those rows starting from that row. E.g. without a specification (or if you specify 0), you might get rows 0 through 49,999. In your next request you might specify first_row=50000 to get rows 50000 to 99,999.
from_date
String
DATETIME. Return only matches dated on or after this date time.
matches
Integer
(Default value 50000). You can set matches to any value from 0 to 50000. This sets the maximum number of matches that will be returned in response to your request. Note that if the response size starts to exceed 50MB, then the response can still include fewer than your “matches” number, to keep the response size reasonable. If you specify “0” here, then no matches will be returned; however, you will still get the information on the number of matches that there were. For asynchronous reports (ones where a destination is specified), the matches parameter is not limited to 50000, but it still defaults to 50000 if not specified. If you expect a larger number of rows, then you must explicitly approve the maximum size of the result set by setting matches appropriately. This helps prevent accidental queries that produce very larger result sets.
through_date
String
DATETIME. Return only matches dated before or on this date time.
destination
String
For reporting requests. Specifying a destination makes the report "asynchronous." This means that a background job will be created to run the report and upload the final CSV file to the requested destination. The API request to start the report will return immediately with a background "job number" and the filename that will be uploaded. The supported value of "destination" is currently only "sftp" for a Secure FTP upload over SSH (as opposed to ftps, which would be a Secure FTP upload over SSL). When "destination" is specified, additional destination parameters are also required. Note that for SFTP uploads, there is a 15-minute upload timeout -- uploads that take longer (e.g., due to slow SFTP servers) will be aborted. WARNING: Multiple concurrent large asynchronous report requests will impact your database performance: reports will take longer to generate and your LuxSci services will experience degraded/slower performance.
destination_directory
String
For asynchronous reporting requests. This optional parameter will be the subdirectory to change to on the SFTP server before uploading the report CSV file. Technically speaking, this will be the argument provided to the SFTP "chdir" command.
destination_hostname
String
For asynchronous reporting requests. This will be the hostname of the SFTP server to which the report CSV file should be uploaded.
destination_password
String
For asynchronous reporting requests. This will be the password to be used for the login to the SFTP server to which the report CSV file should be uploaded.
destination_username
String
For asynchronous reporting requests. This will be the username to be used for the login to the SFTP server to which the report CSV file should be uploaded.
from
String
Case-insensitive substring search of the message “From” email address
header1
String
Case-insensitive name of the custom email header field to match against in the “header 1” column. I.e., if you were matching against “X-My-Header” and saving this in header 1, you would enter “X-My-Header” as the value here.

NOTE: Data is only stored in the customer header capturing fields/columns if you have explicitly enabled this feature in the “Account Administration > Email” area of the LuxSci user interface.
header1_operator
String
If this is present and one of the following 4 values, then the query will only return messages that included “header1” when “header1” was being tracked, and which also satisfy the follow the criteria:
  • is --- The value of the email header named “header1” in the send email must have been exactly the same as header1_value
  • not – The value of the email header named “header1” in the send email must not be exactly the same as header1_value
  • like – The value of the email header named “header1” in the send email must contain (case insensitive) the value in header1_value
  • notlike – The value of the email header named “header1” in the send email must not contain (case insensitive) the value in header1_value
I.e., if you configured your account to capture the value of the header “X-My-Header” and saving this in “header column 1” and an email was sent with the header “X-My-Header: gh6577hh-abc”. This would have been stored in the database. You could then find this message by passing to this API function:
  • header1 = “X-My-Header”
  • header1_operator = “is”
  • header1_value = “gh6577hh-abc”
Or by passing:
  • header1 = “X-My-Header”,/li>
  • header1_operator = “like”
  • header1_value = “abc”
header1_value
String
Text used with “header1_operator” for matching the value of the email header specified in the “header1” parameter in the original sent message.
header2
String
Like “header1” but applies to searching the header 2 column.
header2_operator
String
Like “header1_operator” but applies to searching the header 2 column.
header2_value
String
Like “header1_value” but applies to searching the header 2 column.
header3
String
Like “header1” but applies to searching the header 3 column.
header3_operator
String
Like “header1_operator” but applies to searching the header 3 column.
header3_value
String
Like “header1_value” but applies to searching the header 2 column.
opened
Integer
If specified, the results are restricted as follows:
opened < 0 – select messages where open tracking was not enabled.
opened = 0 – select messages where open tracking was enabled, but which have not yet been opened.
opened > 0 – select messages where open tracking was enabled and which have been opened at least once. When opened is positive, you will get one row back for each open; so, you can get multiple rows per message.

If you do not specify a value for “opened”, a value of “1” will be assumed.
open_date
Boolean
If true, the ”open_date” field will be used for all date selections. If false or not specified, the sent date (“date_sent”) will be used.
sendmail_id
String
Return only the messages with the specified sendmail_id.
sendmail_ids
String
Comma-delimited list of up to 100 sendmail ids. Returns any matching messages.
status
String
Values:
delivered – Accepted by the recipient’s email servers and presumed delivered. If bounce processing is enabled, then this status could change later to ba_soft_fail or ba_hard_fail.
perm_fail – Messages that have permanently failed to be delivered to the recipient’s servers. If bounce processing is on, this status could change shortly to ba_soft_fail, depending on the nature of the failure message.
lost – Messages where the tracking was lost and it is unclear if it was delivered or lost from the queue.
queued – Message is in the email server queue still waiting to be delivered to the recipient.
not_queued -- all statuses except "queued".
ba_soft_fail – Soft failure bounces received (when talking to the recipient’s servers or after successful delivery to the recipient’s servers).
ba_hard_fail – Hard failure bounces received after successful delivery to the recipient’s servers,
any_hard_fail – Results for ba_hard_fail OR perm_fail. I.e., all hard/permanent failures.
subject
String
Case-insensitive substring search of the message subject (in UTF8).
template_id
Integer
Optional template ID to select results only for those messages sent using the specified template. A value of 0 selects all.
to
String
Case-insensitive substring search of all recipient email addresses.
tracked_headers
String
If true and this report is for messages sent vis SMTP, then the results will include the six additional fields (header1, header2, header3, header1_value, header2_value, header3_value) which are used to track custom email message header data.
user_id
String
Restrict the report to the user with this specific User ID number

Responses

Status: 200 - Report content


getEmailSMTPOpenSummaryReportAccount

This report allows returns the number of opens that happened in the selected time period. See [report header columns in the response](/rest-api/report-responses.html#opens_count). *Note: if you are using LuxSci Secure Marketing v2 to send your email messages, then normal LuxSci click and open reporting is disabled (and you will not see click and open data in this report). The LuxSci Secure Marketing v2 platform his its own click and open tracking and reporting system and you should look in that interface for reports.* Dates, for the purposes of narrowing results, refer to the date the message was opened.

Access control required to execute this endpoint: Account: View Reports


/perl/api/v2/account/{accountId}/report/email/smtp/opens_count

Parameters

Path parameters
Name Description
accountId*
String
Required
Header parameters
Name Description
Cookie
Query parameters
Name Description
after_date
String
DATETIME. Return only matches dated after this date time. Format “YYYY-MM-DD HH:MM:SS” in GMT
before_date
String
DATETIME. Return only matches dated before this date time.
first_row
Integer
(Default value 0). All of the matches are sorted and numbered starting from 0. E.g. if you have 100,000 matches, these are rows 0 through 99,999. If you specify a first_row, then the returned matches will be those rows starting from that row. E.g. without a specification (or if you specify 0), you might get rows 0 through 49,999. In your next request you might specify first_row=50000 to get rows 50000 to 99,999.
from_date
String
DATETIME. Return only matches dated on or after this date time.
matches
Integer
(Default value 50000). You can set matches to any value from 0 to 50000. This sets the maximum number of matches that will be returned in response to your request. Note that if the response size starts to exceed 50MB, then the response can still include fewer than your “matches” number, to keep the response size reasonable. If you specify “0” here, then no matches will be returned; however, you will still get the information on the number of matches that there were. For asynchronous reports (ones where a destination is specified), the matches parameter is not limited to 50000, but it still defaults to 50000 if not specified. If you expect a larger number of rows, then you must explicitly approve the maximum size of the result set by setting matches appropriately. This helps prevent accidental queries that produce very larger result sets.
through_date
String
DATETIME. Return only matches dated before or on this date time.
destination
String
For reporting requests. Specifying a destination makes the report "asynchronous." This means that a background job will be created to run the report and upload the final CSV file to the requested destination. The API request to start the report will return immediately with a background "job number" and the filename that will be uploaded. The supported value of "destination" is currently only "sftp" for a Secure FTP upload over SSH (as opposed to ftps, which would be a Secure FTP upload over SSL). When "destination" is specified, additional destination parameters are also required. Note that for SFTP uploads, there is a 15-minute upload timeout -- uploads that take longer (e.g., due to slow SFTP servers) will be aborted. WARNING: Multiple concurrent large asynchronous report requests will impact your database performance: reports will take longer to generate and your LuxSci services will experience degraded/slower performance.
destination_directory
String
For asynchronous reporting requests. This optional parameter will be the subdirectory to change to on the SFTP server before uploading the report CSV file. Technically speaking, this will be the argument provided to the SFTP "chdir" command.
destination_hostname
String
For asynchronous reporting requests. This will be the hostname of the SFTP server to which the report CSV file should be uploaded.
destination_password
String
For asynchronous reporting requests. This will be the password to be used for the login to the SFTP server to which the report CSV file should be uploaded.
destination_username
String
For asynchronous reporting requests. This will be the username to be used for the login to the SFTP server to which the report CSV file should be uploaded.
filter1
String
Control when a summary report returns values (for use with automated reports). See https://luxsci.com/rest-api/reporting.html#filters
filter2
String
Control when a summary report returns values (for use with automated reports). See https://luxsci.com/rest-api/reporting.html#filters
filter3
String
Control when a summary report returns values (for use with automated reports). See https://luxsci.com/rest-api/reporting.html#filters
from
String
Case-insensitive substring search of the message “From” email address
header1
String
Case-insensitive name of the custom email header field to match against in the “header 1” column. I.e., if you were matching against “X-My-Header” and saving this in header 1, you would enter “X-My-Header” as the value here.

NOTE: Data is only stored in the customer header capturing fields/columns if you have explicitly enabled this feature in the “Account Administration > Email” area of the LuxSci user interface.
header1_operator
String
If this is present and one of the following 4 values, then the query will only return messages that included “header1” when “header1” was being tracked, and which also satisfy the follow the criteria:
  • is --- The value of the email header named “header1” in the send email must have been exactly the same as header1_value
  • not – The value of the email header named “header1” in the send email must not be exactly the same as header1_value
  • like – The value of the email header named “header1” in the send email must contain (case insensitive) the value in header1_value
  • notlike – The value of the email header named “header1” in the send email must not contain (case insensitive) the value in header1_value
I.e., if you configured your account to capture the value of the header “X-My-Header” and saving this in “header column 1” and an email was sent with the header “X-My-Header: gh6577hh-abc”. This would have been stored in the database. You could then find this message by passing to this API function:
  • header1 = “X-My-Header”
  • header1_operator = “is”
  • header1_value = “gh6577hh-abc”
Or by passing:
  • header1 = “X-My-Header”,/li>
  • header1_operator = “like”
  • header1_value = “abc”
header1_value
String
Text used with “header1_operator” for matching the value of the email header specified in the “header1” parameter in the original sent message.
header2
String
Like “header1” but applies to searching the header 2 column.
header2_operator
String
Like “header1_operator” but applies to searching the header 2 column.
header2_value
String
Like “header1_value” but applies to searching the header 2 column.
header3
String
Like “header1” but applies to searching the header 3 column.
header3_operator
String
Like “header1_operator” but applies to searching the header 3 column.
header3_value
String
Like “header1_value” but applies to searching the header 2 column.
opened
Integer
If specified, the results are restricted as follows:
opened < 0 – select messages where open tracking was not enabled.
opened = 0 – select messages where open tracking was enabled, but which have not yet been opened.
opened > 0 – select messages where open tracking was enabled and which have been opened at least once. When opened is positive, you will get one row back for each open; so, you can get multiple rows per message.

If you do not specify a value for “opened”, a value of “1” will be assumed.
subject
String
Case-insensitive substring search of the message subject (in UTF8).
to
String
Case-insensitive substring search of all recipient email addresses.
tracked_headers
String
If true and this report is for messages sent vis SMTP, then the results will include the six additional fields (header1, header2, header3, header1_value, header2_value, header3_value) which are used to track custom email message header data.
template_id
Integer
Optional template ID to select results only for those messages sent using the specified template. A value of 0 selects all.
user_id
String
Restrict the report to the user with this specific User ID number

Responses

Status: 200 - Report content


getEmailSMTPSentReportAccount

Return a list of all email messages sent sent via SMTP by users in this account. See also [API Reporting Basics](/rest-api/reporting.html) and [report header columns in the response](/rest-api/report-responses.html#sent).

Access control required to execute this endpoint: Account: View Reports


/perl/api/v2/account/{accountId}/report/email/smtp/sent

Parameters

Path parameters
Name Description
accountId*
String
Required
Header parameters
Name Description
Cookie
Query parameters
Name Description
after_date
String
DATETIME. Return only matches dated after this date time. Format “YYYY-MM-DD HH:MM:SS” in GMT
before_date
String
DATETIME. Return only matches dated before this date time.
first_row
Integer
(Default value 0). All of the matches are sorted and numbered starting from 0. E.g. if you have 100,000 matches, these are rows 0 through 99,999. If you specify a first_row, then the returned matches will be those rows starting from that row. E.g. without a specification (or if you specify 0), you might get rows 0 through 49,999. In your next request you might specify first_row=50000 to get rows 50000 to 99,999.
from_date
String
DATETIME. Return only matches dated on or after this date time.
matches
Integer
(Default value 50000). You can set matches to any value from 0 to 50000. This sets the maximum number of matches that will be returned in response to your request. Note that if the response size starts to exceed 50MB, then the response can still include fewer than your “matches” number, to keep the response size reasonable. If you specify “0” here, then no matches will be returned; however, you will still get the information on the number of matches that there were. For asynchronous reports (ones where a destination is specified), the matches parameter is not limited to 50000, but it still defaults to 50000 if not specified. If you expect a larger number of rows, then you must explicitly approve the maximum size of the result set by setting matches appropriately. This helps prevent accidental queries that produce very larger result sets.
through_date
String
DATETIME. Return only matches dated before or on this date time.
destination
String
For reporting requests. Specifying a destination makes the report "asynchronous." This means that a background job will be created to run the report and upload the final CSV file to the requested destination. The API request to start the report will return immediately with a background "job number" and the filename that will be uploaded. The supported value of "destination" is currently only "sftp" for a Secure FTP upload over SSH (as opposed to ftps, which would be a Secure FTP upload over SSL). When "destination" is specified, additional destination parameters are also required. Note that for SFTP uploads, there is a 15-minute upload timeout -- uploads that take longer (e.g., due to slow SFTP servers) will be aborted. WARNING: Multiple concurrent large asynchronous report requests will impact your database performance: reports will take longer to generate and your LuxSci services will experience degraded/slower performance.
destination_directory
String
For asynchronous reporting requests. This optional parameter will be the subdirectory to change to on the SFTP server before uploading the report CSV file. Technically speaking, this will be the argument provided to the SFTP "chdir" command.
destination_hostname
String
For asynchronous reporting requests. This will be the hostname of the SFTP server to which the report CSV file should be uploaded.
destination_password
String
For asynchronous reporting requests. This will be the password to be used for the login to the SFTP server to which the report CSV file should be uploaded.
destination_username
String
For asynchronous reporting requests. This will be the username to be used for the login to the SFTP server to which the report CSV file should be uploaded.
from
String
Case-insensitive substring search of the message “From” email address
header1
String
Case-insensitive name of the custom email header field to match against in the “header 1” column. I.e., if you were matching against “X-My-Header” and saving this in header 1, you would enter “X-My-Header” as the value here.

NOTE: Data is only stored in the customer header capturing fields/columns if you have explicitly enabled this feature in the “Account Administration > Email” area of the LuxSci user interface.
header1_operator
String
If this is present and one of the following 4 values, then the query will only return messages that included “header1” when “header1” was being tracked, and which also satisfy the follow the criteria:
  • is --- The value of the email header named “header1” in the send email must have been exactly the same as header1_value
  • not – The value of the email header named “header1” in the send email must not be exactly the same as header1_value
  • like – The value of the email header named “header1” in the send email must contain (case insensitive) the value in header1_value
  • notlike – The value of the email header named “header1” in the send email must not contain (case insensitive) the value in header1_value
I.e., if you configured your account to capture the value of the header “X-My-Header” and saving this in “header column 1” and an email was sent with the header “X-My-Header: gh6577hh-abc”. This would have been stored in the database. You could then find this message by passing to this API function:
  • header1 = “X-My-Header”
  • header1_operator = “is”
  • header1_value = “gh6577hh-abc”
Or by passing:
  • header1 = “X-My-Header”,/li>
  • header1_operator = “like”
  • header1_value = “abc”
header1_value
String
Text used with “header1_operator” for matching the value of the email header specified in the “header1” parameter in the original sent message.
header2
String
Like “header1” but applies to searching the header 2 column.
header2_operator
String
Like “header1_operator” but applies to searching the header 2 column.
header2_value
String
Like “header1_value” but applies to searching the header 2 column.
header3
String
Like “header1” but applies to searching the header 3 column.
header3_operator
String
Like “header1_operator” but applies to searching the header 3 column.
header3_value
String
Like “header1_value” but applies to searching the header 2 column.
ip
String
Case-insensitive substring search of the sender IP address (for SMTP reports only).
opt_out
String
Value:
0 – SecureLine Opt Out not used
-1 – SecureLine Opt Out use not recorded for some reason
1 – SecureLine Opt Out
secureline
String
Value:
any – Match anything
-1 – SecureLine usage not recorded for some reason
1 – SecureLine encryption was used
0 – SecureLine encryption was not used

If SecureLine was used, use the delivery status report to see more details.
sendmail_id
String
Return only the message with the specified sendmail_id.
sendmail_ids
String
Comma-delimited list of up to 100 sendmail ids. Returns any matching messages.
spam
String
Value:
0 – Message was not marked as spam by a recipient and returned in a Feed Back Loop
1 – Message was marked as spam by a recipient and returned in a Feed Back Loop
subject
String
Case-insensitive substring search of the message subject (in UTF-8).
to
String
Case-insensitive substring search of all recipient email addresses.
tracked_headers
String
If true and this report is for messages sent vis SMTP, then the results will include the six additional fields (header1, header2, header3, header1_value, header2_value, header3_value) which are used to track custom email message header data.
template_id
Integer
Optional template ID to select results only for those messages sent using the specified template. A value of 0 selects all.
user_id
String
Restrict the report to the user with this specific User ID number.

Responses

Status: 200 - Report content


getEmailSMTPTempFailReportAccount

This report allows you to download all temporary failure responses that were experienced when trying to deliver a message or messages to recipients. These provide insight into why it may have taken longer than expected to deliver a specific email message. See also [API Reporting Basics](/rest-api/reporting.html) and [report header columns in the response](/rest-api/report-responses.html#temp_fail).

Access control required to execute this endpoint: Account: View Reports


/perl/api/v2/account/{accountId}/report/email/smtp/temp_fail

Parameters

Path parameters
Name Description
accountId*
String
Required
Header parameters
Name Description
Cookie
Query parameters
Name Description
after_date
String
DATETIME. Return only matches dated after this date time. Format “YYYY-MM-DD HH:MM:SS” in GMT
before_date
String
DATETIME. Return only matches dated before this date time.
first_row
Integer
(Default value 0). All of the matches are sorted and numbered starting from 0. E.g. if you have 100,000 matches, these are rows 0 through 99,999. If you specify a first_row, then the returned matches will be those rows starting from that row. E.g. without a specification (or if you specify 0), you might get rows 0 through 49,999. In your next request you might specify first_row=50000 to get rows 50000 to 99,999.
from_date
String
DATETIME. Return only matches dated on or after this date time.
matches
Integer
(Default value 50000). You can set matches to any value from 0 to 50000. This sets the maximum number of matches that will be returned in response to your request. Note that if the response size starts to exceed 50MB, then the response can still include fewer than your “matches” number, to keep the response size reasonable. If you specify “0” here, then no matches will be returned; however, you will still get the information on the number of matches that there were. For asynchronous reports (ones where a destination is specified), the matches parameter is not limited to 50000, but it still defaults to 50000 if not specified. If you expect a larger number of rows, then you must explicitly approve the maximum size of the result set by setting matches appropriately. This helps prevent accidental queries that produce very larger result sets.
through_date
String
DATETIME. Return only matches dated before or on this date time.
destination
String
For reporting requests. Specifying a destination makes the report "asynchronous." This means that a background job will be created to run the report and upload the final CSV file to the requested destination. The API request to start the report will return immediately with a background "job number" and the filename that will be uploaded. The supported value of "destination" is currently only "sftp" for a Secure FTP upload over SSH (as opposed to ftps, which would be a Secure FTP upload over SSL). When "destination" is specified, additional destination parameters are also required. Note that for SFTP uploads, there is a 15-minute upload timeout -- uploads that take longer (e.g., due to slow SFTP servers) will be aborted. WARNING: Multiple concurrent large asynchronous report requests will impact your database performance: reports will take longer to generate and your LuxSci services will experience degraded/slower performance.
destination_directory
String
For asynchronous reporting requests. This optional parameter will be the subdirectory to change to on the SFTP server before uploading the report CSV file. Technically speaking, this will be the argument provided to the SFTP "chdir" command.
destination_hostname
String
For asynchronous reporting requests. This will be the hostname of the SFTP server to which the report CSV file should be uploaded.
destination_password
String
For asynchronous reporting requests. This will be the password to be used for the login to the SFTP server to which the report CSV file should be uploaded.
destination_username
String
For asynchronous reporting requests. This will be the username to be used for the login to the SFTP server to which the report CSV file should be uploaded.
sendmail_id
String
String. Return temp failures only the messages with the specified sendmail_id
sendmail_ids
String
Comma-delimited list of up to 100 sendmail ids. Returns temporary failures for any matching messages.
to
String
Case-insensitive substring search of all recipient email addresses.
user_id
Integer
Integer. Restrict the report to the user with this specific User ID number

Responses

Status: 200 - Report content


getEmailWebMailClickReportAccount

This report allows you to query on the “URL click” events (or lack thereof) for Webmail email messages that have email click tracking enabled. Using this command, it is possible to get a report of all individual clicks or to get reports about messages that have not yet been clicked on or for which click tracking was not enabled. See the query parameters for more detail. *Note: if you are using LuxSci Secure Marketing v2 to send your email messages, then normal LuxSci click and open reporting is disabled (and you will not see click and open data in this report). The LuxSci Secure Marketing v2 platform his its own click and open tracking and reporting system and you should look in that interface for reports.* See also [API Reporting Basics](/rest-api/reporting.html) and [report header columns in the response](/rest-api/report-responses.html#click). Dates, for the purposes of narrowing results, refer to the date the message was sent. This corresponds to the “date_sent” output field. However, if you set the “click_date” input parameter to true, then the “click_date” field will be used for date selections.

Access control required to execute this endpoint: Account: View Reports


/perl/api/v2/account/{accountId}/report/email/webmail/clicks

Parameters

Path parameters
Name Description
accountId*
String
Required
Header parameters
Name Description
Cookie
Query parameters
Name Description
after_date
String
DATETIME. Return only matches dated after this date time. Format “YYYY-MM-DD HH:MM:SS” in GMT
before_date
String
DATETIME. Return only matches dated before this date time.
first_row
Integer
(Default value 0). All of the matches are sorted and numbered starting from 0. E.g. if you have 100,000 matches, these are rows 0 through 99,999. If you specify a first_row, then the returned matches will be those rows starting from that row. E.g. without a specification (or if you specify 0), you might get rows 0 through 49,999. In your next request you might specify first_row=50000 to get rows 50000 to 99,999.
from_date
String
DATETIME. Return only matches dated on or after this date time.
matches
Integer
(Default value 50000). You can set matches to any value from 0 to 50000. This sets the maximum number of matches that will be returned in response to your request. Note that if the response size starts to exceed 50MB, then the response can still include fewer than your “matches” number, to keep the response size reasonable. If you specify “0” here, then no matches will be returned; however, you will still get the information on the number of matches that there were. For asynchronous reports (ones where a destination is specified), the matches parameter is not limited to 50000, but it still defaults to 50000 if not specified. If you expect a larger number of rows, then you must explicitly approve the maximum size of the result set by setting matches appropriately. This helps prevent accidental queries that produce very larger result sets.
through_date
String
DATETIME. Return only matches dated before or on this date time.
destination
String
For reporting requests. Specifying a destination makes the report "asynchronous." This means that a background job will be created to run the report and upload the final CSV file to the requested destination. The API request to start the report will return immediately with a background "job number" and the filename that will be uploaded. The supported value of "destination" is currently only "sftp" for a Secure FTP upload over SSH (as opposed to ftps, which would be a Secure FTP upload over SSL). When "destination" is specified, additional destination parameters are also required. Note that for SFTP uploads, there is a 15-minute upload timeout -- uploads that take longer (e.g., due to slow SFTP servers) will be aborted. WARNING: Multiple concurrent large asynchronous report requests will impact your database performance: reports will take longer to generate and your LuxSci services will experience degraded/slower performance.
destination_directory
String
For asynchronous reporting requests. This optional parameter will be the subdirectory to change to on the SFTP server before uploading the report CSV file. Technically speaking, this will be the argument provided to the SFTP "chdir" command.
destination_hostname
String
For asynchronous reporting requests. This will be the hostname of the SFTP server to which the report CSV file should be uploaded.
destination_password
String
For asynchronous reporting requests. This will be the password to be used for the login to the SFTP server to which the report CSV file should be uploaded.
destination_username
String
For asynchronous reporting requests. This will be the username to be used for the login to the SFTP server to which the report CSV file should be uploaded.
from
String
Case-insensitive substring search of the message “From” email address
clicked
Integer
If specified, the results are restricted as follows:
clicked < 0 – select messages where click tracking was not enabled.
clicked = 0 – select messages where click tracking was enabled, but where no URLs have yet been clicked by the recipient.
clicked > 0 – select messages where one or more URLs have been clicked by the recipient. When “clicked” is positive, you will get one row back for each click; so,you can get multiple rows per message.

If a value for “clicked” is not specified, a value of “1” will be assumed.
click_date
String
If true, the ”click_date” field will be used for all date selections. If false or not specified, the sent date (“date_sent”) will be used.
header1
String
Case-insensitive name of the custom email header field to match against in the “header 1” column. I.e., if you were matching against “X-My-Header” and saving this in header 1, you would enter “X-My-Header” as the value here.

NOTE: Data is only stored in the customer header capturing fields/columns if you have explicitly enabled this feature in the “Account Administration > Email” area of the LuxSci user interface.
header1_operator
String
If this is present and one of the following 4 values, then the query will only return messages that included “header1” when “header1” was being tracked, and which also satisfy the follow the criteria:
  • is --- The value of the email header named “header1” in the send email must have been exactly the same as header1_value
  • not – The value of the email header named “header1” in the send email must not be exactly the same as header1_value
  • like – The value of the email header named “header1” in the send email must contain (case insensitive) the value in header1_value
  • notlike – The value of the email header named “header1” in the send email must not contain (case insensitive) the value in header1_value
I.e., if you configured your account to capture the value of the header “X-My-Header” and saving this in “header column 1” and an email was sent with the header “X-My-Header: gh6577hh-abc”. This would have been stored in the database. You could then find this message by passing to this API function:
  • header1 = “X-My-Header”
  • header1_operator = “is”
  • header1_value = “gh6577hh-abc”
Or by passing:
  • header1 = “X-My-Header”,/li>
  • header1_operator = “like”
  • header1_value = “abc”
header1_value
String
Text used with “header1_operator” for matching the value of the email header specified in the “header1” parameter in the original sent message.
header2
String
Like “header1” but applies to searching the header 2 column.
header2_operator
String
Like “header1_operator” but applies to searching the header 2 column.
header2_value
String
Like “header1_value” but applies to searching the header 2 column.
header3
String
Like “header1” but applies to searching the header 3 column.
header3_operator
String
Like “header1_operator” but applies to searching the header 3 column.
header3_value
String
Like “header1_value” but applies to searching the header 2 column.
opened
Integer
If specified, the results are restricted as follows:
opened < 0 – select messages where open tracking was not enabled.
opened = 0 – select messages where open tracking was enabled, but which have not yet been opened.
opened > 0 – select messages where open tracking was enabled, and which have been opened at least once.
sendmail_id
String
String. Return only the messages with the specified sendmail_id
sendmail_ids
String
Comma-delimited list of up to 100 sendmail ids. Returns any matching messages.
status
String
Values:
delivered – Accepted by the recipient’s email servers and presumed delivered. If bounce processing is enabled, then this status could change later to ba_soft_fail or ba_hard_fail.
perm_fail – Messages that have permanently failed to be delivered to the recipient’s servers. If bounce processing is on, this status could change shortly to ba_soft_fail, depending on the nature of the failure message.
lost – Messages where the tracking was lost and it is unclear if it was delivered or lost from the queue.
queued – Message is in the email server queue still waiting to be delivered to the recipient.
not_queued -- all statuses except "queued".
ba_soft_fail – Soft failure bounces received (when talking to the recipient’s servers or after successful delivery to the recipient’s servers).
ba_hard_fail – Hard failure bounces received after successful delivery to the recipient’s servers,
any_hard_fail – Results for ba_hard_fail OR perm_fail. I.e., all hard/permanent failures.
subject
String
Case-insensitive substring search of the message subject (in UTF8).
to
String
Case-insensitive substring search of all recipient email addresses.
tracked_headers
String
If true and this report is for messages sent vis SMTP, then the results will include the six additional fields (header1, header2, header3, header1_value, header2_value, header3_value) which are used to track custom email message header data.
user_id
String
Restrict the report to the user with this specific User ID number
url
String
Substring match on the URL clicked.

Responses

Status: 200 - Report content


getEmailWebMailDeliveryStatusReportAccount

This report allows you to see how each Webmail message was sent to each recipient and what the delivery status is for each of these recipients. Note that delivery status changes over time as messages progress to the recipient’s servers and as bounce messages are sent back and processed. As the delivery status changes, the “last_update” date is also updated. See also [API Reporting Basics](/rest-api/reporting.html) and [report header columns in the response](/rest-api/report-responses.html#delivery). Dates, for the purposes of narrowing results, refer to the *date the message delivery status was last updated*. This corresponds to the “last_update” output field. This can be changed to the date the message was sent using the "sent_date" parameter.

Access control required to execute this endpoint: Account: View Reports


/perl/api/v2/account/{accountId}/report/email/webmail/delivery

Parameters

Path parameters
Name Description
accountId*
String
Required
Header parameters
Name Description
Cookie
Query parameters
Name Description
after_date
String
DATETIME. Return only matches dated after this date time. Format “YYYY-MM-DD HH:MM:SS” in GMT
before_date
String
DATETIME. Return only matches dated before this date time.
first_row
Integer
(Default value 0). All of the matches are sorted and numbered starting from 0. E.g. if you have 100,000 matches, these are rows 0 through 99,999. If you specify a first_row, then the returned matches will be those rows starting from that row. E.g. without a specification (or if you specify 0), you might get rows 0 through 49,999. In your next request you might specify first_row=50000 to get rows 50000 to 99,999.
from_date
String
DATETIME. Return only matches dated on or after this date time.
matches
Integer
(Default value 50000). You can set matches to any value from 0 to 50000. This sets the maximum number of matches that will be returned in response to your request. Note that if the response size starts to exceed 50MB, then the response can still include fewer than your “matches” number, to keep the response size reasonable. If you specify “0” here, then no matches will be returned; however, you will still get the information on the number of matches that there were. For asynchronous reports (ones where a destination is specified), the matches parameter is not limited to 50000, but it still defaults to 50000 if not specified. If you expect a larger number of rows, then you must explicitly approve the maximum size of the result set by setting matches appropriately. This helps prevent accidental queries that produce very larger result sets.
through_date
String
DATETIME. Return only matches dated before or on this date time.
destination
String
For reporting requests. Specifying a destination makes the report "asynchronous." This means that a background job will be created to run the report and upload the final CSV file to the requested destination. The API request to start the report will return immediately with a background "job number" and the filename that will be uploaded. The supported value of "destination" is currently only "sftp" for a Secure FTP upload over SSH (as opposed to ftps, which would be a Secure FTP upload over SSL). When "destination" is specified, additional destination parameters are also required. Note that for SFTP uploads, there is a 15-minute upload timeout -- uploads that take longer (e.g., due to slow SFTP servers) will be aborted. WARNING: Multiple concurrent large asynchronous report requests will impact your database performance: reports will take longer to generate and your LuxSci services will experience degraded/slower performance.
destination_directory
String
For asynchronous reporting requests. This optional parameter will be the subdirectory to change to on the SFTP server before uploading the report CSV file. Technically speaking, this will be the argument provided to the SFTP "chdir" command.
destination_hostname
String
For asynchronous reporting requests. This will be the hostname of the SFTP server to which the report CSV file should be uploaded.
destination_password
String
For asynchronous reporting requests. This will be the password to be used for the login to the SFTP server to which the report CSV file should be uploaded.
destination_username
String
For asynchronous reporting requests. This will be the username to be used for the login to the SFTP server to which the report CSV file should be uploaded.
clicked
Integer
Integer. If specified, the results are restricted as follows:
clicked < 0 – select messages where URL click tracking was not enabled.
clicked = 0 – select messages where URL click tracking was enabled, but where there have as yet been no clicks on any clinks in the messages.
clicked > 0 – select messages where URL click tracking was enabled and where there have been N or more clicks on links in the same message to the same recipient. N, in this case, is the number that you have specified as the value of the “clicked” parameter. I.e., using a value of “1” matches all messages that have had a link clicked on.
from
String
String. Case-insensitive substring search of the message “From” email Address
ip
String
String. Case-insensitive substring search of the sender IP address (for SMTP reports only).
header1
String
Case-insensitive name of the custom email header field to match against in the “header 1” column. I.e., if you were matching against “X-My-Header” and saving this in header 1, you would enter “X-My-Header” as the value here.

NOTE: Data is only stored in the customer header capturing fields/columns if you have explicitly enabled this feature in the “Account Administration > Email” area of the LuxSci user interface.
header1_operator
String
If this is present and one of the following 4 values, then the query will only return messages that included “header1” when “header1” was being tracked, and which also satisfy the follow the criteria:
  • is --- The value of the email header named “header1” in the send email must have been exactly the same as header1_value
  • not – The value of the email header named “header1” in the send email must not be exactly the same as header1_value
  • like – The value of the email header named “header1” in the send email must contain (case insensitive) the value in header1_value
  • notlike – The value of the email header named “header1” in the send email must not contain (case insensitive) the value in header1_value
I.e., if you configured your account to capture the value of the header “X-My-Header” and saving this in “header column 1” and an email was sent with the header “X-My-Header: gh6577hh-abc”. This would have been stored in the database. You could then find this message by passing to this API function:
  • header1 = “X-My-Header”
  • header1_operator = “is”
  • header1_value = “gh6577hh-abc”
Or by passing:
  • header1 = “X-My-Header”,/li>
  • header1_operator = “like”
  • header1_value = “abc”
header1_value
String
Text used with “header1_operator” for matching the value of the email header specified in the “header1” parameter in the original sent message.
header2
String
Like “header1” but applies to searching the header 2 column.
header2_operator
String
Like “header1_operator” but applies to searching the header 2 column.
header2_value
String
Like “header1_value” but applies to searching the header 2 column.
header3
String
Like “header1” but applies to searching the header 3 column.
header3_operator
String
Like “header1_operator” but applies to searching the header 3 column.
header3_value
String
Like “header1_value” but applies to searching the header 2 column.
opened
Integer
Integer. If specified, the results are restricted as follows:
opened < 0 – select messages where open tracking was not enabled.
opened = 0 – select messages where open tracking was enabled, but which have not yet been opened.
opened > 0 – select messages where open tracking was enabled and which have been opened at least N times. N, in this case, is the number that you have specified as the value of the “opened” parameter. I.e., using a value of “1” matches all messages that have been opened.
secureline
String
Enum. Value:
u – Message to this recipient did not use SecureLine (or Opt Out was used)
e – Message did use SecureLine
-2 – SecureLine was not used due to Opt Out being selected
-1 – SecureLine usage not recorded for some reason
1 – SecureLine:PGP was used
2 – SecureLine:S/MIME was used
3 – SecureLine:Escrow was used
4 – SecureLine:TLS was used
sendmail_id
String
String. Return only the messages with the specified sendmail_id
sendmail_ids
String
Comma-delimited list of up to 100 sendmail ids. Returns any matching messages.
sent_date
Integer
If set to true (i.e., 1), the email message sent date will be used for date/time selections, instead of the date of the last update of the delivery status.
spam
Integer
Enum. Value:
0 – Message was not marked as spam by a recipient and returned in a Feed Back Loop.
1 – Message was marked as spam by a recipient and returned in a Feed Back Loop
tls
Integer
Enum. Value:
0 – TLS was NOT used in the successful delivery of this message to the recipient server
1 – TLS was used in the successful delivery of this message to the recipient server
tracked_headers
String
If true and this report is for messages sent vis SMTP, then the results will include the six additional fields (header1, header2, header3, header1_value, header2_value, header3_value) which are used to track custom email message header data.
to
String
Case-insensitive substring search of all recipient email addresses.
user_id
Integer
Integer. Restrict the report to the user with this specific User ID number

Responses

Status: 200 - Report content


getEmailWebMailOpenReportAccount

This report allows you to query on the “opened” events (or lack thereof) for email messages sent via Webmail that have email open tracking enabled. Using this command, it is possible to get a report of all individual opens for messages or to get reports about messages that have not yet been opened or for which open tracking was not enabled. See the query parameters for more detail. *Note: if you are using LuxSci Secure Marketing v2 to send your email messages, then normal LuxSci click and open reporting is disabled (and you will not see click and open data in this report). The LuxSci Secure Marketing v2 platform his its own click and open tracking and reporting system and you should look in that interface for reports.* See also [API Reporting Basics](/rest-api/reporting.html) and [report header columns in the response](/rest-api/report-responses.html#open). Dates, for the purposes of narrowing results, refer to the date the message was sent. This corresponds to the “date_sent” output field. However, if you set the “open_date” input parameter to true, then the “open_date” field will be used for date selections.

Access control required to execute this endpoint: Account: View Reports


/perl/api/v2/account/{accountId}/report/email/webmail/opens

Parameters

Path parameters
Name Description
accountId*
String
Required
Header parameters
Name Description
Cookie
Query parameters
Name Description
after_date
String
DATETIME. Return only matches dated after this date time. Format “YYYY-MM-DD HH:MM:SS” in GMT
before_date
String
DATETIME. Return only matches dated before this date time.
first_row
Integer
(Default value 0). All of the matches are sorted and numbered starting from 0. E.g. if you have 100,000 matches, these are rows 0 through 99,999. If you specify a first_row, then the returned matches will be those rows starting from that row. E.g. without a specification (or if you specify 0), you might get rows 0 through 49,999. In your next request you might specify first_row=50000 to get rows 50000 to 99,999.
from_date
String
DATETIME. Return only matches dated on or after this date time.
matches
Integer
(Default value 50000). You can set matches to any value from 0 to 50000. This sets the maximum number of matches that will be returned in response to your request. Note that if the response size starts to exceed 50MB, then the response can still include fewer than your “matches” number, to keep the response size reasonable. If you specify “0” here, then no matches will be returned; however, you will still get the information on the number of matches that there were. For asynchronous reports (ones where a destination is specified), the matches parameter is not limited to 50000, but it still defaults to 50000 if not specified. If you expect a larger number of rows, then you must explicitly approve the maximum size of the result set by setting matches appropriately. This helps prevent accidental queries that produce very larger result sets.
through_date
String
DATETIME. Return only matches dated before or on this date time.
destination
String
For reporting requests. Specifying a destination makes the report "asynchronous." This means that a background job will be created to run the report and upload the final CSV file to the requested destination. The API request to start the report will return immediately with a background "job number" and the filename that will be uploaded. The supported value of "destination" is currently only "sftp" for a Secure FTP upload over SSH (as opposed to ftps, which would be a Secure FTP upload over SSL). When "destination" is specified, additional destination parameters are also required. Note that for SFTP uploads, there is a 15-minute upload timeout -- uploads that take longer (e.g., due to slow SFTP servers) will be aborted. WARNING: Multiple concurrent large asynchronous report requests will impact your database performance: reports will take longer to generate and your LuxSci services will experience degraded/slower performance.
destination_directory
String
For asynchronous reporting requests. This optional parameter will be the subdirectory to change to on the SFTP server before uploading the report CSV file. Technically speaking, this will be the argument provided to the SFTP "chdir" command.
destination_hostname
String
For asynchronous reporting requests. This will be the hostname of the SFTP server to which the report CSV file should be uploaded.
destination_password
String
For asynchronous reporting requests. This will be the password to be used for the login to the SFTP server to which the report CSV file should be uploaded.
destination_username
String
For asynchronous reporting requests. This will be the username to be used for the login to the SFTP server to which the report CSV file should be uploaded.
from
String
Case-insensitive substring search of the message “From” email address
header1
String
Case-insensitive name of the custom email header field to match against in the “header 1” column. I.e., if you were matching against “X-My-Header” and saving this in header 1, you would enter “X-My-Header” as the value here.

NOTE: Data is only stored in the customer header capturing fields/columns if you have explicitly enabled this feature in the “Account Administration > Email” area of the LuxSci user interface.
header1_operator
String
If this is present and one of the following 4 values, then the query will only return messages that included “header1” when “header1” was being tracked, and which also satisfy the follow the criteria:
  • is --- The value of the email header named “header1” in the send email must have been exactly the same as header1_value
  • not – The value of the email header named “header1” in the send email must not be exactly the same as header1_value
  • like – The value of the email header named “header1” in the send email must contain (case insensitive) the value in header1_value
  • notlike – The value of the email header named “header1” in the send email must not contain (case insensitive) the value in header1_value
I.e., if you configured your account to capture the value of the header “X-My-Header” and saving this in “header column 1” and an email was sent with the header “X-My-Header: gh6577hh-abc”. This would have been stored in the database. You could then find this message by passing to this API function:
  • header1 = “X-My-Header”
  • header1_operator = “is”
  • header1_value = “gh6577hh-abc”
Or by passing:
  • header1 = “X-My-Header”,/li>
  • header1_operator = “like”
  • header1_value = “abc”
header1_value
String
Text used with “header1_operator” for matching the value of the email header specified in the “header1” parameter in the original sent message.
header2
String
Like “header1” but applies to searching the header 2 column.
header2_operator
String
Like “header1_operator” but applies to searching the header 2 column.
header2_value
String
Like “header1_value” but applies to searching the header 2 column.
header3
String
Like “header1” but applies to searching the header 3 column.
header3_operator
String
Like “header1_operator” but applies to searching the header 3 column.
header3_value
String
Like “header1_value” but applies to searching the header 2 column.
opened
Integer
If specified, the results are restricted as follows:
opened < 0 – select messages where open tracking was not enabled.
opened = 0 – select messages where open tracking was enabled, but which have not yet been opened.
opened > 0 – select messages where open tracking was enabled and which have been opened at least once. When opened is positive, you will get one row back for each open; so, you can get multiple rows per message.

If you do not specify a value for “opened”, a value of “1” will be assumed.
open_date
Boolean
If true, the ”open_date” field will be used for all date selections. If false or not specified, the sent date (“date_sent”) will be used.
sendmail_id
String
Return only the messages with the specified sendmail_id.
sendmail_ids
String
Comma-delimited list of up to 100 sendmail ids. Returns any matching messages.
status
String
Values:
delivered – Accepted by the recipient’s email servers and presumed delivered. If bounce processing is enabled, then this status could change later to ba_soft_fail or ba_hard_fail.
perm_fail – Messages that have permanently failed to be delivered to the recipient’s servers. If bounce processing is on, this status could change shortly to ba_soft_fail, depending on the nature of the failure message.
lost – Messages where the tracking was lost and it is unclear if it was delivered or lost from the queue.
queued – Message is in the email server queue still waiting to be delivered to the recipient.
not_queued -- all statuses except "queued".
ba_soft_fail – Soft failure bounces received (when talking to the recipient’s servers or after successful delivery to the recipient’s servers).
ba_hard_fail – Hard failure bounces received after successful delivery to the recipient’s servers,
any_hard_fail – Results for ba_hard_fail OR perm_fail. I.e., all hard/permanent failures.
subject
String
Case-insensitive substring search of the message subject (in UTF8).
to
String
Case-insensitive substring search of all recipient email addresses.
tracked_headers
String
If true and this report is for messages sent vis SMTP, then the results will include the six additional fields (header1, header2, header3, header1_value, header2_value, header3_value) which are used to track custom email message header data.
user_id
String
Restrict the report to the user with this specific User ID number

Responses

Status: 200 - Report content


getEmailWebMailSentReportAccount

Return a list of all WebMail email messages sent by users in this account. See also [API Reporting Basics](/rest-api/reporting.html) and [report header columns in the response](/rest-api/report-responses.html#sent).

Access control required to execute this endpoint: Account: View Reports


/perl/api/v2/account/{accountId}/report/email/webmail/sent

Parameters

Path parameters
Name Description
accountId*
String
Required
Header parameters
Name Description
Cookie
Query parameters
Name Description
after_date
String
DATETIME. Return only matches dated after this date time. Format “YYYY-MM-DD HH:MM:SS” in GMT
before_date
String
DATETIME. Return only matches dated before this date time.
first_row
Integer
(Default value 0). All of the matches are sorted and numbered starting from 0. E.g. if you have 100,000 matches, these are rows 0 through 99,999. If you specify a first_row, then the returned matches will be those rows starting from that row. E.g. without a specification (or if you specify 0), you might get rows 0 through 49,999. In your next request you might specify first_row=50000 to get rows 50000 to 99,999.
from_date
String
DATETIME. Return only matches dated on or after this date time.
matches
Integer
(Default value 50000). You can set matches to any value from 0 to 50000. This sets the maximum number of matches that will be returned in response to your request. Note that if the response size starts to exceed 50MB, then the response can still include fewer than your “matches” number, to keep the response size reasonable. If you specify “0” here, then no matches will be returned; however, you will still get the information on the number of matches that there were. For asynchronous reports (ones where a destination is specified), the matches parameter is not limited to 50000, but it still defaults to 50000 if not specified. If you expect a larger number of rows, then you must explicitly approve the maximum size of the result set by setting matches appropriately. This helps prevent accidental queries that produce very larger result sets.
through_date
String
DATETIME. Return only matches dated before or on this date time.
destination
String
For reporting requests. Specifying a destination makes the report "asynchronous." This means that a background job will be created to run the report and upload the final CSV file to the requested destination. The API request to start the report will return immediately with a background "job number" and the filename that will be uploaded. The supported value of "destination" is currently only "sftp" for a Secure FTP upload over SSH (as opposed to ftps, which would be a Secure FTP upload over SSL). When "destination" is specified, additional destination parameters are also required. Note that for SFTP uploads, there is a 15-minute upload timeout -- uploads that take longer (e.g., due to slow SFTP servers) will be aborted. WARNING: Multiple concurrent large asynchronous report requests will impact your database performance: reports will take longer to generate and your LuxSci services will experience degraded/slower performance.
destination_directory
String
For asynchronous reporting requests. This optional parameter will be the subdirectory to change to on the SFTP server before uploading the report CSV file. Technically speaking, this will be the argument provided to the SFTP "chdir" command.
destination_hostname
String
For asynchronous reporting requests. This will be the hostname of the SFTP server to which the report CSV file should be uploaded.
destination_password
String
For asynchronous reporting requests. This will be the password to be used for the login to the SFTP server to which the report CSV file should be uploaded.
destination_username
String
For asynchronous reporting requests. This will be the username to be used for the login to the SFTP server to which the report CSV file should be uploaded.
from
String
Case-insensitive substring search of the message “From” email address
header1
String
Case-insensitive name of the custom email header field to match against in the “header 1” column. I.e., if you were matching against “X-My-Header” and saving this in header 1, you would enter “X-My-Header” as the value here.

NOTE: Data is only stored in the customer header capturing fields/columns if you have explicitly enabled this feature in the “Account Administration > Email” area of the LuxSci user interface.
header1_operator
String
If this is present and one of the following 4 values, then the query will only return messages that included “header1” when “header1” was being tracked, and which also satisfy the follow the criteria:
  • is --- The value of the email header named “header1” in the send email must have been exactly the same as header1_value
  • not – The value of the email header named “header1” in the send email must not be exactly the same as header1_value
  • like – The value of the email header named “header1” in the send email must contain (case insensitive) the value in header1_value
  • notlike – The value of the email header named “header1” in the send email must not contain (case insensitive) the value in header1_value
I.e., if you configured your account to capture the value of the header “X-My-Header” and saving this in “header column 1” and an email was sent with the header “X-My-Header: gh6577hh-abc”. This would have been stored in the database. You could then find this message by passing to this API function:
  • header1 = “X-My-Header”
  • header1_operator = “is”
  • header1_value = “gh6577hh-abc”
Or by passing:
  • header1 = “X-My-Header”,/li>
  • header1_operator = “like”
  • header1_value = “abc”
header1_value
String
Text used with “header1_operator” for matching the value of the email header specified in the “header1” parameter in the original sent message.
header2
String
Like “header1” but applies to searching the header 2 column.
header2_operator
String
Like “header1_operator” but applies to searching the header 2 column.
header2_value
String
Like “header1_value” but applies to searching the header 2 column.
header3
String
Like “header1” but applies to searching the header 3 column.
header3_operator
String
Like “header1_operator” but applies to searching the header 3 column.
header3_value
String
Like “header1_value” but applies to searching the header 2 column.
ip
String
Case-insensitive substring search of the sender IP address (for SMTP reports only).
opt_out
String
Value:
0 – SecureLine Opt Out not used
-1 – SecureLine Opt Out use not recorded for some reason
1 – SecureLine Opt Out
secureline
String
Value:
any – Match anything
-1 – SecureLine usage not recorded for some reason
1 – SecureLine encryption was used
0 – SecureLine encryption was not used

If SecureLine was used, use the delivery status report to see more details.
sendmail_id
String
Return only the message with the specified sendmail_id.
sendmail_ids
String
Comma-delimited list of up to 100 sendmail ids. Returns any matching messages.
spam
String
Value:
0 – Message was not marked as spam by a recipient and returned in a Feed Back Loop
1 – Message was marked as spam by a recipient and returned in a Feed Back Loop
subject
String
Case-insensitive substring search of the message subject (in UTF-8).
to
String
Case-insensitive substring search of all recipient email addresses.
tracked_headers
String
If true and this report is for messages sent vis SMTP, then the results will include the six additional fields (header1, header2, header3, header1_value, header2_value, header3_value) which are used to track custom email message header data.
user_id
String
Restrict the report to the user with this specific User ID number.

Responses

Status: 200 - Report content


getSMTPLoginFailureReportAccount

This report allows to see all SMTP login failures, as well as sending errors that resulted from our servers explicitly rejecting your request to send an email message for one reason or another. See also [API Reporting Basics](/rest-api/reporting.html) and [report header columns in the response](/rest-api/report-responses.html#smtp_login_fail).

Access control required to execute this endpoint: Account: View Reports


/perl/api/v2/account/{accountId}/report/login_fail/smtp

Parameters

Path parameters
Name Description
accountId*
String
Required
Header parameters
Name Description
Cookie
Query parameters
Name Description
after_date
String
DATETIME. Return only matches dated after this date time. Format “YYYY-MM-DD HH:MM:SS” in GMT
before_date
String
DATETIME. Return only matches dated before this date time.
first_row
Integer
(Default value 0). All of the matches are sorted and numbered starting from 0. E.g. if you have 100,000 matches, these are rows 0 through 99,999. If you specify a first_row, then the returned matches will be those rows starting from that row. E.g. without a specification (or if you specify 0), you might get rows 0 through 49,999. In your next request you might specify first_row=50000 to get rows 50000 to 99,999.
from_date
String
DATETIME. Return only matches dated on or after this date time.
matches
Integer
(Default value 50000). You can set matches to any value from 0 to 50000. This sets the maximum number of matches that will be returned in response to your request. Note that if the response size starts to exceed 50MB, then the response can still include fewer than your “matches” number, to keep the response size reasonable. If you specify “0” here, then no matches will be returned; however, you will still get the information on the number of matches that there were. For asynchronous reports (ones where a destination is specified), the matches parameter is not limited to 50000, but it still defaults to 50000 if not specified. If you expect a larger number of rows, then you must explicitly approve the maximum size of the result set by setting matches appropriately. This helps prevent accidental queries that produce very larger result sets.
through_date
String
DATETIME. Return only matches dated before or on this date time.
destination
String
For reporting requests. Specifying a destination makes the report "asynchronous." This means that a background job will be created to run the report and upload the final CSV file to the requested destination. The API request to start the report will return immediately with a background "job number" and the filename that will be uploaded. The supported value of "destination" is currently only "sftp" for a Secure FTP upload over SSH (as opposed to ftps, which would be a Secure FTP upload over SSL). When "destination" is specified, additional destination parameters are also required. Note that for SFTP uploads, there is a 15-minute upload timeout -- uploads that take longer (e.g., due to slow SFTP servers) will be aborted. WARNING: Multiple concurrent large asynchronous report requests will impact your database performance: reports will take longer to generate and your LuxSci services will experience degraded/slower performance.
destination_directory
String
For asynchronous reporting requests. This optional parameter will be the subdirectory to change to on the SFTP server before uploading the report CSV file. Technically speaking, this will be the argument provided to the SFTP "chdir" command.
destination_hostname
String
For asynchronous reporting requests. This will be the hostname of the SFTP server to which the report CSV file should be uploaded.
destination_password
String
For asynchronous reporting requests. This will be the password to be used for the login to the SFTP server to which the report CSV file should be uploaded.
destination_username
String
For asynchronous reporting requests. This will be the username to be used for the login to the SFTP server to which the report CSV file should be uploaded.
ip
String
String. Case-insensitive substring search of the message “IP Address” if the email program or device that made the connection.
Reason
String
String Case-insensitive substring search of the login failure / reason data.

Responses

Status: 200 - Report content


SecureForm

deleteSecureFormDatabaseFile

This function is used to remove a file associated with a row in your SecureForm database.

Access control required to execute this endpoint: Account: SecureForm Database - Delete


/perl/api/v2/account/{accountId}/secureforms/{formID}/db/{rowIndex}/file/{fileIndex}

Parameters

Path parameters
Name Description
accountId*
String
Required
formID*
String
Required
rowIndex*
String
Required
fileIndex*
String
Required
Header parameters
Name Description
Cookie

Responses

Status: 200 - standard


deleteSecureFormDatabaseRow

This function allows you to delete a row from your SecureForm database, based on the row index. This function will delete the row and any associated files. This API call is audited: a record will be made of the particular API Integration and IP address that “deleted” each matching row (also implying that any associated files have been removed).

Access control required to execute this endpoint: Account: SecureForm Database - Delete


/perl/api/v2/account/{accountId}/secureforms/{formID}/db/rows/{index}

Parameters

Path parameters
Name Description
accountId*
String
Required
formID*
String
Required
index*
String
Required
Header parameters
Name Description
Cookie

Responses

Status: 200 - standard simple response


getSecureForm

Returns details on a specific SecureForm configuration, based on the configuration’s unique ID.

Access control required to execute this endpoint: Account: SecureForm Configuration


/perl/api/v2/account/{accountId}/secureforms/{formID}

Parameters

Path parameters
Name Description
accountId*
String
Required
formID*
String
Required
Header parameters
Name Description
Cookie

Responses

Status: 200 - The Response Body contains a “data” keyword contains one object which provides details about the specified form. The keywords and values in this object are the same as those defined for the “Get SecureForm List” operation.


getSecureFormDatabaseFile

This function is used to retrieve a file associated with a row in your SecureForm database. You will need the row index and the file ID (which you can retrieve by reading the row data using other API calls). If the file was encrypted at rest in the database, it will be decrypted for you. This API call is audited: a record will be made of the particular API Integration and IP address that “read” each file.

Access control required to execute this endpoint: Account: SecureForm Database - Read


/perl/api/v2/account/{accountId}/secureforms/{formID}/db/{rowIndex}/file/{fileIndex}

Parameters

Path parameters
Name Description
accountId*
String
Required
formID*
String
Required
rowIndex*
String
Required
fileIndex*
String
Required
Header parameters
Name Description
Cookie

Responses

Status: 200 - The JSON response body has a data object


getSecureFormDatabasePosts

Returns details on the posts currently stored in the database table associated with a specific SecureForm configuration. This function is recommended for use when synchronizing or periodically downloading new rows to an external source: it allows you to quickly and easily see what, if any, entries are new relative to your last actions (if you saved the last index or date when you previously downloaded data). You can optionally pass one or more parameters to narrow down the scope of what rows are examined to produce the summary results. By default, all table rows are examined. All criteria passed as parameters are used; it is possible (and easy) to specify mutually exclusive parameters that result in no rows being examined (e.g. all rows with an index greater than 100 and less than 50).

Access control required to execute this endpoint: Account: SecureForm Database - Read


/perl/api/v2/account/{accountId}/secureforms/{formID}/db

Parameters

Path parameters
Name Description
accountId*
String
Required
formID*
String
Required
Header parameters
Name Description
Cookie
Query parameters
Name Description
after_date
String
DATETIME. All rows added after thes pecified date time (in GMT, format “YYYY-MM-DD HH:MM:SS”).
after_index
Integer
All rows whose index is greater than the specified value
before_date
String
DATETIME. All rows added before the specified date time
before_index
Integer
All rows whose index is less than the specified value
from_date
String
DATETIME. All rows added on or after the specified date time
from_index
Integer
All rows whose index is greater than or equal to the specified value.
through_date
String
DATETIME. All rows added on or before the specified date time
through_index
Integer
All rows whose index is less than or equal to the specified value.

Responses

Status: 200 - The Response Body contains a “data” object with keywords and values.


getSecureFormDatabaseRow

This function works the same as “Get SecureForm Database Rows”, except that you specify the row index and get back up to 1 row. This index is the `\_\_index\_\_` field for the row. This API call is audited: a record will be made of the particular API Integration and IP address that “read” each matching row.

Access control required to execute this endpoint: Account: SecureForm Database - Read


/perl/api/v2/account/{accountId}/secureforms/{formID}/db/rows/{index}

Parameters

Path parameters
Name Description
accountId*
String
Required
formID*
String
Required
index*
String
Required
Header parameters
Name Description
Cookie

Responses

Status: 200 - The JSON response body is the SAME as that returned for the “Database Rows” command, except that insted of a “rows” keyword with an array of matching rows, there is a `row` keyword which holds the object data for the requested row. This will be `null` if that row was not found.


getSecureFormDatabaseRows

This function returns the actual content of all database rows matching your query. Encrypted database fields will be automatically decrypted and the actual values of the fields returned. This API call is audited: a record will be made of the particular API Integration and IP address that “read” each matching row. You can optionally pass one or more parameters to narrow down the scope of what rows are returned. These parameters are the same as those for “Get SecureForm Database Info”.

Access control required to execute this endpoint: Account: SecureForm Database - Read


/perl/api/v2/account/{accountId}/secureforms/{formID}/db/rows

Parameters

Path parameters
Name Description
accountId*
String
Required
formID*
String
Required
Header parameters
Name Description
Cookie
Query parameters
Name Description
after_date
String
DATETIME. All rows added after thes pecified date time (in GMT, format “YYYY-MM-DD HH:MM:SS”).
after_index
Integer
All rows whose index is greater than the specified value
before_date
String
DATETIME. All rows added before the specified date time
before_index
Integer
All rows whose index is less than the specified value
from_date
String
DATETIME. All rows added on or after the specified date time
from_index
Integer
All rows whose index is greater than or equal to the specified value.
through_date
String
DATETIME. All rows added on or before the specified date time
through_index
Integer
All rows whose index is less than or equal to the specified value.

Responses

Status: 200 - Up to 500 rows can be returned per API call. If more rows match, only the first 500 (sorted by row index) are actually returned. The “data” body element will contain 2 items. The first is called `fields`. This is an object where the keywords are the physical database column names in use for each column of data. These keywords correspond to the keywords in the objects returned in the `rows` array. The values of these keywords are corresponding the actual field names from your form. E.g., in many cases the form field name cannot be used “as is” as a database column name and must be “sanitized”. You can use this `fields` object to map between the database column names and the original form field names. The second is called `rows`. This is an array of objects. Each object contains the data for a single matching row. The keywords are the database column names, the values are the row values for those columns. Values that were encrypted in the database are automatically decrypted and the real value is returned. If the row cannot be decrypted using the saved encryption key for this SecureForm configuration (e.g. if it was saved using some other SecureForm configuration and a different key), then the encrypted row values will all have the value of the word `ENCRYPTED`. Files are not downloaded with this function; however, information as to what files are available is included with each row of data. Separate functions are used to request individual files Explanations of common database columns shown below.

Access control required to execute this endpoint: Account: SecureForm Database - Read


getSecureFormList

Return a list of all SecureForm configurations currently defined in your account.

Access control required to execute this endpoint: Account: SecureForm Configuration


/perl/api/v2/account/{accountId}/secureforms

Parameters

Path parameters
Name Description
accountId*
String
Required
Header parameters
Name Description
Cookie

Responses

Status: 200 - The Response Body contains a “data” keyword which is an array of objects, one for each SecureForm configuration.


SecureSend

changeSecureSendUserPassword

You can do this with the User Update function, above. We provide a simple, direct method here as well.

Access control required to execute this endpoint: Account: SecureSend Namespaces - Manage


/perl/api/v2/account/{accountId}/pl/namespaces/{namespaceId}/users/{username}/password

Parameters

Path parameters
Name Description
accountId*
String
Required
namespaceId*
String
Required
username*
String
Required
Header parameters
Name Description
Cookie
Body parameters
Name Description
body

Responses

Status: 200 - Standard simple success


createOrUpdateSecureSendUser

Create a new SecureSend User in a specific NameSpace. This function also validates the user’s account so the user does not have to do anything (like checking a link in his/her email) to start using the account. If an account already exists for the specified user, then this request will merely update the user’s account, changing any data passed through. The “username” must be the email address (which is also the login) of the user to be created or updated. When updating a user, request parameters omitted will not be updated.

Access control required to execute this endpoint: Account: SecureSend Namespaces - Manage


/perl/api/v2/account/{accountId}/pl/namespaces/{namespaceId}/users/{username}

Parameters

Path parameters
Name Description
accountId*
String
Required
namespaceId*
String
Required
username*
String
Required
Header parameters
Name Description
Cookie
Body parameters
Name Description
body

Responses

Status: 200 - Standard simple success


getSecureSendUserList

Return a list of all users in this NameSpace.

Access control required to execute this endpoint: Account: SecureSend Namespaces - Manage


/perl/api/v2/account/{accountId}/pl/namespaces/{namespaceId}/users

Parameters

Path parameters
Name Description
accountId*
String
Required
namespaceId*
String
Required
Header parameters
Name Description
Cookie

Responses

Status: 200 - This returns a list of objects.



Servers

getServerStatus

This report allows you to retrieve specific current status of a specific server. This request will actually directly interrogate the server for some of this information; in situations where the server is overloaded or down or very slow, *this API will fail.*

Access control required to execute this endpoint: Account: Servers - Report


/perl/api/v2/account/{accountId}/server/{serverId}

Parameters

Path parameters
Name Description
accountId*
String
Required
serverId*
String
Should be the numeric server_id returned by the Server List API call, above. However, it can also be the short host name. I.e., if server with host rs999 has a server_id of 197890 then you can use either 197890 or 999 as the server_id.
Required
Header parameters
Name Description
Cookie

Responses

Status: 200 - Server information. The data field in the JSON response has all of the keywords defined in the “Server List” command, above, as well as additional keywords.


getServers

This report allows you to retrieve general information about all of the dedicated servers associated with your account. {{ACL: Account: Servers - Report}


/perl/api/v2/account/{accountId}/servers

Parameters

Path parameters
Name Description
accountId*
String
Required
Header parameters
Name Description
Cookie

Responses

Status: 200 - List of servers. The data field in the JSON response is a list of hashes, one for every server. This list will be empty if your account does not have any dedicated servers.


serverEmptyAllEmailQueues

This command allows you to remove all email messages that are queued. These are the mail_queue_trying and mail_queue_unprocessed messages returned by the server status call. Messages that have not yet been processed will be deleted by this call.


/perl/api/v2/account/{accountId}/server/{serverId}/sending_queues/all

Parameters

Path parameters
Name Description
accountId*
String
Required
serverId*
String
Should be the numeric server_id returned by the Server List API call, above. However, it can also be the short host name. I.e., if server with host rs999 has a server_id of 197890 then you can use either 197890 or 999 as the server_id.
Required
Header parameters
Name Description
Cookie

Responses

Status: 200 - Simple success response.


serverEmptyEmailQueues

This command allows you to remove all email messages that are queued and trying to be delivered to recipients. These are the mail_queue_trying messages returned by the server status call. Messages that have not yet been processed are not deleted.


/perl/api/v2/account/{accountId}/server/{serverId}/sending_queues

Parameters

Path parameters
Name Description
accountId*
String
Required
serverId*
String
Should be the numeric server_id returned by the Server List API call, above. However, it can also be the short host name. I.e., if server with host rs999 has a server_id of 197890 then you can use either 197890 or 999 as the server_id.
Required
Header parameters
Name Description
Cookie

Responses

Status: 200 - Simple success response.


setServerSendngRate

This command allows you to update the email processing rate limits for this server. These rate limits govern the rate at which messages are processed and delivered to the queues for delivery to recipients, for IP Warmup purposes. These settings to not impact messages already processed trying to be delivered to recipients.


/perl/api/v2/account/{accountId}/server/{serverId}/sending_rate

Parameters

Path parameters
Name Description
accountId*
String
Required
serverId*
String
Should be the numeric server_id returned by the Server List API call, above. However, it can also be the short host name. I.e., if server with host rs999 has a server_id of 197890 then you can use either 197890 or 999 as the server_id.
Required
Header parameters
Name Description
Cookie
Body parameters
Name Description
body

Responses

Status: 200 - Simple success response.


User Reports

getEmailFeedBackLoopsReportUser

This report allows to see what messages that `username` havs sent successfully that have been “marked as spam” by recipients and this information has come back to LuxSci via one of our feed-back loops. See also [API Reporting Basics](/rest-api/reporting.html) and [report header columns in the response](/rest-api/report-responses.html#fbl).

Access control required to execute this endpoint: User: View Reports


/perl/api/v2/user/{username}/report/email/fbl

Parameters

Path parameters
Name Description
username*
String
Required
Header parameters
Name Description
Cookie
Query parameters
Name Description
after_date
String
DATETIME. Return only matches dated after this date time. Format “YYYY-MM-DD HH:MM:SS” in GMT
before_date
String
DATETIME. Return only matches dated before this date time.
first_row
Integer
(Default value 0). All of the matches are sorted and numbered starting from 0. E.g. if you have 100,000 matches, these are rows 0 through 99,999. If you specify a first_row, then the returned matches will be those rows starting from that row. E.g. without a specification (or if you specify 0), you might get rows 0 through 49,999. In your next request you might specify first_row=50000 to get rows 50000 to 99,999.
from_date
String
DATETIME. Return only matches dated on or after this date time.
matches
Integer
(Default value 50000). You can set matches to any value from 0 to 50000. This sets the maximum number of matches that will be returned in response to your request. Note that if the response size starts to exceed 50MB, then the response can still include fewer than your “matches” number, to keep the response size reasonable. If you specify “0” here, then no matches will be returned; however, you will still get the information on the number of matches that there were. For asynchronous reports (ones where a destination is specified), the matches parameter is not limited to 50000, but it still defaults to 50000 if not specified. If you expect a larger number of rows, then you must explicitly approve the maximum size of the result set by setting matches appropriately. This helps prevent accidental queries that produce very larger result sets.
through_date
String
DATETIME. Return only matches dated before or on this date time.
destination
String
For reporting requests. Specifying a destination makes the report "asynchronous." This means that a background job will be created to run the report and upload the final CSV file to the requested destination. The API request to start the report will return immediately with a background "job number" and the filename that will be uploaded. The supported value of "destination" is currently only "sftp" for a Secure FTP upload over SSH (as opposed to ftps, which would be a Secure FTP upload over SSL). When "destination" is specified, additional destination parameters are also required. Note that for SFTP uploads, there is a 15-minute upload timeout -- uploads that take longer (e.g., due to slow SFTP servers) will be aborted. WARNING: Multiple concurrent large asynchronous report requests will impact your database performance: reports will take longer to generate and your LuxSci services will experience degraded/slower performance.
destination_directory
String
For asynchronous reporting requests. This optional parameter will be the subdirectory to change to on the SFTP server before uploading the report CSV file. Technically speaking, this will be the argument provided to the SFTP "chdir" command.
destination_hostname
String
For asynchronous reporting requests. This will be the hostname of the SFTP server to which the report CSV file should be uploaded.
destination_password
String
For asynchronous reporting requests. This will be the password to be used for the login to the SFTP server to which the report CSV file should be uploaded.
destination_username
String
For asynchronous reporting requests. This will be the username to be used for the login to the SFTP server to which the report CSV file should be uploaded.
from
String
String Case-insensitive substring search of the message “From” email address
subject
String
String Case-insensitive substring search of the message subject (in UTF-8).
to
String
String. Case-insensitive substring search of all recipient email addresses.
user_id
Integer
Integer Restrict the report to the user with this specific User ID number.

Responses

Status: 200 - Report content


getEmailFeedBackLoopsSummaryReportUser

This report allows to see how many messages have been marked as spam. The date of the compliant is used for date filters. See also [API Reporting Basics](/rest-api/reporting.html) and [report header columns in the response](/rest-api/report-responses.html#fbl_count).

Access control required to execute this endpoint: User: View Reports


/perl/api/v2/user/{username}/report/email/fbl_count

Parameters

Path parameters
Name Description
username*
String
Required
Header parameters
Name Description
Cookie
Query parameters
Name Description
after_date
String
DATETIME. Return only matches dated after this date time. Format “YYYY-MM-DD HH:MM:SS” in GMT
before_date
String
DATETIME. Return only matches dated before this date time.
first_row
Integer
(Default value 0). All of the matches are sorted and numbered starting from 0. E.g. if you have 100,000 matches, these are rows 0 through 99,999. If you specify a first_row, then the returned matches will be those rows starting from that row. E.g. without a specification (or if you specify 0), you might get rows 0 through 49,999. In your next request you might specify first_row=50000 to get rows 50000 to 99,999.
from_date
String
DATETIME. Return only matches dated on or after this date time.
matches
Integer
(Default value 50000). You can set matches to any value from 0 to 50000. This sets the maximum number of matches that will be returned in response to your request. Note that if the response size starts to exceed 50MB, then the response can still include fewer than your “matches” number, to keep the response size reasonable. If you specify “0” here, then no matches will be returned; however, you will still get the information on the number of matches that there were. For asynchronous reports (ones where a destination is specified), the matches parameter is not limited to 50000, but it still defaults to 50000 if not specified. If you expect a larger number of rows, then you must explicitly approve the maximum size of the result set by setting matches appropriately. This helps prevent accidental queries that produce very larger result sets.
through_date
String
DATETIME. Return only matches dated before or on this date time.
destination
String
For reporting requests. Specifying a destination makes the report "asynchronous." This means that a background job will be created to run the report and upload the final CSV file to the requested destination. The API request to start the report will return immediately with a background "job number" and the filename that will be uploaded. The supported value of "destination" is currently only "sftp" for a Secure FTP upload over SSH (as opposed to ftps, which would be a Secure FTP upload over SSL). When "destination" is specified, additional destination parameters are also required. Note that for SFTP uploads, there is a 15-minute upload timeout -- uploads that take longer (e.g., due to slow SFTP servers) will be aborted. WARNING: Multiple concurrent large asynchronous report requests will impact your database performance: reports will take longer to generate and your LuxSci services will experience degraded/slower performance.
destination_directory
String
For asynchronous reporting requests. This optional parameter will be the subdirectory to change to on the SFTP server before uploading the report CSV file. Technically speaking, this will be the argument provided to the SFTP "chdir" command.
destination_hostname
String
For asynchronous reporting requests. This will be the hostname of the SFTP server to which the report CSV file should be uploaded.
destination_password
String
For asynchronous reporting requests. This will be the password to be used for the login to the SFTP server to which the report CSV file should be uploaded.
destination_username
String
For asynchronous reporting requests. This will be the username to be used for the login to the SFTP server to which the report CSV file should be uploaded.
filter1
String
Control when a summary report returns values (for use with automated reports). See https://luxsci.com/rest-api/reporting.html#filters
filter2
String
Control when a summary report returns values (for use with automated reports). See https://luxsci.com/rest-api/reporting.html#filters
filter3
String
Control when a summary report returns values (for use with automated reports). See https://luxsci.com/rest-api/reporting.html#filters
from
String
String Case-insensitive substring search of the message “From” email address
subject
String
String Case-insensitive substring search of the message subject (in UTF-8).
to
String
String. Case-insensitive substring search of all recipient email addresses.
user_id
Integer
Integer Restrict the report to the user with this specific User ID number.

Responses

Status: 200 - Report content. The summary header field is named compliants.


getEmailSMTPClickReportUser

This report allows you to query on the “URL click” events (or lack thereof) for email messages sent via SMTP by `username` that have email click tracking enabled. Using this command, it is possible to get a report of all individual clicks or to get reports about messages that have not yet been clicked on or for which click tracking was not enabled. See the query parameters for more detail. *Note that if you are using LuxSci Secure Marketing v2 to send your email messages, then normal LuxSci click and open reporting is disabled (and you will not see click and open data in this report). The LuxSci Secure Marketing v2 platform his its own click and open tracking and reporting system and you should look in that interface for reports.* See also [API Reporting Basics](/rest-api/reporting.html) and [report header columns in the response](/rest-api/report-responses.html#click). Dates, for the purposes of narrowing results, refer to the date the message was sent. This corresponds to the `date_sent` output field. However, if you set the `click_date` input parameter to true, then the `click_date` field will be used for date selections.

Access control required to execute this endpoint: User: View Reports


/perl/api/v2/user/{username}/report/email/smtp/clicks

Parameters

Path parameters
Name Description
username*
String
Required
Header parameters
Name Description
Cookie
Query parameters
Name Description
after_date
String
DATETIME. Return only matches dated after this date time. Format “YYYY-MM-DD HH:MM:SS” in GMT
before_date
String
DATETIME. Return only matches dated before this date time.
first_row
Integer
(Default value 0). All of the matches are sorted and numbered starting from 0. E.g. if you have 100,000 matches, these are rows 0 through 99,999. If you specify a first_row, then the returned matches will be those rows starting from that row. E.g. without a specification (or if you specify 0), you might get rows 0 through 49,999. In your next request you might specify first_row=50000 to get rows 50000 to 99,999.
from_date
String
DATETIME. Return only matches dated on or after this date time.
matches
Integer
(Default value 50000). You can set matches to any value from 0 to 50000. This sets the maximum number of matches that will be returned in response to your request. Note that if the response size starts to exceed 50MB, then the response can still include fewer than your “matches” number, to keep the response size reasonable. If you specify “0” here, then no matches will be returned; however, you will still get the information on the number of matches that there were. For asynchronous reports (ones where a destination is specified), the matches parameter is not limited to 50000, but it still defaults to 50000 if not specified. If you expect a larger number of rows, then you must explicitly approve the maximum size of the result set by setting matches appropriately. This helps prevent accidental queries that produce very larger result sets.
through_date
String
DATETIME. Return only matches dated before or on this date time.
destination
String
For reporting requests. Specifying a destination makes the report "asynchronous." This means that a background job will be created to run the report and upload the final CSV file to the requested destination. The API request to start the report will return immediately with a background "job number" and the filename that will be uploaded. The supported value of "destination" is currently only "sftp" for a Secure FTP upload over SSH (as opposed to ftps, which would be a Secure FTP upload over SSL). When "destination" is specified, additional destination parameters are also required. Note that for SFTP uploads, there is a 15-minute upload timeout -- uploads that take longer (e.g., due to slow SFTP servers) will be aborted. WARNING: Multiple concurrent large asynchronous report requests will impact your database performance: reports will take longer to generate and your LuxSci services will experience degraded/slower performance.
destination_directory
String
For asynchronous reporting requests. This optional parameter will be the subdirectory to change to on the SFTP server before uploading the report CSV file. Technically speaking, this will be the argument provided to the SFTP "chdir" command.
destination_hostname
String
For asynchronous reporting requests. This will be the hostname of the SFTP server to which the report CSV file should be uploaded.
destination_password
String
For asynchronous reporting requests. This will be the password to be used for the login to the SFTP server to which the report CSV file should be uploaded.
destination_username
String
For asynchronous reporting requests. This will be the username to be used for the login to the SFTP server to which the report CSV file should be uploaded.
from
String
Case-insensitive substring search of the message “From” email address
clicked
Integer
If specified, the results are restricted as follows:
clicked < 0 – select messages where click tracking was not enabled.
clicked = 0 – select messages where click tracking was enabled, but where no URLs have yet been clicked by the recipient.
clicked > 0 – select messages where one or more URLs have been clicked by the recipient. When “clicked” is positive, you will get one row back for each click; so,you can get multiple rows per message.

If a value for “clicked” is not specified, a value of “1” will be assumed.
click_date
String
If true, the ”click_date” field will be used for all date selections. If false or not specified, the sent date (“date_sent”) will be used.
header1
String
Case-insensitive name of the custom email header field to match against in the “header 1” column. I.e., if you were matching against “X-My-Header” and saving this in header 1, you would enter “X-My-Header” as the value here.

NOTE: Data is only stored in the customer header capturing fields/columns if you have explicitly enabled this feature in the “Account Administration > Email” area of the LuxSci user interface.
header1_operator
String
If this is present and one of the following 4 values, then the query will only return messages that included “header1” when “header1” was being tracked, and which also satisfy the follow the criteria:
  • is --- The value of the email header named “header1” in the send email must have been exactly the same as header1_value
  • not – The value of the email header named “header1” in the send email must not be exactly the same as header1_value
  • like – The value of the email header named “header1” in the send email must contain (case insensitive) the value in header1_value
  • notlike – The value of the email header named “header1” in the send email must not contain (case insensitive) the value in header1_value
I.e., if you configured your account to capture the value of the header “X-My-Header” and saving this in “header column 1” and an email was sent with the header “X-My-Header: gh6577hh-abc”. This would have been stored in the database. You could then find this message by passing to this API function:
  • header1 = “X-My-Header”
  • header1_operator = “is”
  • header1_value = “gh6577hh-abc”
Or by passing:
  • header1 = “X-My-Header”,/li>
  • header1_operator = “like”
  • header1_value = “abc”
header1_value
String
Text used with “header1_operator” for matching the value of the email header specified in the “header1” parameter in the original sent message.
header2
String
Like “header1” but applies to searching the header 2 column.
header2_operator
String
Like “header1_operator” but applies to searching the header 2 column.
header2_value
String
Like “header1_value” but applies to searching the header 2 column.
header3
String
Like “header1” but applies to searching the header 3 column.
header3_operator
String
Like “header1_operator” but applies to searching the header 3 column.
header3_value
String
Like “header1_value” but applies to searching the header 2 column.
opened
Integer
If specified, the results are restricted as follows:
opened < 0 – select messages where open tracking was not enabled.
opened = 0 – select messages where open tracking was enabled, but which have not yet been opened.
opened > 0 – select messages where open tracking was enabled, and which have been opened at least once.
sendmail_id
String
String. Return only the messages with the specified sendmail_id
sendmail_ids
String
Comma-delimited list of up to 100 sendmail ids. Returns any matching messages.
status
String
Values:
delivered – Accepted by the recipient’s email servers and presumed delivered. If bounce processing is enabled, then this status could change later to ba_soft_fail or ba_hard_fail.
perm_fail – Messages that have permanently failed to be delivered to the recipient’s servers. If bounce processing is on, this status could change shortly to ba_soft_fail, depending on the nature of the failure message.
lost – Messages where the tracking was lost and it is unclear if it was delivered or lost from the queue.
queued – Message is in the email server queue still waiting to be delivered to the recipient.
not_queued -- all statuses except "queued".
ba_soft_fail – Soft failure bounces received (when talking to the recipient’s servers or after successful delivery to the recipient’s servers).
ba_hard_fail – Hard failure bounces received after successful delivery to the recipient’s servers,
any_hard_fail – Results for ba_hard_fail OR perm_fail. I.e., all hard/permanent failures.
subject
String
Case-insensitive substring search of the message subject (in UTF8).
to
String
Case-insensitive substring search of all recipient email addresses.
tracked_headers
String
If true and this report is for messages sent vis SMTP, then the results will include the six additional fields (header1, header2, header3, header1_value, header2_value, header3_value) which are used to track custom email message header data.
template_id
Integer
Optional template ID to select results only for those messages sent using the specified template. A value of 0 selects all.
user_id
String
Restrict the report to the user with this specific User ID number
url
String
Substring match on the URL clicked.

Responses

Status: 200 - Report content


getEmailSMTPClickSummaryReportUser

This report allows you to query the number of clicks on tracked links during the specified date period. *Note that if you are using LuxSci Secure Marketing v2 to send your email messages, then normal LuxSci click and open reporting is disabled (and you will not see click and open data in this report). The LuxSci Secure Marketing v2 platform his its own click and open tracking and reporting system and you should look in that interface for reports.* See also [API Reporting Basics](/rest-api/reporting.html) and [report header columns in the response](/rest-api/report-responses.html#clicks_count). Dates, for the purposes of narrowing results, refer to the date the link was clicked on.

Access control required to execute this endpoint: User: View Reports


/perl/api/v2/user/{username}/report/email/smtp/clicks_count

Parameters

Path parameters
Name Description
username*
String
Required
Header parameters
Name Description
Cookie
Query parameters
Name Description
after_date
String
DATETIME. Return only matches dated after this date time. Format “YYYY-MM-DD HH:MM:SS” in GMT
before_date
String
DATETIME. Return only matches dated before this date time.
first_row
Integer
(Default value 0). All of the matches are sorted and numbered starting from 0. E.g. if you have 100,000 matches, these are rows 0 through 99,999. If you specify a first_row, then the returned matches will be those rows starting from that row. E.g. without a specification (or if you specify 0), you might get rows 0 through 49,999. In your next request you might specify first_row=50000 to get rows 50000 to 99,999.
from_date
String
DATETIME. Return only matches dated on or after this date time.
matches
Integer
(Default value 50000). You can set matches to any value from 0 to 50000. This sets the maximum number of matches that will be returned in response to your request. Note that if the response size starts to exceed 50MB, then the response can still include fewer than your “matches” number, to keep the response size reasonable. If you specify “0” here, then no matches will be returned; however, you will still get the information on the number of matches that there were. For asynchronous reports (ones where a destination is specified), the matches parameter is not limited to 50000, but it still defaults to 50000 if not specified. If you expect a larger number of rows, then you must explicitly approve the maximum size of the result set by setting matches appropriately. This helps prevent accidental queries that produce very larger result sets.
through_date
String
DATETIME. Return only matches dated before or on this date time.
destination
String
For reporting requests. Specifying a destination makes the report "asynchronous." This means that a background job will be created to run the report and upload the final CSV file to the requested destination. The API request to start the report will return immediately with a background "job number" and the filename that will be uploaded. The supported value of "destination" is currently only "sftp" for a Secure FTP upload over SSH (as opposed to ftps, which would be a Secure FTP upload over SSL). When "destination" is specified, additional destination parameters are also required. Note that for SFTP uploads, there is a 15-minute upload timeout -- uploads that take longer (e.g., due to slow SFTP servers) will be aborted. WARNING: Multiple concurrent large asynchronous report requests will impact your database performance: reports will take longer to generate and your LuxSci services will experience degraded/slower performance.
destination_directory
String
For asynchronous reporting requests. This optional parameter will be the subdirectory to change to on the SFTP server before uploading the report CSV file. Technically speaking, this will be the argument provided to the SFTP "chdir" command.
destination_hostname
String
For asynchronous reporting requests. This will be the hostname of the SFTP server to which the report CSV file should be uploaded.
destination_password
String
For asynchronous reporting requests. This will be the password to be used for the login to the SFTP server to which the report CSV file should be uploaded.
destination_username
String
For asynchronous reporting requests. This will be the username to be used for the login to the SFTP server to which the report CSV file should be uploaded.
filter1
String
Control when a summary report returns values (for use with automated reports). See https://luxsci.com/rest-api/reporting.html#filters
filter2
String
Control when a summary report returns values (for use with automated reports). See https://luxsci.com/rest-api/reporting.html#filters
filter3
String
Control when a summary report returns values (for use with automated reports). See https://luxsci.com/rest-api/reporting.html#filters
from
String
Case-insensitive substring search of the message “From” email address
header1
String
Case-insensitive name of the custom email header field to match against in the “header 1” column. I.e., if you were matching against “X-My-Header” and saving this in header 1, you would enter “X-My-Header” as the value here.

NOTE: Data is only stored in the customer header capturing fields/columns if you have explicitly enabled this feature in the “Account Administration > Email” area of the LuxSci user interface.
header1_operator
String
If this is present and one of the following 4 values, then the query will only return messages that included “header1” when “header1” was being tracked, and which also satisfy the follow the criteria:
  • is --- The value of the email header named “header1” in the send email must have been exactly the same as header1_value
  • not – The value of the email header named “header1” in the send email must not be exactly the same as header1_value
  • like – The value of the email header named “header1” in the send email must contain (case insensitive) the value in header1_value
  • notlike – The value of the email header named “header1” in the send email must not contain (case insensitive) the value in header1_value
I.e., if you configured your account to capture the value of the header “X-My-Header” and saving this in “header column 1” and an email was sent with the header “X-My-Header: gh6577hh-abc”. This would have been stored in the database. You could then find this message by passing to this API function:
  • header1 = “X-My-Header”
  • header1_operator = “is”
  • header1_value = “gh6577hh-abc”
Or by passing:
  • header1 = “X-My-Header”,/li>
  • header1_operator = “like”
  • header1_value = “abc”
header1_value
String
Text used with “header1_operator” for matching the value of the email header specified in the “header1” parameter in the original sent message.
header2
String
Like “header1” but applies to searching the header 2 column.
header2_operator
String
Like “header1_operator” but applies to searching the header 2 column.
header2_value
String
Like “header1_value” but applies to searching the header 2 column.
header3
String
Like “header1” but applies to searching the header 3 column.
header3_operator
String
Like “header1_operator” but applies to searching the header 3 column.
header3_value
String
Like “header1_value” but applies to searching the header 2 column.
subject
String
Case-insensitive substring search of the message subject (in UTF8).
tracked_headers
String
If true and this report is for messages sent vis SMTP, then the results will include the six additional fields (header1, header2, header3, header1_value, header2_value, header3_value) which are used to track custom email message header data.
template_id
Integer
Optional template ID to select results only for those messages sent using the specified template. A value of 0 selects all.
user_id
String
Restrict the report to the user with this specific User ID number
url
String
Substring match on the URL clicked.

Responses

Status: 200 - Report content


getEmailSMTPDeliveryStatusReportUser

This report allows you to see how each SMTP message sent by `username` was sent to each recipient and what the delivery status is for each of these recipients. Note that delivery status changes over time as messages progress to the recipient’s servers and as bounce messages are sent back and processed. As the delivery status changes, the `last_update` date is also updated. See also [API Reporting Basics](/rest-api/reporting.html) and [report header columns in the response](/rest-api/report-responses.html#delivery). Dates, for the purposes of narrowing results, refer to the *date the row was last updated*. This corresponds to the last_update output field. This can be changed to the date the message was sent using the "sent_date" parameter or the date of the last delivery status update using the "delivery_date" parameter.

Access control required to execute this endpoint: User: View Reports


/perl/api/v2/user/{username}/report/email/smtp/delivery

Parameters

Path parameters
Name Description
username*
String
Required
Header parameters
Name Description
Cookie
Query parameters
Name Description
after_date
String
DATETIME. Return only matches dated after this date time. Format “YYYY-MM-DD HH:MM:SS” in GMT
before_date
String
DATETIME. Return only matches dated before this date time.
first_row
Integer
(Default value 0). All of the matches are sorted and numbered starting from 0. E.g. if you have 100,000 matches, these are rows 0 through 99,999. If you specify a first_row, then the returned matches will be those rows starting from that row. E.g. without a specification (or if you specify 0), you might get rows 0 through 49,999. In your next request you might specify first_row=50000 to get rows 50000 to 99,999.
from_date
String
DATETIME. Return only matches dated on or after this date time.
matches
Integer
(Default value 50000). You can set matches to any value from 0 to 50000. This sets the maximum number of matches that will be returned in response to your request. Note that if the response size starts to exceed 50MB, then the response can still include fewer than your “matches” number, to keep the response size reasonable. If you specify “0” here, then no matches will be returned; however, you will still get the information on the number of matches that there were. For asynchronous reports (ones where a destination is specified), the matches parameter is not limited to 50000, but it still defaults to 50000 if not specified. If you expect a larger number of rows, then you must explicitly approve the maximum size of the result set by setting matches appropriately. This helps prevent accidental queries that produce very larger result sets.
through_date
String
DATETIME. Return only matches dated before or on this date time.
destination
String
For reporting requests. Specifying a destination makes the report "asynchronous." This means that a background job will be created to run the report and upload the final CSV file to the requested destination. The API request to start the report will return immediately with a background "job number" and the filename that will be uploaded. The supported value of "destination" is currently only "sftp" for a Secure FTP upload over SSH (as opposed to ftps, which would be a Secure FTP upload over SSL). When "destination" is specified, additional destination parameters are also required. Note that for SFTP uploads, there is a 15-minute upload timeout -- uploads that take longer (e.g., due to slow SFTP servers) will be aborted. WARNING: Multiple concurrent large asynchronous report requests will impact your database performance: reports will take longer to generate and your LuxSci services will experience degraded/slower performance.
destination_directory
String
For asynchronous reporting requests. This optional parameter will be the subdirectory to change to on the SFTP server before uploading the report CSV file. Technically speaking, this will be the argument provided to the SFTP "chdir" command.
destination_hostname
String
For asynchronous reporting requests. This will be the hostname of the SFTP server to which the report CSV file should be uploaded.
destination_password
String
For asynchronous reporting requests. This will be the password to be used for the login to the SFTP server to which the report CSV file should be uploaded.
destination_username
String
For asynchronous reporting requests. This will be the username to be used for the login to the SFTP server to which the report CSV file should be uploaded.
clicked
Integer
Integer. If specified, the results are restricted as follows:
clicked < 0 – select messages where URL click tracking was not enabled.
clicked = 0 – select messages where URL click tracking was enabled, but where there have as yet been no clicks on any clinks in the messages.
clicked > 0 – select messages where URL click tracking was enabled and where there have been N or more clicks on links in the same message to the same recipient. N, in this case, is the number that you have specified as the value of the “clicked” parameter. I.e., using a value of “1” matches all messages that have had a link clicked on.
from
String
String. Case-insensitive substring search of the message “From” email Address
ip
String
String. Case-insensitive substring search of the sender IP address (for SMTP reports only).
header1
String
Case-insensitive name of the custom email header field to match against in the “header 1” column. I.e., if you were matching against “X-My-Header” and saving this in header 1, you would enter “X-My-Header” as the value here.

NOTE: Data is only stored in the customer header capturing fields/columns if you have explicitly enabled this feature in the “Account Administration > Email” area of the LuxSci user interface.
header1_operator
String
If this is present and one of the following 4 values, then the query will only return messages that included “header1” when “header1” was being tracked, and which also satisfy the follow the criteria:
  • is --- The value of the email header named “header1” in the send email must have been exactly the same as header1_value
  • not – The value of the email header named “header1” in the send email must not be exactly the same as header1_value
  • like – The value of the email header named “header1” in the send email must contain (case insensitive) the value in header1_value
  • notlike – The value of the email header named “header1” in the send email must not contain (case insensitive) the value in header1_value
I.e., if you configured your account to capture the value of the header “X-My-Header” and saving this in “header column 1” and an email was sent with the header “X-My-Header: gh6577hh-abc”. This would have been stored in the database. You could then find this message by passing to this API function:
  • header1 = “X-My-Header”
  • header1_operator = “is”
  • header1_value = “gh6577hh-abc”
Or by passing:
  • header1 = “X-My-Header”,/li>
  • header1_operator = “like”
  • header1_value = “abc”
header1_value
String
Text used with “header1_operator” for matching the value of the email header specified in the “header1” parameter in the original sent message.
header2
String
Like “header1” but applies to searching the header 2 column.
header2_operator
String
Like “header1_operator” but applies to searching the header 2 column.
header2_value
String
Like “header1_value” but applies to searching the header 2 column.
header3
String
Like “header1” but applies to searching the header 3 column.
header3_operator
String
Like “header1_operator” but applies to searching the header 3 column.
header3_value
String
Like “header1_value” but applies to searching the header 2 column.
opened
Integer
Integer. If specified, the results are restricted as follows:
opened < 0 – select messages where open tracking was not enabled.
opened = 0 – select messages where open tracking was enabled, but which have not yet been opened.
opened > 0 – select messages where open tracking was enabled and which have been opened at least N times. N, in this case, is the number that you have specified as the value of the “opened” parameter. I.e., using a value of “1” matches all messages that have been opened.
secureline
String
Enum. Value:
u – Message to this recipient did not use SecureLine (or Opt Out was used)
e – Message did use SecureLine
-2 – SecureLine was not used due to Opt Out being selected
-1 – SecureLine usage not recorded for some reason
1 – SecureLine:PGP was used
2 – SecureLine:S/MIME was used
3 – SecureLine:Escrow was used
4 – SecureLine:TLS was used
sendmail_id
String
String. Return only the messages with the specified sendmail_id
sendmail_ids
String
Comma-delimited list of up to 100 sendmail ids. Returns any matching messages.
sent_date
Integer
If set to true (i.e., 1), the email message sent date will be used for date/time selections, instead of the date of the last update of the row.
state
String
Optionally, match only messages with specific delivery states. This is a comma-delimited list of one or more states to match. The possible states include:
delivered - Successful delivery.
perm_fail - Message immediately rejected by recipient servers.
ba_hard_fail - Post-delivery hard bounce.
ba_soft_fail - Post-delivery soft bounce.
temp_fail - Message still queued after 1+ temporary delivery failures.
queued - Message queued -- includes the "temp_fail" state.
lost - Message delivery status unknown.
any_hard_fail - "perm_fail" or "ba_hard_fail".
failed - "perm_fail" or "ba_hard_fail" or "ba_soft_fail".
not_queued - "delivered" or "lost" or any of the "failed" states.
state_detail
String
Optionally, match only messages where the "state_detail" delivery status description contains the specified text (case insensitive).
delivery_date
Integer
If set to true (i.e., 1), the email message last delivery status updated date will be used for date/time selections, instead of the date of the last update of the row.
spam
Integer
Enum. Value:
0 – Message was not marked as spam by a recipient and returned in a Feed Back Loop.
1 – Message was marked as spam by a recipient and returned in a Feed Back Loop
unsubscribed
Integer
Enum. Value: 0 – The recipient did not unsubscribe based on this email message. 1 – The recipient did unsubscribe based on this email message.
smtp_code
String
String. 1-3 characters. Substring match to the beginning of the smtp_code field. E.g., 5 matches all codes starting with 5.
tls
Integer
Enum. Value:
0 – TLS was NOT used in the successful delivery of this message to the recipient server
1 – TLS was used in the successful delivery of this message to the recipient server.
tracked_headers
String
If true and this report is for messages sent vis SMTP, then the results will include the six additional fields (header1, header2, header3, header1_value, header2_value, header3_value) which are used to track custom email message header data.
template_id
Integer
Optional template ID to select results only for those messages sent using the specified template. A value of 0 selects all.
to
String
Case-insensitive substring search of all recipient email addresses.
user_id
Integer
Integer. Restrict the report to the user with this specific User ID number

Responses

Status: 200 - Report content


getEmailSMTPDeliveryStatusSummaryReportUser

This report allows you to retrieve a summary of the delivery status (and other statistics) across all messages in a given time range. See also [API Reporting Basics](/rest-api/reporting.html) and [report header columns in the response](/rest-api/report-responses.html#delivery_count). Dates, for the purposes of narrowing results, refer to the *date the message delivery status was last updated*. This can be changed to the date the message was sent using the "sent_date" parameter.

Access control required to execute this endpoint: User: View Reports


/perl/api/v2/user/{username}/report/email/smtp/delivery_count

Parameters

Path parameters
Name Description
username*
String
Required
Header parameters
Name Description
Cookie
Query parameters
Name Description
after_date
String
DATETIME. Return only matches dated after this date time. Format “YYYY-MM-DD HH:MM:SS” in GMT
before_date
String
DATETIME. Return only matches dated before this date time.
first_row
Integer
(Default value 0). All of the matches are sorted and numbered starting from 0. E.g. if you have 100,000 matches, these are rows 0 through 99,999. If you specify a first_row, then the returned matches will be those rows starting from that row. E.g. without a specification (or if you specify 0), you might get rows 0 through 49,999. In your next request you might specify first_row=50000 to get rows 50000 to 99,999.
from_date
String
DATETIME. Return only matches dated on or after this date time.
matches
Integer
(Default value 50000). You can set matches to any value from 0 to 50000. This sets the maximum number of matches that will be returned in response to your request. Note that if the response size starts to exceed 50MB, then the response can still include fewer than your “matches” number, to keep the response size reasonable. If you specify “0” here, then no matches will be returned; however, you will still get the information on the number of matches that there were. For asynchronous reports (ones where a destination is specified), the matches parameter is not limited to 50000, but it still defaults to 50000 if not specified. If you expect a larger number of rows, then you must explicitly approve the maximum size of the result set by setting matches appropriately. This helps prevent accidental queries that produce very larger result sets.
through_date
String
DATETIME. Return only matches dated before or on this date time.
destination
String
For reporting requests. Specifying a destination makes the report "asynchronous." This means that a background job will be created to run the report and upload the final CSV file to the requested destination. The API request to start the report will return immediately with a background "job number" and the filename that will be uploaded. The supported value of "destination" is currently only "sftp" for a Secure FTP upload over SSH (as opposed to ftps, which would be a Secure FTP upload over SSL). When "destination" is specified, additional destination parameters are also required. Note that for SFTP uploads, there is a 15-minute upload timeout -- uploads that take longer (e.g., due to slow SFTP servers) will be aborted. WARNING: Multiple concurrent large asynchronous report requests will impact your database performance: reports will take longer to generate and your LuxSci services will experience degraded/slower performance.
destination_directory
String
For asynchronous reporting requests. This optional parameter will be the subdirectory to change to on the SFTP server before uploading the report CSV file. Technically speaking, this will be the argument provided to the SFTP "chdir" command.
destination_hostname
String
For asynchronous reporting requests. This will be the hostname of the SFTP server to which the report CSV file should be uploaded.
destination_password
String
For asynchronous reporting requests. This will be the password to be used for the login to the SFTP server to which the report CSV file should be uploaded.
destination_username
String
For asynchronous reporting requests. This will be the username to be used for the login to the SFTP server to which the report CSV file should be uploaded.
filter1
String
Control when a summary report returns values (for use with automated reports). See https://luxsci.com/rest-api/reporting.html#filters
filter2
String
Control when a summary report returns values (for use with automated reports). See https://luxsci.com/rest-api/reporting.html#filters
filter3
String
Control when a summary report returns values (for use with automated reports). See https://luxsci.com/rest-api/reporting.html#filters
clicked
Integer
Integer. If specified, the results are restricted as follows:
clicked < 0 – select messages where URL click tracking was not enabled.
clicked = 0 – select messages where URL click tracking was enabled, but where there have as yet been no clicks on any clinks in the messages.
clicked > 0 – select messages where URL click tracking was enabled and where there have been N or more clicks on links in the same message to the same recipient. N, in this case, is the number that you have specified as the value of the “clicked” parameter. I.e., using a value of “1” matches all messages that have had a link clicked on.
from
String
String. Case-insensitive substring search of the message “From” email Address
ip
String
String. Case-insensitive substring search of the sender IP address (for SMTP reports only).
header1
String
Case-insensitive name of the custom email header field to match against in the “header 1” column. I.e., if you were matching against “X-My-Header” and saving this in header 1, you would enter “X-My-Header” as the value here.

NOTE: Data is only stored in the customer header capturing fields/columns if you have explicitly enabled this feature in the “Account Administration > Email” area of the LuxSci user interface.
header1_operator
String
If this is present and one of the following 4 values, then the query will only return messages that included “header1” when “header1” was being tracked, and which also satisfy the follow the criteria:
  • is --- The value of the email header named “header1” in the send email must have been exactly the same as header1_value
  • not – The value of the email header named “header1” in the send email must not be exactly the same as header1_value
  • like – The value of the email header named “header1” in the send email must contain (case insensitive) the value in header1_value
  • notlike – The value of the email header named “header1” in the send email must not contain (case insensitive) the value in header1_value
I.e., if you configured your account to capture the value of the header “X-My-Header” and saving this in “header column 1” and an email was sent with the header “X-My-Header: gh6577hh-abc”. This would have been stored in the database. You could then find this message by passing to this API function:
  • header1 = “X-My-Header”
  • header1_operator = “is”
  • header1_value = “gh6577hh-abc”
Or by passing:
  • header1 = “X-My-Header”,/li>
  • header1_operator = “like”
  • header1_value = “abc”
header1_value
String
Text used with “header1_operator” for matching the value of the email header specified in the “header1” parameter in the original sent message.
header2
String
Like “header1” but applies to searching the header 2 column.
header2_operator
String
Like “header1_operator” but applies to searching the header 2 column.
header2_value
String
Like “header1_value” but applies to searching the header 2 column.
header3
String
Like “header1” but applies to searching the header 3 column.
header3_operator
String
Like “header1_operator” but applies to searching the header 3 column.
header3_value
String
Like “header1_value” but applies to searching the header 2 column.
opened
Integer
Integer. If specified, the results are restricted as follows:
opened < 0 – select messages where open tracking was not enabled.
opened = 0 – select messages where open tracking was enabled, but which have not yet been opened.
opened > 0 – select messages where open tracking was enabled and which have been opened at least N times. N, in this case, is the number that you have specified as the value of the “opened” parameter. I.e., using a value of “1” matches all messages that have been opened.
secureline
String
Enum. Value:
u – Message to this recipient did not use SecureLine (or Opt Out was used)
e – Message did use SecureLine
-2 – SecureLine was not used due to Opt Out being selected
-1 – SecureLine usage not recorded for some reason
1 – SecureLine:PGP was used
2 – SecureLine:S/MIME was used
3 – SecureLine:Escrow was used
4 – SecureLine:TLS was used
sent_date
Integer
If set to true (i.e., 1), the email message sent date will be used for date/time selections, instead of the date of the last update of the delivery status.
queue_age_sec
Integer
If provided, then the "queued" and "pct_queued" results will reflect only those messages that have been not delivered for at least this number of seconds. I.e., use this to eliminate very recently sent messages from your analysis or how mange messages were queued and not yet delivered.
unsubscribed
Integer
Enum. Value: 0 – The recipient did not unsubscribe based on this email message. 1 – The recipient did unsubscribe based on this email message.
tls
Integer
Enum. Value:
0 – TLS was NOT used in the successful delivery of this message to the recipient server
1 – TLS was used in the successful delivery of this message to the recipient server.
tracked_headers
String
If true and this report is for messages sent vis SMTP, then the results will include the six additional fields (header1, header2, header3, header1_value, header2_value, header3_value) which are used to track custom email message header data.
template_id
Integer
Optional template ID to select results only for those messages sent using the specified template. A value of 0 selects all.
to
String
Case-insensitive substring search of all recipient email addresses.

Responses

Status: 200 -


getEmailSMTPLoginFailureReportUser

This report allows to see all SMTP login failures to the user login `username`, as well as sending errors that resulted from our servers explicitly rejecting your request to send an email message for one reason or another. See also [API Reporting Basics](/rest-api/reporting.html) and [report header columns in the response](/rest-api/report-responses.html#smtp_login_fail).

Access control required to execute this endpoint: User: View Reports


/perl/api/v2/user/{username}/report/login_fail/smtp

Parameters

Path parameters
Name Description
username*
String
Required
Header parameters
Name Description
Cookie
Query parameters
Name Description
after_date
String
DATETIME. Return only matches dated after this date time. Format “YYYY-MM-DD HH:MM:SS” in GMT
before_date
String
DATETIME. Return only matches dated before this date time.
first_row
Integer
(Default value 0). All of the matches are sorted and numbered starting from 0. E.g. if you have 100,000 matches, these are rows 0 through 99,999. If you specify a first_row, then the returned matches will be those rows starting from that row. E.g. without a specification (or if you specify 0), you might get rows 0 through 49,999. In your next request you might specify first_row=50000 to get rows 50000 to 99,999.
from_date
String
DATETIME. Return only matches dated on or after this date time.
matches
Integer
(Default value 50000). You can set matches to any value from 0 to 50000. This sets the maximum number of matches that will be returned in response to your request. Note that if the response size starts to exceed 50MB, then the response can still include fewer than your “matches” number, to keep the response size reasonable. If you specify “0” here, then no matches will be returned; however, you will still get the information on the number of matches that there were. For asynchronous reports (ones where a destination is specified), the matches parameter is not limited to 50000, but it still defaults to 50000 if not specified. If you expect a larger number of rows, then you must explicitly approve the maximum size of the result set by setting matches appropriately. This helps prevent accidental queries that produce very larger result sets.
through_date
String
DATETIME. Return only matches dated before or on this date time.
destination
String
For reporting requests. Specifying a destination makes the report "asynchronous." This means that a background job will be created to run the report and upload the final CSV file to the requested destination. The API request to start the report will return immediately with a background "job number" and the filename that will be uploaded. The supported value of "destination" is currently only "sftp" for a Secure FTP upload over SSH (as opposed to ftps, which would be a Secure FTP upload over SSL). When "destination" is specified, additional destination parameters are also required. Note that for SFTP uploads, there is a 15-minute upload timeout -- uploads that take longer (e.g., due to slow SFTP servers) will be aborted. WARNING: Multiple concurrent large asynchronous report requests will impact your database performance: reports will take longer to generate and your LuxSci services will experience degraded/slower performance.
destination_directory
String
For asynchronous reporting requests. This optional parameter will be the subdirectory to change to on the SFTP server before uploading the report CSV file. Technically speaking, this will be the argument provided to the SFTP "chdir" command.
destination_hostname
String
For asynchronous reporting requests. This will be the hostname of the SFTP server to which the report CSV file should be uploaded.
destination_password
String
For asynchronous reporting requests. This will be the password to be used for the login to the SFTP server to which the report CSV file should be uploaded.
destination_username
String
For asynchronous reporting requests. This will be the username to be used for the login to the SFTP server to which the report CSV file should be uploaded.
ip
String
String. Case-insensitive substring search of the message “IP Address” if the email program or device that made the connection.
Reason
String
String Case-insensitive substring search of the login failure / reason data.

Responses

Status: 200 - Report content


getEmailSMTPOpenReportUser

This report allows you to query on the “opened” events (or lack thereof) for email messages sent via SMTP by `username` that have email open tracking enabled. Using this command, it is possible to get a report of all individual opens for messages or to get reports about messages that have not yet been opened or for which open tracking was not enabled. See the query parameters for more detail. *Note: if you are using LuxSci Secure Marketing v2 to send your email messages, then normal LuxSci click and open reporting is disabled (and you will not see click and open data in this report). The LuxSci Secure Marketing v2 platform his its own click and open tracking and reporting system and you should look in that interface for reports.* See also [API Reporting Basics](/rest-api/reporting.html) and [report header columns in the response](/rest-api/report-responses.html#open). Dates, for the purposes of narrowing results, refer to the date the message was sent. This corresponds to the “date_sent” output field. However, if you set the “open_date” input parameter to true, then the “open_date” field will be used for date selections.

Access control required to execute this endpoint: User: View Reports


/perl/api/v2/user/{username}/report/email/smtp/opens

Parameters

Path parameters
Name Description
username*
String
Required
Header parameters
Name Description
Cookie
Query parameters
Name Description
after_date
String
DATETIME. Return only matches dated after this date time. Format “YYYY-MM-DD HH:MM:SS” in GMT
before_date
String
DATETIME. Return only matches dated before this date time.
first_row
Integer
(Default value 0). All of the matches are sorted and numbered starting from 0. E.g. if you have 100,000 matches, these are rows 0 through 99,999. If you specify a first_row, then the returned matches will be those rows starting from that row. E.g. without a specification (or if you specify 0), you might get rows 0 through 49,999. In your next request you might specify first_row=50000 to get rows 50000 to 99,999.
from_date
String
DATETIME. Return only matches dated on or after this date time.
matches
Integer
(Default value 50000). You can set matches to any value from 0 to 50000. This sets the maximum number of matches that will be returned in response to your request. Note that if the response size starts to exceed 50MB, then the response can still include fewer than your “matches” number, to keep the response size reasonable. If you specify “0” here, then no matches will be returned; however, you will still get the information on the number of matches that there were. For asynchronous reports (ones where a destination is specified), the matches parameter is not limited to 50000, but it still defaults to 50000 if not specified. If you expect a larger number of rows, then you must explicitly approve the maximum size of the result set by setting matches appropriately. This helps prevent accidental queries that produce very larger result sets.
through_date
String
DATETIME. Return only matches dated before or on this date time.
destination
String
For reporting requests. Specifying a destination makes the report "asynchronous." This means that a background job will be created to run the report and upload the final CSV file to the requested destination. The API request to start the report will return immediately with a background "job number" and the filename that will be uploaded. The supported value of "destination" is currently only "sftp" for a Secure FTP upload over SSH (as opposed to ftps, which would be a Secure FTP upload over SSL). When "destination" is specified, additional destination parameters are also required. Note that for SFTP uploads, there is a 15-minute upload timeout -- uploads that take longer (e.g., due to slow SFTP servers) will be aborted. WARNING: Multiple concurrent large asynchronous report requests will impact your database performance: reports will take longer to generate and your LuxSci services will experience degraded/slower performance.
destination_directory
String
For asynchronous reporting requests. This optional parameter will be the subdirectory to change to on the SFTP server before uploading the report CSV file. Technically speaking, this will be the argument provided to the SFTP "chdir" command.
destination_hostname
String
For asynchronous reporting requests. This will be the hostname of the SFTP server to which the report CSV file should be uploaded.
destination_password
String
For asynchronous reporting requests. This will be the password to be used for the login to the SFTP server to which the report CSV file should be uploaded.
destination_username
String
For asynchronous reporting requests. This will be the username to be used for the login to the SFTP server to which the report CSV file should be uploaded.
from
String
Case-insensitive substring search of the message “From” email address
header1
String
Case-insensitive name of the custom email header field to match against in the “header 1” column. I.e., if you were matching against “X-My-Header” and saving this in header 1, you would enter “X-My-Header” as the value here.

NOTE: Data is only stored in the customer header capturing fields/columns if you have explicitly enabled this feature in the “Account Administration > Email” area of the LuxSci user interface.
header1_operator
String
If this is present and one of the following 4 values, then the query will only return messages that included “header1” when “header1” was being tracked, and which also satisfy the follow the criteria:
  • is --- The value of the email header named “header1” in the send email must have been exactly the same as header1_value
  • not – The value of the email header named “header1” in the send email must not be exactly the same as header1_value
  • like – The value of the email header named “header1” in the send email must contain (case insensitive) the value in header1_value
  • notlike – The value of the email header named “header1” in the send email must not contain (case insensitive) the value in header1_value
I.e., if you configured your account to capture the value of the header “X-My-Header” and saving this in “header column 1” and an email was sent with the header “X-My-Header: gh6577hh-abc”. This would have been stored in the database. You could then find this message by passing to this API function:
  • header1 = “X-My-Header”
  • header1_operator = “is”
  • header1_value = “gh6577hh-abc”
Or by passing:
  • header1 = “X-My-Header”,/li>
  • header1_operator = “like”
  • header1_value = “abc”
header1_value
String
Text used with “header1_operator” for matching the value of the email header specified in the “header1” parameter in the original sent message.
header2
String
Like “header1” but applies to searching the header 2 column.
header2_operator
String
Like “header1_operator” but applies to searching the header 2 column.
header2_value
String
Like “header1_value” but applies to searching the header 2 column.
header3
String
Like “header1” but applies to searching the header 3 column.
header3_operator
String
Like “header1_operator” but applies to searching the header 3 column.
header3_value
String
Like “header1_value” but applies to searching the header 2 column.
opened
Integer
If specified, the results are restricted as follows:
opened < 0 – select messages where open tracking was not enabled.
opened = 0 – select messages where open tracking was enabled, but which have not yet been opened.
opened > 0 – select messages where open tracking was enabled and which have been opened at least once. When opened is positive, you will get one row back for each open; so, you can get multiple rows per message.

If you do not specify a value for “opened”, a value of “1” will be assumed.
open_date
Boolean
If true, the ”open_date” field will be used for all date selections. If false or not specified, the sent date (“date_sent”) will be used.
sendmail_id
String
Return only the messages with the specified sendmail_id.
sendmail_ids
String
Comma-delimited list of up to 100 sendmail ids. Returns any matching messages.
status
String
Values:
delivered – Accepted by the recipient’s email servers and presumed delivered. If bounce processing is enabled, then this status could change later to ba_soft_fail or ba_hard_fail.
perm_fail – Messages that have permanently failed to be delivered to the recipient’s servers. If bounce processing is on, this status could change shortly to ba_soft_fail, depending on the nature of the failure message.
lost – Messages where the tracking was lost and it is unclear if it was delivered or lost from the queue.
queued – Message is in the email server queue still waiting to be delivered to the recipient.
not_queued -- all statuses except "queued".
ba_soft_fail – Soft failure bounces received (when talking to the recipient’s servers or after successful delivery to the recipient’s servers).
ba_hard_fail – Hard failure bounces received after successful delivery to the recipient’s servers,
any_hard_fail – Results for ba_hard_fail OR perm_fail. I.e., all hard/permanent failures.
subject
String
Case-insensitive substring search of the message subject (in UTF8).
to
String
Case-insensitive substring search of all recipient email addresses.
tracked_headers
String
If true and this report is for messages sent vis SMTP, then the results will include the six additional fields (header1, header2, header3, header1_value, header2_value, header3_value) which are used to track custom email message header data.
template_id
Integer
Optional template ID to select results only for those messages sent using the specified template. A value of 0 selects all.

Responses

Status: 200 - Report content


getEmailSMTPOpenSummaryReportUser

This report allows returns the number of opens that happened in the selected time period. See also [API Reporting Basics](/rest-api/reporting.html) and [report header columns in the response](/rest-api/report-responses.html#opens_count). *Note: if you are using LuxSci Secure Marketing v2 to send your email messages, then normal LuxSci click and open reporting is disabled (and you will not see click and open data in this report). The LuxSci Secure Marketing v2 platform his its own click and open tracking and reporting system and you should look in that interface for reports.* Dates, for the purposes of narrowing results, refer to the date the message was opened.

Access control required to execute this endpoint: User: View Reports


/perl/api/v2/user/{username}/report/email/smtp/opens_count

Parameters

Path parameters
Name Description
username*
String
Required
Header parameters
Name Description
Cookie
Query parameters
Name Description
after_date
String
DATETIME. Return only matches dated after this date time. Format “YYYY-MM-DD HH:MM:SS” in GMT
before_date
String
DATETIME. Return only matches dated before this date time.
first_row
Integer
(Default value 0). All of the matches are sorted and numbered starting from 0. E.g. if you have 100,000 matches, these are rows 0 through 99,999. If you specify a first_row, then the returned matches will be those rows starting from that row. E.g. without a specification (or if you specify 0), you might get rows 0 through 49,999. In your next request you might specify first_row=50000 to get rows 50000 to 99,999.
from_date
String
DATETIME. Return only matches dated on or after this date time.
matches
Integer
(Default value 50000). You can set matches to any value from 0 to 50000. This sets the maximum number of matches that will be returned in response to your request. Note that if the response size starts to exceed 50MB, then the response can still include fewer than your “matches” number, to keep the response size reasonable. If you specify “0” here, then no matches will be returned; however, you will still get the information on the number of matches that there were. For asynchronous reports (ones where a destination is specified), the matches parameter is not limited to 50000, but it still defaults to 50000 if not specified. If you expect a larger number of rows, then you must explicitly approve the maximum size of the result set by setting matches appropriately. This helps prevent accidental queries that produce very larger result sets.
through_date
String
DATETIME. Return only matches dated before or on this date time.
destination
String
For reporting requests. Specifying a destination makes the report "asynchronous." This means that a background job will be created to run the report and upload the final CSV file to the requested destination. The API request to start the report will return immediately with a background "job number" and the filename that will be uploaded. The supported value of "destination" is currently only "sftp" for a Secure FTP upload over SSH (as opposed to ftps, which would be a Secure FTP upload over SSL). When "destination" is specified, additional destination parameters are also required. Note that for SFTP uploads, there is a 15-minute upload timeout -- uploads that take longer (e.g., due to slow SFTP servers) will be aborted. WARNING: Multiple concurrent large asynchronous report requests will impact your database performance: reports will take longer to generate and your LuxSci services will experience degraded/slower performance.
destination_directory
String
For asynchronous reporting requests. This optional parameter will be the subdirectory to change to on the SFTP server before uploading the report CSV file. Technically speaking, this will be the argument provided to the SFTP "chdir" command.
destination_hostname
String
For asynchronous reporting requests. This will be the hostname of the SFTP server to which the report CSV file should be uploaded.
destination_password
String
For asynchronous reporting requests. This will be the password to be used for the login to the SFTP server to which the report CSV file should be uploaded.
destination_username
String
For asynchronous reporting requests. This will be the username to be used for the login to the SFTP server to which the report CSV file should be uploaded.
filter1
String
Control when a summary report returns values (for use with automated reports). See https://luxsci.com/rest-api/reporting.html#filters
filter2
String
Control when a summary report returns values (for use with automated reports). See https://luxsci.com/rest-api/reporting.html#filters
filter3
String
Control when a summary report returns values (for use with automated reports). See https://luxsci.com/rest-api/reporting.html#filters
from
String
Case-insensitive substring search of the message “From” email address
header1
String
Case-insensitive name of the custom email header field to match against in the “header 1” column. I.e., if you were matching against “X-My-Header” and saving this in header 1, you would enter “X-My-Header” as the value here.

NOTE: Data is only stored in the customer header capturing fields/columns if you have explicitly enabled this feature in the “Account Administration > Email” area of the LuxSci user interface.
header1_operator
String
If this is present and one of the following 4 values, then the query will only return messages that included “header1” when “header1” was being tracked, and which also satisfy the follow the criteria:
  • is --- The value of the email header named “header1” in the send email must have been exactly the same as header1_value
  • not – The value of the email header named “header1” in the send email must not be exactly the same as header1_value
  • like – The value of the email header named “header1” in the send email must contain (case insensitive) the value in header1_value
  • notlike – The value of the email header named “header1” in the send email must not contain (case insensitive) the value in header1_value
I.e., if you configured your account to capture the value of the header “X-My-Header” and saving this in “header column 1” and an email was sent with the header “X-My-Header: gh6577hh-abc”. This would have been stored in the database. You could then find this message by passing to this API function:
  • header1 = “X-My-Header”
  • header1_operator = “is”
  • header1_value = “gh6577hh-abc”
Or by passing:
  • header1 = “X-My-Header”,/li>
  • header1_operator = “like”
  • header1_value = “abc”
header1_value
String
Text used with “header1_operator” for matching the value of the email header specified in the “header1” parameter in the original sent message.
header2
String
Like “header1” but applies to searching the header 2 column.
header2_operator
String
Like “header1_operator” but applies to searching the header 2 column.
header2_value
String
Like “header1_value” but applies to searching the header 2 column.
header3
String
Like “header1” but applies to searching the header 3 column.
header3_operator
String
Like “header1_operator” but applies to searching the header 3 column.
header3_value
String
Like “header1_value” but applies to searching the header 2 column.
opened
Integer
If specified, the results are restricted as follows:
opened < 0 – select messages where open tracking was not enabled.
opened = 0 – select messages where open tracking was enabled, but which have not yet been opened.
opened > 0 – select messages where open tracking was enabled and which have been opened at least once. When opened is positive, you will get one row back for each open; so, you can get multiple rows per message.

If you do not specify a value for “opened”, a value of “1” will be assumed.
subject
String
Case-insensitive substring search of the message subject (in UTF8).
to
String
Case-insensitive substring search of all recipient email addresses.
tracked_headers
String
If true and this report is for messages sent vis SMTP, then the results will include the six additional fields (header1, header2, header3, header1_value, header2_value, header3_value) which are used to track custom email message header data.
template_id
Integer
Optional template ID to select results only for those messages sent using the specified template. A value of 0 selects all.

Responses

Status: 200 - Report content


getEmailSMTPSentReportUser

Return a list of all email messages sent via SMTP by `username`. See also [API Reporting Basics](/rest-api/reporting.html) and [report header columns in the response.](/rest-api/report-responses.html#sent).

Access control required to execute this endpoint: User: View Reports


/perl/api/v2/user/{username}/report/email/smtp/sent

Parameters

Path parameters
Name Description
username*
String
Required
Header parameters
Name Description
Cookie
Query parameters
Name Description
after_date
String
DATETIME. Return only matches dated after this date time. Format “YYYY-MM-DD HH:MM:SS” in GMT
before_date
String
DATETIME. Return only matches dated before this date time.
first_row
Integer
(Default value 0). All of the matches are sorted and numbered starting from 0. E.g. if you have 100,000 matches, these are rows 0 through 99,999. If you specify a first_row, then the returned matches will be those rows starting from that row. E.g. without a specification (or if you specify 0), you might get rows 0 through 49,999. In your next request you might specify first_row=50000 to get rows 50000 to 99,999.
from_date
String
DATETIME. Return only matches dated on or after this date time.
matches
Integer
(Default value 50000). You can set matches to any value from 0 to 50000. This sets the maximum number of matches that will be returned in response to your request. Note that if the response size starts to exceed 50MB, then the response can still include fewer than your “matches” number, to keep the response size reasonable. If you specify “0” here, then no matches will be returned; however, you will still get the information on the number of matches that there were. For asynchronous reports (ones where a destination is specified), the matches parameter is not limited to 50000, but it still defaults to 50000 if not specified. If you expect a larger number of rows, then you must explicitly approve the maximum size of the result set by setting matches appropriately. This helps prevent accidental queries that produce very larger result sets.
through_date
String
DATETIME. Return only matches dated before or on this date time.
destination
String
For reporting requests. Specifying a destination makes the report "asynchronous." This means that a background job will be created to run the report and upload the final CSV file to the requested destination. The API request to start the report will return immediately with a background "job number" and the filename that will be uploaded. The supported value of "destination" is currently only "sftp" for a Secure FTP upload over SSH (as opposed to ftps, which would be a Secure FTP upload over SSL). When "destination" is specified, additional destination parameters are also required. Note that for SFTP uploads, there is a 15-minute upload timeout -- uploads that take longer (e.g., due to slow SFTP servers) will be aborted. WARNING: Multiple concurrent large asynchronous report requests will impact your database performance: reports will take longer to generate and your LuxSci services will experience degraded/slower performance.
destination_directory
String
For asynchronous reporting requests. This optional parameter will be the subdirectory to change to on the SFTP server before uploading the report CSV file. Technically speaking, this will be the argument provided to the SFTP "chdir" command.
destination_hostname
String
For asynchronous reporting requests. This will be the hostname of the SFTP server to which the report CSV file should be uploaded.
destination_password
String
For asynchronous reporting requests. This will be the password to be used for the login to the SFTP server to which the report CSV file should be uploaded.
destination_username
String
For asynchronous reporting requests. This will be the username to be used for the login to the SFTP server to which the report CSV file should be uploaded.
from
String
Case-insensitive substring search of the message “From” email address
header1
String
Case-insensitive name of the custom email header field to match against in the “header 1” column. I.e., if you were matching against “X-My-Header” and saving this in header 1, you would enter “X-My-Header” as the value here.

NOTE: Data is only stored in the customer header capturing fields/columns if you have explicitly enabled this feature in the “Account Administration > Email” area of the LuxSci user interface.
header1_operator
String
If this is present and one of the following 4 values, then the query will only return messages that included “header1” when “header1” was being tracked, and which also satisfy the follow the criteria:
  • is --- The value of the email header named “header1” in the send email must have been exactly the same as header1_value
  • not – The value of the email header named “header1” in the send email must not be exactly the same as header1_value
  • like – The value of the email header named “header1” in the send email must contain (case insensitive) the value in header1_value
  • notlike – The value of the email header named “header1” in the send email must not contain (case insensitive) the value in header1_value
I.e., if you configured your account to capture the value of the header “X-My-Header” and saving this in “header column 1” and an email was sent with the header “X-My-Header: gh6577hh-abc”. This would have been stored in the database. You could then find this message by passing to this API function:
  • header1 = “X-My-Header”
  • header1_operator = “is”
  • header1_value = “gh6577hh-abc”
Or by passing:
  • header1 = “X-My-Header”,/li>
  • header1_operator = “like”
  • header1_value = “abc”
header1_value
String
Text used with “header1_operator” for matching the value of the email header specified in the “header1” parameter in the original sent message.
header2
String
Like “header1” but applies to searching the header 2 column.
header2_operator
String
Like “header1_operator” but applies to searching the header 2 column.
header2_value
String
Like “header1_value” but applies to searching the header 2 column.
header3
String
Like “header1” but applies to searching the header 3 column.
header3_operator
String
Like “header1_operator” but applies to searching the header 3 column.
header3_value
String
Like “header1_value” but applies to searching the header 2 column.
ip
String
Case-insensitive substring search of the sender IP address (for SMTP reports only).
opt_out
String
Value:
0 – SecureLine Opt Out not used
-1 – SecureLine Opt Out use not recorded for some reason
1 – SecureLine Opt Out
secureline
String
Value:
any – Match anything
-1 – SecureLine usage not recorded for some reason
1 – SecureLine encryption was used
0 – SecureLine encryption was not used

If SecureLine was used, use the delivery status report to see more details.
sendmail_id
String
Return only the message with the specified sendmail_id.
sendmail_ids
String
Comma-delimited list of up to 100 sendmail ids. Returns any matching messages.
spam
String
Value:
0 – Message was not marked as spam by a recipient and returned in a Feed Back Loop
1 – Message was marked as spam by a recipient and returned in a Feed Back Loop
subject
String
Case-insensitive substring search of the message subject (in UTF-8).
to
String
Case-insensitive substring search of all recipient email addresses.
template_id
Integer
Optional template ID to select results only for those messages sent using the specified template. A value of 0 selects all.
tracked_headers
String
If true and this report is for messages sent vis SMTP, then the results will include the six additional fields (header1, header2, header3, header1_value, header2_value, header3_value) which are used to track custom email message header data.
user_id
String
Restrict the report to the user with this specific User ID number.

Responses

Status: 200 - Report content


getEmailSMTPTempFailReportUser

This report allows you to download all temporary failure responses that were experienced when trying to deliver a message or messages to recipients. These provide insight into why it may have taken longer than expected to deliver a specific email message. See also [API Reporting Basics](/rest-api/reporting.html) and [report header columns in the response](/rest-api/report-responses.html#temp_fail).

Access control required to execute this endpoint: User: View Reports


/perl/api/v2/user/{username}/report/email/smtp/temp_fail

Parameters

Path parameters
Name Description
accountId*
String
Required
Header parameters
Name Description
Cookie
Query parameters
Name Description
after_date
String
DATETIME. Return only matches dated after this date time. Format “YYYY-MM-DD HH:MM:SS” in GMT
before_date
String
DATETIME. Return only matches dated before this date time.
first_row
Integer
(Default value 0). All of the matches are sorted and numbered starting from 0. E.g. if you have 100,000 matches, these are rows 0 through 99,999. If you specify a first_row, then the returned matches will be those rows starting from that row. E.g. without a specification (or if you specify 0), you might get rows 0 through 49,999. In your next request you might specify first_row=50000 to get rows 50000 to 99,999.
from_date
String
DATETIME. Return only matches dated on or after this date time.
matches
Integer
(Default value 50000). You can set matches to any value from 0 to 50000. This sets the maximum number of matches that will be returned in response to your request. Note that if the response size starts to exceed 50MB, then the response can still include fewer than your “matches” number, to keep the response size reasonable. If you specify “0” here, then no matches will be returned; however, you will still get the information on the number of matches that there were. For asynchronous reports (ones where a destination is specified), the matches parameter is not limited to 50000, but it still defaults to 50000 if not specified. If you expect a larger number of rows, then you must explicitly approve the maximum size of the result set by setting matches appropriately. This helps prevent accidental queries that produce very larger result sets.
through_date
String
DATETIME. Return only matches dated before or on this date time.
destination
String
For reporting requests. Specifying a destination makes the report "asynchronous." This means that a background job will be created to run the report and upload the final CSV file to the requested destination. The API request to start the report will return immediately with a background "job number" and the filename that will be uploaded. The supported value of "destination" is currently only "sftp" for a Secure FTP upload over SSH (as opposed to ftps, which would be a Secure FTP upload over SSL). When "destination" is specified, additional destination parameters are also required. Note that for SFTP uploads, there is a 15-minute upload timeout -- uploads that take longer (e.g., due to slow SFTP servers) will be aborted. WARNING: Multiple concurrent large asynchronous report requests will impact your database performance: reports will take longer to generate and your LuxSci services will experience degraded/slower performance.
destination_directory
String
For asynchronous reporting requests. This optional parameter will be the subdirectory to change to on the SFTP server before uploading the report CSV file. Technically speaking, this will be the argument provided to the SFTP "chdir" command.
destination_hostname
String
For asynchronous reporting requests. This will be the hostname of the SFTP server to which the report CSV file should be uploaded.
destination_password
String
For asynchronous reporting requests. This will be the password to be used for the login to the SFTP server to which the report CSV file should be uploaded.
destination_username
String
For asynchronous reporting requests. This will be the username to be used for the login to the SFTP server to which the report CSV file should be uploaded.
sendmail_id
String
String. Return temp failures only the messages with the specified sendmail_id
sendmail_ids
String
Comma-delimited list of up to 100 sendmail ids. Returns temporary failures for any matching messages.
to
String
Case-insensitive substring search of all recipient email addresses.

Responses

Status: 200 - Report content


getEmailWebMailClickReportUser

This report allows you to query on the “URL click” events (or lack thereof) for Webmail email messages sent by `username` that have email click tracking enabled. Using this command, it is possible to get a report of all individual clicks or to get reports about messages that have not yet been clicked on or for which click tracking was not enabled. See the query parameters for more detail. *Note: if you are using LuxSci Secure Marketing v2 to send your email messages, then normal LuxSci click and open reporting is disabled (and you will not see click and open data in this report). The LuxSci Secure Marketing v2 platform his its own click and open tracking and reporting system and you should look in that interface for reports.* See also [API Reporting Basics](/rest-api/reporting.html) and [report header columns in the response](/rest-api/report-responses.html#click). Dates, for the purposes of narrowing results, refer to the date the message was sent. This corresponds to the `date_sent` output field. However, if you set the `click_date` input parameter to true, then the `click_date` field will be used for date selections.

Access control required to execute this endpoint: User: View Reports


/perl/api/v2/user/{username}/report/email/webmail/clicks

Parameters

Path parameters
Name Description
username*
String
Required
Header parameters
Name Description
Cookie
Query parameters
Name Description
after_date
String
DATETIME. Return only matches dated after this date time. Format “YYYY-MM-DD HH:MM:SS” in GMT
before_date
String
DATETIME. Return only matches dated before this date time.
first_row
Integer
(Default value 0). All of the matches are sorted and numbered starting from 0. E.g. if you have 100,000 matches, these are rows 0 through 99,999. If you specify a first_row, then the returned matches will be those rows starting from that row. E.g. without a specification (or if you specify 0), you might get rows 0 through 49,999. In your next request you might specify first_row=50000 to get rows 50000 to 99,999.
from_date
String
DATETIME. Return only matches dated on or after this date time.
matches
Integer
(Default value 50000). You can set matches to any value from 0 to 50000. This sets the maximum number of matches that will be returned in response to your request. Note that if the response size starts to exceed 50MB, then the response can still include fewer than your “matches” number, to keep the response size reasonable. If you specify “0” here, then no matches will be returned; however, you will still get the information on the number of matches that there were. For asynchronous reports (ones where a destination is specified), the matches parameter is not limited to 50000, but it still defaults to 50000 if not specified. If you expect a larger number of rows, then you must explicitly approve the maximum size of the result set by setting matches appropriately. This helps prevent accidental queries that produce very larger result sets.
through_date
String
DATETIME. Return only matches dated before or on this date time.
destination
String
For reporting requests. Specifying a destination makes the report "asynchronous." This means that a background job will be created to run the report and upload the final CSV file to the requested destination. The API request to start the report will return immediately with a background "job number" and the filename that will be uploaded. The supported value of "destination" is currently only "sftp" for a Secure FTP upload over SSH (as opposed to ftps, which would be a Secure FTP upload over SSL). When "destination" is specified, additional destination parameters are also required. Note that for SFTP uploads, there is a 15-minute upload timeout -- uploads that take longer (e.g., due to slow SFTP servers) will be aborted. WARNING: Multiple concurrent large asynchronous report requests will impact your database performance: reports will take longer to generate and your LuxSci services will experience degraded/slower performance.
destination_directory
String
For asynchronous reporting requests. This optional parameter will be the subdirectory to change to on the SFTP server before uploading the report CSV file. Technically speaking, this will be the argument provided to the SFTP "chdir" command.
destination_hostname
String
For asynchronous reporting requests. This will be the hostname of the SFTP server to which the report CSV file should be uploaded.
destination_password
String
For asynchronous reporting requests. This will be the password to be used for the login to the SFTP server to which the report CSV file should be uploaded.
destination_username
String
For asynchronous reporting requests. This will be the username to be used for the login to the SFTP server to which the report CSV file should be uploaded.
from
String
Case-insensitive substring search of the message “From” email address
clicked
Integer
If specified, the results are restricted as follows:
clicked < 0 – select messages where click tracking was not enabled.
clicked = 0 – select messages where click tracking was enabled, but where no URLs have yet been clicked by the recipient.
clicked > 0 – select messages where one or more URLs have been clicked by the recipient. When “clicked” is positive, you will get one row back for each click; so,you can get multiple rows per message.

If a value for “clicked” is not specified, a value of “1” will be assumed.
click_date
String
If true, the ”click_date” field will be used for all date selections. If false or not specified, the sent date (“date_sent”) will be used.
header1
String
Case-insensitive name of the custom email header field to match against in the “header 1” column. I.e., if you were matching against “X-My-Header” and saving this in header 1, you would enter “X-My-Header” as the value here.

NOTE: Data is only stored in the customer header capturing fields/columns if you have explicitly enabled this feature in the “Account Administration > Email” area of the LuxSci user interface.
header1_operator
String
If this is present and one of the following 4 values, then the query will only return messages that included “header1” when “header1” was being tracked, and which also satisfy the follow the criteria:
  • is --- The value of the email header named “header1” in the send email must have been exactly the same as header1_value
  • not – The value of the email header named “header1” in the send email must not be exactly the same as header1_value
  • like – The value of the email header named “header1” in the send email must contain (case insensitive) the value in header1_value
  • notlike – The value of the email header named “header1” in the send email must not contain (case insensitive) the value in header1_value
I.e., if you configured your account to capture the value of the header “X-My-Header” and saving this in “header column 1” and an email was sent with the header “X-My-Header: gh6577hh-abc”. This would have been stored in the database. You could then find this message by passing to this API function:
  • header1 = “X-My-Header”
  • header1_operator = “is”
  • header1_value = “gh6577hh-abc”
Or by passing:
  • header1 = “X-My-Header”,/li>
  • header1_operator = “like”
  • header1_value = “abc”
header1_value
String
Text used with “header1_operator” for matching the value of the email header specified in the “header1” parameter in the original sent message.
header2
String
Like “header1” but applies to searching the header 2 column.
header2_operator
String
Like “header1_operator” but applies to searching the header 2 column.
header2_value
String
Like “header1_value” but applies to searching the header 2 column.
header3
String
Like “header1” but applies to searching the header 3 column.
header3_operator
String
Like “header1_operator” but applies to searching the header 3 column.
header3_value
String
Like “header1_value” but applies to searching the header 2 column.
opened
Integer
If specified, the results are restricted as follows:
opened < 0 – select messages where open tracking was not enabled.
opened = 0 – select messages where open tracking was enabled, but which have not yet been opened.
opened > 0 – select messages where open tracking was enabled, and which have been opened at least once.
sendmail_id
String
String. Return only the messages with the specified sendmail_id
sendmail_ids
String
Comma-delimited list of up to 100 sendmail ids. Returns any matching messages.
status
String
Values:
delivered – Accepted by the recipient’s email servers and presumed delivered. If bounce processing is enabled, then this status could change later to ba_soft_fail or ba_hard_fail.
perm_fail – Messages that have permanently failed to be delivered to the recipient’s servers. If bounce processing is on, this status could change shortly to ba_soft_fail, depending on the nature of the failure message.
lost – Messages where the tracking was lost and it is unclear if it was delivered or lost from the queue.
queued – Message is in the email server queue still waiting to be delivered to the recipient.
not_queued -- all statuses except "queued".
ba_soft_fail – Soft failure bounces received (when talking to the recipient’s servers or after successful delivery to the recipient’s servers).
ba_hard_fail – Hard failure bounces received after successful delivery to the recipient’s servers,
any_hard_fail – Results for ba_hard_fail OR perm_fail. I.e., all hard/permanent failures.
subject
String
Case-insensitive substring search of the message subject (in UTF8).
to
String
Case-insensitive substring search of all recipient email addresses.
tracked_headers
String
If true and this report is for messages sent vis SMTP, then the results will include the six additional fields (header1, header2, header3, header1_value, header2_value, header3_value) which are used to track custom email message header data.
user_id
String
Restrict the report to the user with this specific User ID number
url
String
Substring match on the URL clicked.

Responses

Status: 200 - Report content


getEmailWebMailDeliveryStatusReportUser

This report allows you to see how each Webmail message sent by `username` was sent to each recipient and what the delivery status is for each of these recipients. Note that delivery status changes over time as messages progress to the recipient’s servers and as bounce messages are sent back and processed. As the delivery status changes, the “last_update” date is also updated. See also [API Reporting Basics](/rest-api/reporting.html) and [report header columns in the response](/rest-api/report-responses.html#delivery). Dates, for the purposes of narrowing results, refer to the *date the message delivery status was last updated*. This corresponds to the `last_update` output field. This can be changed to the date the message was sent using the "sent_date" parameter.

Access control required to execute this endpoint: User: View Reports


/perl/api/v2/user/{username}/report/email/webmail/delivery

Parameters

Path parameters
Name Description
username*
String
Required
Header parameters
Name Description
Cookie
Query parameters
Name Description
after_date
String
DATETIME. Return only matches dated after this date time. Format “YYYY-MM-DD HH:MM:SS” in GMT
before_date
String
DATETIME. Return only matches dated before this date time.
first_row
Integer
(Default value 0). All of the matches are sorted and numbered starting from 0. E.g. if you have 100,000 matches, these are rows 0 through 99,999. If you specify a first_row, then the returned matches will be those rows starting from that row. E.g. without a specification (or if you specify 0), you might get rows 0 through 49,999. In your next request you might specify first_row=50000 to get rows 50000 to 99,999.
from_date
String
DATETIME. Return only matches dated on or after this date time.
matches
Integer
(Default value 50000). You can set matches to any value from 0 to 50000. This sets the maximum number of matches that will be returned in response to your request. Note that if the response size starts to exceed 50MB, then the response can still include fewer than your “matches” number, to keep the response size reasonable. If you specify “0” here, then no matches will be returned; however, you will still get the information on the number of matches that there were. For asynchronous reports (ones where a destination is specified), the matches parameter is not limited to 50000, but it still defaults to 50000 if not specified. If you expect a larger number of rows, then you must explicitly approve the maximum size of the result set by setting matches appropriately. This helps prevent accidental queries that produce very larger result sets.
through_date
String
DATETIME. Return only matches dated before or on this date time.
destination
String
For reporting requests. Specifying a destination makes the report "asynchronous." This means that a background job will be created to run the report and upload the final CSV file to the requested destination. The API request to start the report will return immediately with a background "job number" and the filename that will be uploaded. The supported value of "destination" is currently only "sftp" for a Secure FTP upload over SSH (as opposed to ftps, which would be a Secure FTP upload over SSL). When "destination" is specified, additional destination parameters are also required. Note that for SFTP uploads, there is a 15-minute upload timeout -- uploads that take longer (e.g., due to slow SFTP servers) will be aborted. WARNING: Multiple concurrent large asynchronous report requests will impact your database performance: reports will take longer to generate and your LuxSci services will experience degraded/slower performance.
destination_directory
String
For asynchronous reporting requests. This optional parameter will be the subdirectory to change to on the SFTP server before uploading the report CSV file. Technically speaking, this will be the argument provided to the SFTP "chdir" command.
destination_hostname
String
For asynchronous reporting requests. This will be the hostname of the SFTP server to which the report CSV file should be uploaded.
destination_password
String
For asynchronous reporting requests. This will be the password to be used for the login to the SFTP server to which the report CSV file should be uploaded.
destination_username
String
For asynchronous reporting requests. This will be the username to be used for the login to the SFTP server to which the report CSV file should be uploaded.
clicked
Integer
Integer. If specified, the results are restricted as follows:
clicked < 0 – select messages where URL click tracking was not enabled.
clicked = 0 – select messages where URL click tracking was enabled, but where there have as yet been no clicks on any clinks in the messages.
clicked > 0 – select messages where URL click tracking was enabled and where there have been N or more clicks on links in the same message to the same recipient. N, in this case, is the number that you have specified as the value of the “clicked” parameter. I.e., using a value of “1” matches all messages that have had a link clicked on.
from
String
String. Case-insensitive substring search of the message “From” email Address
ip
String
String. Case-insensitive substring search of the sender IP address (for SMTP reports only).
header1
String
Case-insensitive name of the custom email header field to match against in the “header 1” column. I.e., if you were matching against “X-My-Header” and saving this in header 1, you would enter “X-My-Header” as the value here.

NOTE: Data is only stored in the customer header capturing fields/columns if you have explicitly enabled this feature in the “Account Administration > Email” area of the LuxSci user interface.
header1_operator
String
If this is present and one of the following 4 values, then the query will only return messages that included “header1” when “header1” was being tracked, and which also satisfy the follow the criteria:
  • is --- The value of the email header named “header1” in the send email must have been exactly the same as header1_value
  • not – The value of the email header named “header1” in the send email must not be exactly the same as header1_value
  • like – The value of the email header named “header1” in the send email must contain (case insensitive) the value in header1_value
  • notlike – The value of the email header named “header1” in the send email must not contain (case insensitive) the value in header1_value
I.e., if you configured your account to capture the value of the header “X-My-Header” and saving this in “header column 1” and an email was sent with the header “X-My-Header: gh6577hh-abc”. This would have been stored in the database. You could then find this message by passing to this API function:
  • header1 = “X-My-Header”
  • header1_operator = “is”
  • header1_value = “gh6577hh-abc”
Or by passing:
  • header1 = “X-My-Header”,/li>
  • header1_operator = “like”
  • header1_value = “abc”
header1_value
String
Text used with “header1_operator” for matching the value of the email header specified in the “header1” parameter in the original sent message.
header2
String
Like “header1” but applies to searching the header 2 column.
header2_operator
String
Like “header1_operator” but applies to searching the header 2 column.
header2_value
String
Like “header1_value” but applies to searching the header 2 column.
header3
String
Like “header1” but applies to searching the header 3 column.
header3_operator
String
Like “header1_operator” but applies to searching the header 3 column.
header3_value
String
Like “header1_value” but applies to searching the header 2 column.
opened
Integer
Integer. If specified, the results are restricted as follows:
opened < 0 – select messages where open tracking was not enabled.
opened = 0 – select messages where open tracking was enabled, but which have not yet been opened.
opened > 0 – select messages where open tracking was enabled and which have been opened at least N times. N, in this case, is the number that you have specified as the value of the “opened” parameter. I.e., using a value of “1” matches all messages that have been opened.
secureline
String
Enum. Value:
u – Message to this recipient did not use SecureLine (or Opt Out was used)
e – Message did use SecureLine
-2 – SecureLine was not used due to Opt Out being selected
-1 – SecureLine usage not recorded for some reason
1 – SecureLine:PGP was used
2 – SecureLine:S/MIME was used
3 – SecureLine:Escrow was used
4 – SecureLine:TLS was used
sendmail_id
String
String. Return only the messages with the specified sendmail_id
sendmail_ids
String
Comma-delimited list of up to 100 sendmail ids. Returns any matching messages.
sent_date
Integer
If set to true (i.e., 1), the email message sent date will be used for date/time selections, instead of the date of the last update of the delivery status.
spam
Integer
Enum. Value:
0 – Message was not marked as spam by a recipient and returned in a Feed Back Loop.
1 – Message was marked as spam by a recipient and returned in a Feed Back Loop
tls
Integer
Enum. Value:
0 – TLS was NOT used in the successful delivery of this message to the recipient server
1 – TLS was used in the successful delivery of this message to the recipient server
tracked_headers
String
If true and this report is for messages sent vis SMTP, then the results will include the six additional fields (header1, header2, header3, header1_value, header2_value, header3_value) which are used to track custom email message header data.
to
String
Case-insensitive substring search of all recipient email addresses.
user_id
Integer
Integer. Restrict the report to the user with this specific User ID number

Responses

Status: 200 - Report content


getEmailWebMailOpenReportUser

This report allows you to query on the “opened” events (or lack thereof) for email messages sent via Webmail by `username` that have email open tracking enabled. Using this command, it is possible to get a report of all individual opens for messages or to get reports about messages that have not yet been opened or for which open tracking was not enabled. See the query parameters for more detail. *Note: if you are using LuxSci Secure Marketing v2 to send your email messages, then normal LuxSci click and open reporting is disabled (and you will not see click and open data in this report). The LuxSci Secure Marketing v2 platform his its own click and open tracking and reporting system and you should look in that interface for reports.* See also [API Reporting Basics](/rest-api/reporting.html) and [report header columns in the response](/rest-api/report-responses.html#open). Dates, for the purposes of narrowing results, refer to the date the message was sent. This corresponds to the `date_sent` output field. However, if you set the `open_date` input parameter to true, then the `open_date` field will be used for date selections.

Access control required to execute this endpoint: User: View Reports


/perl/api/v2/user/{username}/report/email/webmail/opens

Parameters

Path parameters
Name Description
username*
String
Required
Header parameters
Name Description
Cookie
Query parameters
Name Description
after_date
String
DATETIME. Return only matches dated after this date time. Format “YYYY-MM-DD HH:MM:SS” in GMT
before_date
String
DATETIME. Return only matches dated before this date time.
first_row
Integer
(Default value 0). All of the matches are sorted and numbered starting from 0. E.g. if you have 100,000 matches, these are rows 0 through 99,999. If you specify a first_row, then the returned matches will be those rows starting from that row. E.g. without a specification (or if you specify 0), you might get rows 0 through 49,999. In your next request you might specify first_row=50000 to get rows 50000 to 99,999.
from_date
String
DATETIME. Return only matches dated on or after this date time.
matches
Integer
(Default value 50000). You can set matches to any value from 0 to 50000. This sets the maximum number of matches that will be returned in response to your request. Note that if the response size starts to exceed 50MB, then the response can still include fewer than your “matches” number, to keep the response size reasonable. If you specify “0” here, then no matches will be returned; however, you will still get the information on the number of matches that there were. For asynchronous reports (ones where a destination is specified), the matches parameter is not limited to 50000, but it still defaults to 50000 if not specified. If you expect a larger number of rows, then you must explicitly approve the maximum size of the result set by setting matches appropriately. This helps prevent accidental queries that produce very larger result sets.
through_date
String
DATETIME. Return only matches dated before or on this date time.
destination
String
For reporting requests. Specifying a destination makes the report "asynchronous." This means that a background job will be created to run the report and upload the final CSV file to the requested destination. The API request to start the report will return immediately with a background "job number" and the filename that will be uploaded. The supported value of "destination" is currently only "sftp" for a Secure FTP upload over SSH (as opposed to ftps, which would be a Secure FTP upload over SSL). When "destination" is specified, additional destination parameters are also required. Note that for SFTP uploads, there is a 15-minute upload timeout -- uploads that take longer (e.g., due to slow SFTP servers) will be aborted. WARNING: Multiple concurrent large asynchronous report requests will impact your database performance: reports will take longer to generate and your LuxSci services will experience degraded/slower performance.
destination_directory
String
For asynchronous reporting requests. This optional parameter will be the subdirectory to change to on the SFTP server before uploading the report CSV file. Technically speaking, this will be the argument provided to the SFTP "chdir" command.
destination_hostname
String
For asynchronous reporting requests. This will be the hostname of the SFTP server to which the report CSV file should be uploaded.
destination_password
String
For asynchronous reporting requests. This will be the password to be used for the login to the SFTP server to which the report CSV file should be uploaded.
destination_username
String
For asynchronous reporting requests. This will be the username to be used for the login to the SFTP server to which the report CSV file should be uploaded.
from
String
Case-insensitive substring search of the message “From” email address
header1
String
Case-insensitive name of the custom email header field to match against in the “header 1” column. I.e., if you were matching against “X-My-Header” and saving this in header 1, you would enter “X-My-Header” as the value here.

NOTE: Data is only stored in the customer header capturing fields/columns if you have explicitly enabled this feature in the “Account Administration > Email” area of the LuxSci user interface.
header1_operator
String
If this is present and one of the following 4 values, then the query will only return messages that included “header1” when “header1” was being tracked, and which also satisfy the follow the criteria:
  • is --- The value of the email header named “header1” in the send email must have been exactly the same as header1_value
  • not – The value of the email header named “header1” in the send email must not be exactly the same as header1_value
  • like – The value of the email header named “header1” in the send email must contain (case insensitive) the value in header1_value
  • notlike – The value of the email header named “header1” in the send email must not contain (case insensitive) the value in header1_value
I.e., if you configured your account to capture the value of the header “X-My-Header” and saving this in “header column 1” and an email was sent with the header “X-My-Header: gh6577hh-abc”. This would have been stored in the database. You could then find this message by passing to this API function:
  • header1 = “X-My-Header”
  • header1_operator = “is”
  • header1_value = “gh6577hh-abc”
Or by passing:
  • header1 = “X-My-Header”,/li>
  • header1_operator = “like”
  • header1_value = “abc”
header1_value
String
Text used with “header1_operator” for matching the value of the email header specified in the “header1” parameter in the original sent message.
header2
String
Like “header1” but applies to searching the header 2 column.
header2_operator
String
Like “header1_operator” but applies to searching the header 2 column.
header2_value
String
Like “header1_value” but applies to searching the header 2 column.
header3
String
Like “header1” but applies to searching the header 3 column.
header3_operator
String
Like “header1_operator” but applies to searching the header 3 column.
header3_value
String
Like “header1_value” but applies to searching the header 2 column.
opened
Integer
If specified, the results are restricted as follows:
opened < 0 – select messages where open tracking was not enabled.
opened = 0 – select messages where open tracking was enabled, but which have not yet been opened.
opened > 0 – select messages where open tracking was enabled and which have been opened at least once. When opened is positive, you will get one row back for each open; so, you can get multiple rows per message.

If you do not specify a value for “opened”, a value of “1” will be assumed.
open_date
Boolean
If true, the ”open_date” field will be used for all date selections. If false or not specified, the sent date (“date_sent”) will be used.
sendmail_id
String
Return only the messages with the specified sendmail_id.
sendmail_ids
String
Comma-delimited list of up to 100 sendmail ids. Returns any matching messages.
status
String
Values:
delivered – Accepted by the recipient’s email servers and presumed delivered. If bounce processing is enabled, then this status could change later to ba_soft_fail or ba_hard_fail.
perm_fail – Messages that have permanently failed to be delivered to the recipient’s servers. If bounce processing is on, this status could change shortly to ba_soft_fail, depending on the nature of the failure message.
lost – Messages where the tracking was lost and it is unclear if it was delivered or lost from the queue.
queued – Message is in the email server queue still waiting to be delivered to the recipient.
not_queued -- all statuses except "queued".
ba_soft_fail – Soft failure bounces received (when talking to the recipient’s servers or after successful delivery to the recipient’s servers).
ba_hard_fail – Hard failure bounces received after successful delivery to the recipient’s servers,
any_hard_fail – Results for ba_hard_fail OR perm_fail. I.e., all hard/permanent failures.
subject
String
Case-insensitive substring search of the message subject (in UTF8).
to
String
Case-insensitive substring search of all recipient email addresses.
tracked_headers
String
If true and this report is for messages sent vis SMTP, then the results will include the six additional fields (header1, header2, header3, header1_value, header2_value, header3_value) which are used to track custom email message header data.
user_id
String
Restrict the report to the user with this specific User ID number

Responses

Status: 200 - Report content


getEmailWebMailSentReportUser

Return a list of all email messages sent via Webmail by `username`. See also [API Reporting Basics](/rest-api/reporting.html) and [report header columns in the response](/rest-api/report-responses.html#sent).

Access control required to execute this endpoint: User: View Reports


/perl/api/v2/user/{username}/report/email/webmail/sent

Parameters

Path parameters
Name Description
username*
String
Required
Header parameters
Name Description
Cookie
Query parameters
Name Description
after_date
String
DATETIME. Return only matches dated after this date time. Format “YYYY-MM-DD HH:MM:SS” in GMT
before_date
String
DATETIME. Return only matches dated before this date time.
first_row
Integer
(Default value 0). All of the matches are sorted and numbered starting from 0. E.g. if you have 100,000 matches, these are rows 0 through 99,999. If you specify a first_row, then the returned matches will be those rows starting from that row. E.g. without a specification (or if you specify 0), you might get rows 0 through 49,999. In your next request you might specify first_row=50000 to get rows 50000 to 99,999.
from_date
String
DATETIME. Return only matches dated on or after this date time.
matches
Integer
(Default value 50000). You can set matches to any value from 0 to 50000. This sets the maximum number of matches that will be returned in response to your request. Note that if the response size starts to exceed 50MB, then the response can still include fewer than your “matches” number, to keep the response size reasonable. If you specify “0” here, then no matches will be returned; however, you will still get the information on the number of matches that there were. For asynchronous reports (ones where a destination is specified), the matches parameter is not limited to 50000, but it still defaults to 50000 if not specified. If you expect a larger number of rows, then you must explicitly approve the maximum size of the result set by setting matches appropriately. This helps prevent accidental queries that produce very larger result sets.
through_date
String
DATETIME. Return only matches dated before or on this date time.
destination
String
For reporting requests. Specifying a destination makes the report "asynchronous." This means that a background job will be created to run the report and upload the final CSV file to the requested destination. The API request to start the report will return immediately with a background "job number" and the filename that will be uploaded. The supported value of "destination" is currently only "sftp" for a Secure FTP upload over SSH (as opposed to ftps, which would be a Secure FTP upload over SSL). When "destination" is specified, additional destination parameters are also required. Note that for SFTP uploads, there is a 15-minute upload timeout -- uploads that take longer (e.g., due to slow SFTP servers) will be aborted. WARNING: Multiple concurrent large asynchronous report requests will impact your database performance: reports will take longer to generate and your LuxSci services will experience degraded/slower performance.
destination_directory
String
For asynchronous reporting requests. This optional parameter will be the subdirectory to change to on the SFTP server before uploading the report CSV file. Technically speaking, this will be the argument provided to the SFTP "chdir" command.
destination_hostname
String
For asynchronous reporting requests. This will be the hostname of the SFTP server to which the report CSV file should be uploaded.
destination_password
String
For asynchronous reporting requests. This will be the password to be used for the login to the SFTP server to which the report CSV file should be uploaded.
destination_username
String
For asynchronous reporting requests. This will be the username to be used for the login to the SFTP server to which the report CSV file should be uploaded.
from
String
Case-insensitive substring search of the message “From” email address
header1
String
Case-insensitive name of the custom email header field to match against in the “header 1” column. I.e., if you were matching against “X-My-Header” and saving this in header 1, you would enter “X-My-Header” as the value here.

NOTE: Data is only stored in the customer header capturing fields/columns if you have explicitly enabled this feature in the “Account Administration > Email” area of the LuxSci user interface.
header1_operator
String
If this is present and one of the following 4 values, then the query will only return messages that included “header1” when “header1” was being tracked, and which also satisfy the follow the criteria:
  • is --- The value of the email header named “header1” in the send email must have been exactly the same as header1_value
  • not – The value of the email header named “header1” in the send email must not be exactly the same as header1_value
  • like – The value of the email header named “header1” in the send email must contain (case insensitive) the value in header1_value
  • notlike – The value of the email header named “header1” in the send email must not contain (case insensitive) the value in header1_value
I.e., if you configured your account to capture the value of the header “X-My-Header” and saving this in “header column 1” and an email was sent with the header “X-My-Header: gh6577hh-abc”. This would have been stored in the database. You could then find this message by passing to this API function:
  • header1 = “X-My-Header”
  • header1_operator = “is”
  • header1_value = “gh6577hh-abc”
Or by passing:
  • header1 = “X-My-Header”,/li>
  • header1_operator = “like”
  • header1_value = “abc”
header1_value
String
Text used with “header1_operator” for matching the value of the email header specified in the “header1” parameter in the original sent message.
header2
String
Like “header1” but applies to searching the header 2 column.
header2_operator
String
Like “header1_operator” but applies to searching the header 2 column.
header2_value
String
Like “header1_value” but applies to searching the header 2 column.
header3
String
Like “header1” but applies to searching the header 3 column.
header3_operator
String
Like “header1_operator” but applies to searching the header 3 column.
header3_value
String
Like “header1_value” but applies to searching the header 2 column.
ip
String
Case-insensitive substring search of the sender IP address (for SMTP reports only).
opt_out
String
Value:
0 – SecureLine Opt Out not used
-1 – SecureLine Opt Out use not recorded for some reason
1 – SecureLine Opt Out
secureline
String
Value:
any – Match anything
-1 – SecureLine usage not recorded for some reason
1 – SecureLine encryption was used
0 – SecureLine encryption was not used

If SecureLine was used, use the delivery status report to see more details.
sendmail_id
String
Return only the message with the specified sendmail_id.
sendmail_ids
String
Comma-delimited list of up to 100 sendmail ids. Returns any matching messages.
spam
String
Value:
0 – Message was not marked as spam by a recipient and returned in a Feed Back Loop
1 – Message was marked as spam by a recipient and returned in a Feed Back Loop
subject
String
Case-insensitive substring search of the message subject (in UTF-8).
to
String
Case-insensitive substring search of all recipient email addresses.
tracked_headers
String
If true and this report is for messages sent vis SMTP, then the results will include the six additional fields (header1, header2, header3, header1_value, header2_value, header3_value) which are used to track custom email message header data.
user_id
String
Restrict the report to the user with this specific User ID number.

Responses

Status: 200 - Report content


getUserJob

Return the details of a specific asynchronous reporting job. If the job_id is not found, a not found API error will be emitted.


/perl/api/v2/user/{username}/job/{job_id}

Parameters

Path parameters
Name Description
username*
String
Required
job_id*
Integer
Required
Header parameters
Name Description
Cookie

Responses

Status: 200 - This will return an associated array containing standard job description details.


getUserJobs

Return a list of all asynchronous reporting jobs submitted by this user in the past 7 days.


/perl/api/v2/user/{username}/jobs

Parameters

Path parameters
Name Description
username*
String
Required
Header parameters
Name Description
Cookie

Responses

Status: 200 - This will return a list of associated arrays each containing standard job description details.


getUserSuppressionReport

Retrieve all email suppressions at the user level using a report-style call. See also [API Reporting Basics](/rest-api/reporting.html) and [report header columns in the response](/rest-api/report-responses.html#sup).

Access control required to execute this endpoint: User Email: Suppression


/perl/api/v2/user/{username}/suppression_v2/

Parameters

Path parameters
Name Description
username*
String
Required
Header parameters
Name Description
Cookie
Query parameters
Name Description
email
String
Restrict the report to suppressions of this specific email address.
after_date
String
DATETIME. Return only matches dated after this date time. Format “YYYY-MM-DD HH:MM:SS” in GMT
before_date
String
DATETIME. Return only matches dated before this date time.
first_row
Integer
(Default value 0). All of the matches are sorted and numbered starting from 0. E.g. if you have 100,000 matches, these are rows 0 through 99,999. If you specify a first_row, then the returned matches will be those rows starting from that row. E.g. without a specification (or if you specify 0), you might get rows 0 through 49,999. In your next request you might specify first_row=50000 to get rows 50000 to 99,999.
from_date
String
DATETIME. Return only matches dated on or after this date time.
matches
Integer
(Default value 50000). You can set matches to any value from 0 to 50000. This sets the maximum number of matches that will be returned in response to your request. Note that if the response size starts to exceed 50MB, then the response can still include fewer than your “matches” number, to keep the response size reasonable. If you specify “0” here, then no matches will be returned; however, you will still get the information on the number of matches that there were. For asynchronous reports (ones where a destination is specified), the matches parameter is not limited to 50000, but it still defaults to 50000 if not specified. If you expect a larger number of rows, then you must explicitly approve the maximum size of the result set by setting matches appropriately. This helps prevent accidental queries that produce very larger result sets.
through_date
String
DATETIME. Return only matches dated before or on this date time.
destination
String
For reporting requests. Specifying a destination makes the report "asynchronous." This means that a background job will be created to run the report and upload the final CSV file to the requested destination. The API request to start the report will return immediately with a background "job number" and the filename that will be uploaded. The supported value of "destination" is currently only "sftp" for a Secure FTP upload over SSH (as opposed to ftps, which would be a Secure FTP upload over SSL). When "destination" is specified, additional destination parameters are also required. Note that for SFTP uploads, there is a 15-minute upload timeout -- uploads that take longer (e.g., due to slow SFTP servers) will be aborted. WARNING: Multiple concurrent large asynchronous report requests will impact your database performance: reports will take longer to generate and your LuxSci services will experience degraded/slower performance.
destination_directory
String
For asynchronous reporting requests. This optional parameter will be the subdirectory to change to on the SFTP server before uploading the report CSV file. Technically speaking, this will be the argument provided to the SFTP "chdir" command.
destination_hostname
String
For asynchronous reporting requests. This will be the hostname of the SFTP server to which the report CSV file should be uploaded.
destination_password
String
For asynchronous reporting requests. This will be the password to be used for the login to the SFTP server to which the report CSV file should be uploaded.
destination_username
String
For asynchronous reporting requests. This will be the username to be used for the login to the SFTP server to which the report CSV file should be uploaded.

Responses

Status: 200 - Report of suppressions


getUserSuppressionSummaryReport

Retrieve a count of the matching email suppressions at the user level using a report-style call. Dates are based on the date that the suppression was added. See also [API Reporting Basics](/rest-api/reporting.html) and [report header columns in the response](/rest-api/report-responses.html#sup_count).

Access control required to execute this endpoint: User Email: Suppression


/perl/api/v2/user/{username}/suppression_count/

Parameters

Path parameters
Name Description
username*
String
Required
Header parameters
Name Description
Cookie
Query parameters
Name Description
after_date
String
DATETIME. Return only matches dated after this date time. Format “YYYY-MM-DD HH:MM:SS” in GMT
before_date
String
DATETIME. Return only matches dated before this date time.
first_row
Integer
(Default value 0). All of the matches are sorted and numbered starting from 0. E.g. if you have 100,000 matches, these are rows 0 through 99,999. If you specify a first_row, then the returned matches will be those rows starting from that row. E.g. without a specification (or if you specify 0), you might get rows 0 through 49,999. In your next request you might specify first_row=50000 to get rows 50000 to 99,999.
from_date
String
DATETIME. Return only matches dated on or after this date time.
matches
Integer
(Default value 50000). You can set matches to any value from 0 to 50000. This sets the maximum number of matches that will be returned in response to your request. Note that if the response size starts to exceed 50MB, then the response can still include fewer than your “matches” number, to keep the response size reasonable. If you specify “0” here, then no matches will be returned; however, you will still get the information on the number of matches that there were. For asynchronous reports (ones where a destination is specified), the matches parameter is not limited to 50000, but it still defaults to 50000 if not specified. If you expect a larger number of rows, then you must explicitly approve the maximum size of the result set by setting matches appropriately. This helps prevent accidental queries that produce very larger result sets.
through_date
String
DATETIME. Return only matches dated before or on this date time.
destination
String
For reporting requests. Specifying a destination makes the report "asynchronous." This means that a background job will be created to run the report and upload the final CSV file to the requested destination. The API request to start the report will return immediately with a background "job number" and the filename that will be uploaded. The supported value of "destination" is currently only "sftp" for a Secure FTP upload over SSH (as opposed to ftps, which would be a Secure FTP upload over SSL). When "destination" is specified, additional destination parameters are also required. Note that for SFTP uploads, there is a 15-minute upload timeout -- uploads that take longer (e.g., due to slow SFTP servers) will be aborted. WARNING: Multiple concurrent large asynchronous report requests will impact your database performance: reports will take longer to generate and your LuxSci services will experience degraded/slower performance.
destination_directory
String
For asynchronous reporting requests. This optional parameter will be the subdirectory to change to on the SFTP server before uploading the report CSV file. Technically speaking, this will be the argument provided to the SFTP "chdir" command.
destination_hostname
String
For asynchronous reporting requests. This will be the hostname of the SFTP server to which the report CSV file should be uploaded.
destination_password
String
For asynchronous reporting requests. This will be the password to be used for the login to the SFTP server to which the report CSV file should be uploaded.
destination_username
String
For asynchronous reporting requests. This will be the username to be used for the login to the SFTP server to which the report CSV file should be uploaded.
filter1
String
Control when a summary report returns values (for use with automated reports). See https://luxsci.com/rest-api/reporting.html#filters
filter2
String
Control when a summary report returns values (for use with automated reports). See https://luxsci.com/rest-api/reporting.html#filters
filter3
String
Control when a summary report returns values (for use with automated reports). See https://luxsci.com/rest-api/reporting.html#filters

Responses

Status: 200 - Report the count of matching suppressions. The returned field name for this count is suppressions.


Users

changeUserPassword

This command changes the user’s password. It validates the new password using all the same tests that would be applied if you were changing the password in the Web Interface. Make sure that the configuration settings for password strength validation are compatible with that used by your own applications generating the passwords. You cannot change the passwords of users that have been disabled. You must re-enable them first, then change the password.

Access control required to execute this endpoint: User Settings - Change Password


/perl/api/v2/user/{username}/password

Parameters

Path parameters
Name Description
username*
String
Required
Body parameters
Name Description
body

Responses

Status: 201 - Response description.


createAppSpecificPassword

This command creates a new user app-specific password/login for a specific user. Note that users can have at most 30 app-specific passwords defined at any one time.

Access control required to execute this endpoint: User Settings - Change Password


/perl/api/v2/user/{username}/app-password/{suffix}

Parameters

Path parameters
Name Description
username*
String
Required
suffix*
String
It is the plain text suffix to the user’s regular login email address that will be used to create this new app-specific password. E.g., if you specify “email” as the suffix for the user ‘user@domain.com’, then the new login will be ‘usr@domain.com/email’. The suffix string must be 1-10 characters long and can only contain letters and numbers. It is also case insensitive (so will be converted to lower case).'
Required
Header parameters
Name Description
Cookie
Body parameters
Name Description
body

Responses

Status: 201 - The response body for a successful request will have a keywords and data in the “data” in the JSON response.


createUser

Create a new user in your account. Your API Interface looks to see how many users were added to your account in the past 24 hours. If this number is equal or greater than your API create limit, then your API will reject additional user creation requests until that situation changes. See your API Interface configuration page for your user creation limit. If you would like to update other user information, such as contact information, disk quota, etc., you would use other, specific API calls. The user’s initial preferences are copied from the account main administrator user. This user will have all licenses and services that are currently being purchased “for all users” in your account or which are required (e.g. SecureLine for HIPAA or Archival in a domain provisioned for Archival). **Upgrades:** If your account does not have available user licenses (or licenses for SecureLine, Archival, or other needed services) for this new user, then either the request will be rejected, or your account will be auto-upgraded if you have “Permit auto-upgrades as needed for fulfill requests” enabled. In the latter case, your account will be upgraded by a block of at least your specified “licenses at a time” upgrade setting from your API Interface configuration.

Access control required to execute this endpoint: Account: Users - Add


/perl/api/v2/account/{accountId}/users

Parameters

Path parameters
Name Description
accountId*
String
Required
Header parameters
Name Description
Cookie
Body parameters
Name Description
body

Responses

Status: 200 - ""


deleteAppSpecificPassword

This command removes a user app-specific password/login for a specific user.

Access control required to execute this endpoint: User Settings - Change Password


/perl/api/v2/user/{username}/app-password/{suffix}

Parameters

Path parameters
Name Description
username*
String
Required
suffix*
String
It is the plain text suffix to the user’s regular login email address that will be used to identify the app-specific password. E.g., if you specify “email” as the suffix for the user ‘user@ domain.com’, then the login deleted will be ‘usr@domain.com/email’.
Required
Header parameters
Name Description
Cookie

Responses

Status: 201 - Response description.


deleteUser

Delete the user from the system. This eliminates all the user’s data, history, web/ftp files, and email. After this command is complete, there will no longer be any record that the user existed. **This command cannot be undone.** Note that some users cannot be deleted in this way. For example, any user with “account management” permission cannot be deleted. Other users may not be able to be deleted if there are things in your account (e.g., web sites) that are still owned by them. You will receive an error if you try to delete a user that is not currently deletable. Note that deletion of a user does not downgrade your account. Please contact billing for account downgrade requests.

Access control required to execute this endpoint: Account: Users - Enable/Disable/Delete


/perl/api/v2/account/{accountId}/users/{username}

Parameters

Path parameters
Name Description
accountId*
String
Required
username*
String
Required
Header parameters
Name Description
Cookie

Responses

Status: 200 - ""


getTimeZonesList

Return a list of all available time zones. The keywords are the canonical time zone names. The values are plain text versions of the names. Note, that with the “GMT+/-” times, specifically, the canonical name has the opposite sign compared to the common plain text version we all are used to seeing. E.g. “GMT-5” for Eastern Time USA, has a canonical name of “GMT+5”. Ya, weird, but based on how the standard time zone database works – we use these canonical names in conjunction with the standard time zone database to translate times from one time zone to another. So, if you are in “GMT+5”, your saved time zone name will be “GMT-5” so that, behind the scenes, the software can use this database to properly handle your time.

Access control required to execute this endpoint: User Settings - Read


/perl/api/v2/user/{username}/settings/timezones

Parameters

Path parameters
Name Description
username*
String
Required
Header parameters
Name Description
Cookie

Responses

Status: 200 - The response body for a successful request will have a keywords and data in the “data” in the JSON response. The keywords are the time zone code names (e.g. “EST”) and the values are the descriptions for these names (e.g. “EST: Eastern Standard Time”).


getUser

Return contact information and other general metadata for the user.

Access control required to execute this endpoint: User Settings - Read


/perl/api/v2/user/{username}

Parameters

Path parameters
Name Description
username*
String
Required
Header parameters
Name Description
Cookie

Responses

Status: 200 - User profile


getUserBrandingInformation

Return information that can be used to brand (private label) a user interface consistently with the branding the user would experience when logging in to WebMail. Other keywords may be added in the future as the need arises.

Access control required to execute this endpoint: User Settings - Read


/perl/api/v2/user/{username}/branding

Parameters

Path parameters
Name Description
username*
String
Required
Header parameters
Name Description
Cookie

Responses

Status: 200 - The response body for a successful request will have a keywords and data in the “data” in the JSON response.


getUserProfile

Return contact information and other general metadata for the user. This endpoint is the same as `getUser`.

Access control required to execute this endpoint: User Settings - Read


/perl/api/v2/user/{username}/profile

Parameters

Path parameters
Name Description
username*
String
Required
Header parameters
Name Description
Cookie

Responses

Status: 200 - User profile


getUserReport

Return an array of information about all users matching your query request. The Request query string can contain any or all of the following keywords parameters to refine the search. If all are omitted, the report will include information about all users in the account. In all cases, any users protected from API access will not be included in the report.

Access control required to execute this endpoint: User Settings: Read Access


/perl/api/v2/account/{accountId}/users

Parameters

Path parameters
Name Description
accountId*
String
Required
Header parameters
Name Description
Cookie
Query parameters
Name Description
status
String
Value ‘enabled’ – return only active/enabled users.
Value ‘disabled’ – return only disabled users.
domain
String
Domain name in your account. If supplied, only users in this domain will be returned.
younger_than
Integer
Return only users created less than this number of days ago.
older_than
Integer
Return only users created more than this number of days ago.

Responses

Status: 200 - The successful response will be an array of objects, one for each matching user in your account.


getUserReport2

This report-style API call returns a list of all users in the account, with optional date range selection by user creation date. See also [API Reporting Basics](/rest-api/reporting.html) and [report header columns in the response](/rest-api/report-responses.html#users).

Access control required to execute this endpoint: Account: View Reports


/perl/api/v2/account/{accountId}/users/report

Parameters

Path parameters
Name Description
accountId*
String
Required
Header parameters
Name Description
Cookie
Query parameters
Name Description
after_date
String
DATETIME. Return only matches dated after this date time. Format “YYYY-MM-DD HH:MM:SS” in GMT
before_date
String
DATETIME. Return only matches dated before this date time.
first_row
Integer
(Default value 0). All of the matches are sorted and numbered starting from 0. E.g. if you have 100,000 matches, these are rows 0 through 99,999. If you specify a first_row, then the returned matches will be those rows starting from that row. E.g. without a specification (or if you specify 0), you might get rows 0 through 49,999. In your next request you might specify first_row=50000 to get rows 50000 to 99,999.
from_date
String
DATETIME. Return only matches dated on or after this date time.
matches
Integer
(Default value 50000). You can set matches to any value from 0 to 50000. This sets the maximum number of matches that will be returned in response to your request. Note that if the response size starts to exceed 50MB, then the response can still include fewer than your “matches” number, to keep the response size reasonable. If you specify “0” here, then no matches will be returned; however, you will still get the information on the number of matches that there were. For asynchronous reports (ones where a destination is specified), the matches parameter is not limited to 50000, but it still defaults to 50000 if not specified. If you expect a larger number of rows, then you must explicitly approve the maximum size of the result set by setting matches appropriately. This helps prevent accidental queries that produce very larger result sets.
through_date
String
DATETIME. Return only matches dated before or on this date time.
destination
String
For reporting requests. Specifying a destination makes the report "asynchronous." This means that a background job will be created to run the report and upload the final CSV file to the requested destination. The API request to start the report will return immediately with a background "job number" and the filename that will be uploaded. The supported value of "destination" is currently only "sftp" for a Secure FTP upload over SSH (as opposed to ftps, which would be a Secure FTP upload over SSL). When "destination" is specified, additional destination parameters are also required. Note that for SFTP uploads, there is a 15-minute upload timeout -- uploads that take longer (e.g., due to slow SFTP servers) will be aborted. WARNING: Multiple concurrent large asynchronous report requests will impact your database performance: reports will take longer to generate and your LuxSci services will experience degraded/slower performance.
destination_directory
String
For asynchronous reporting requests. This optional parameter will be the subdirectory to change to on the SFTP server before uploading the report CSV file. Technically speaking, this will be the argument provided to the SFTP "chdir" command.
destination_hostname
String
For asynchronous reporting requests. This will be the hostname of the SFTP server to which the report CSV file should be uploaded.
destination_password
String
For asynchronous reporting requests. This will be the password to be used for the login to the SFTP server to which the report CSV file should be uploaded.
destination_username
String
For asynchronous reporting requests. This will be the username to be used for the login to the SFTP server to which the report CSV file should be uploaded.
status
String
Specify one of enabled or disabled to retrieve only enabled or disabled users.
domain
String
Enter the name of a domain to retrieve only users whose login is in that domain.

Responses

Status: 200 - Report content


getUserSettings

Return information regarding selected user preferences and settings. Other keywords may be added in the future as the need arises.

Access control required to execute this endpoint: User Settings - Read


/perl/api/v2/user/{username}/settings

Parameters

Path parameters
Name Description
username*
String
Required
Header parameters
Name Description
Cookie

Responses

Status: 200 - The response body for a successful request will have a keywords and data in the “data” in the JSON response.


getUserSingleSignOnLoginURL

Create a URL that the user can click on which will automatically log the user into the Web Interface without needing to enter his/her username and password. For example, if the user has already authenticated himself in your system, you can use this API call to get a link that can be presented to the user so the user can then access WebMail or other services without needing to login again (e.g. “single sign-on”). Notes: 1. This API call returns a URL. You can have the user click on that URL or you can redirect him/her to it. 2. This URL is valid for 15 minutes from the time of issuance. It can be used multiple times while it is in use. 3. These URLs are invalidated if the user’s password is changed. 4. These URLs will only work for someone coming from the IP address that your specified in your request for the URL 5. If a user has a preference that permits only OpenID/Social media logins to his/her account, then this auto-login URL will not work. 6. If a user has two-factor authentication enabled, then this URL will take him through the username/password portion of the login process; however, the user will still have to do the chosen second factor. 7. All logins via Single Sign-on are logged and are denoted as Single Sign-on logins in the user’s login history report.


/perl/api/v2/user/{username}/password

Parameters

Path parameters
Name Description
username*
String
Optional. Path after the domain name to take the user to upon automatic sign in. If omitted, the default path of “/perl/member/email/messages.pl” will be used; this default takes one to view the WebMail INBOX folder. You can use this parameter to select other destinations.
Required
Header parameters
Name Description
Cookie
Query parameters
Name Description
ip*
String
Required. This must be the IPv4 IP address that the end user is currently using. The resulting login URL will only work for someone who is coming from this specific IP address.
Required

Responses

Status: 200 - Response description.


getUserSummaryReport

This report the number of users in the account, with optional date range selection by user creation date. See also [API Reporting Basics](/rest-api/reporting.html) and [report header columns in the response](/rest-api/report-responses.html#users_count).

Access control required to execute this endpoint: Account: View Reports


/perl/api/v2/account/{accountId}/users/report_count

Parameters

Path parameters
Name Description
accountId*
String
Required
Header parameters
Name Description
Cookie
Query parameters
Name Description
after_date
String
DATETIME. Return only matches dated after this date time. Format “YYYY-MM-DD HH:MM:SS” in GMT
before_date
String
DATETIME. Return only matches dated before this date time.
first_row
Integer
(Default value 0). All of the matches are sorted and numbered starting from 0. E.g. if you have 100,000 matches, these are rows 0 through 99,999. If you specify a first_row, then the returned matches will be those rows starting from that row. E.g. without a specification (or if you specify 0), you might get rows 0 through 49,999. In your next request you might specify first_row=50000 to get rows 50000 to 99,999.
from_date
String
DATETIME. Return only matches dated on or after this date time.
matches
Integer
(Default value 50000). You can set matches to any value from 0 to 50000. This sets the maximum number of matches that will be returned in response to your request. Note that if the response size starts to exceed 50MB, then the response can still include fewer than your “matches” number, to keep the response size reasonable. If you specify “0” here, then no matches will be returned; however, you will still get the information on the number of matches that there were. For asynchronous reports (ones where a destination is specified), the matches parameter is not limited to 50000, but it still defaults to 50000 if not specified. If you expect a larger number of rows, then you must explicitly approve the maximum size of the result set by setting matches appropriately. This helps prevent accidental queries that produce very larger result sets.
through_date
String
DATETIME. Return only matches dated before or on this date time.
destination
String
For reporting requests. Specifying a destination makes the report "asynchronous." This means that a background job will be created to run the report and upload the final CSV file to the requested destination. The API request to start the report will return immediately with a background "job number" and the filename that will be uploaded. The supported value of "destination" is currently only "sftp" for a Secure FTP upload over SSH (as opposed to ftps, which would be a Secure FTP upload over SSL). When "destination" is specified, additional destination parameters are also required. Note that for SFTP uploads, there is a 15-minute upload timeout -- uploads that take longer (e.g., due to slow SFTP servers) will be aborted. WARNING: Multiple concurrent large asynchronous report requests will impact your database performance: reports will take longer to generate and your LuxSci services will experience degraded/slower performance.
destination_directory
String
For asynchronous reporting requests. This optional parameter will be the subdirectory to change to on the SFTP server before uploading the report CSV file. Technically speaking, this will be the argument provided to the SFTP "chdir" command.
destination_hostname
String
For asynchronous reporting requests. This will be the hostname of the SFTP server to which the report CSV file should be uploaded.
destination_password
String
For asynchronous reporting requests. This will be the password to be used for the login to the SFTP server to which the report CSV file should be uploaded.
destination_username
String
For asynchronous reporting requests. This will be the username to be used for the login to the SFTP server to which the report CSV file should be uploaded.
status
String
Specify one of enabled or disabled to retrieve only enabled or disabled users.
domain
String
Enter the name of a domain to retrieve only users whose login is in that domain.

Responses

Status: 200 - Report content


listAllAppSpecificPassword

This command creates a list of all app-specific password/logins defined for a specific user. This command does not allow you to access the passwords themselves, as these are stored only as complex hashes on the server. A list of all defined app-specific passwords will be returned.

Access control required to execute this endpoint: User Settings - Change Password


/perl/api/v2/user/{username}/app-password

Parameters

Path parameters
Name Description
username*
String
Required
Header parameters
Name Description
Cookie

Responses

Status: 201 - The response body for a successful request will have a list as the “data” in the JSON response. Each element of the list will be the definition of one of the app-specific passwords for this user. An app specific-password definitions is a list containing 4 elements: [suffix, title, types, created, expires] The “suffix” is the login suffix we have been using; “title” is the text description; “types” is the comma-delimited list of code words that defines the access available to this login; “created” is the date and time in GMT in the format “YYYY-MM-DD HHMMSS” of when this app-specific login was created. Expires is the similar date when it expires; if this is before “2020-01-01”, then it does not expire.


listAppSpecificPasswords

This command creates a list of all app-specific password/logins defined for a specific user. This command does not allow you to access the passwords themselves, as these are stored only as complex hashes on the server. The list will contain either 0 results (if there is no app-specific password defined with that suffix), or the 1 singular result corresponding to that suffix.

Access control required to execute this endpoint: User Settings - Change Password


/perl/api/v2/user/{username}/app-password/{suffix}

Parameters

Path parameters
Name Description
username*
String
Required
suffix*
String
Required
Header parameters
Name Description
Cookie

Responses

Status: 200 - The response body for a successful request will have a list as the “data” in the JSON response. Each element of the list will be the definition of one of the app-specific passwords for this user. An appspecific-password definitions is a list containing 4 elements: [suffix, title, types, created, expires] The “suffix” is the login suffix we have been using; “title” is the text description; “types” is the comma-delimited list of code words that defines the access available to this login; “created” is the date and time in GMT in the format “YYYY-MM-DD HHMMSS” of when this app-specific login was created. Expires is the similar date when it expires; if this is before “2020-01-01”, then it does not expire.


renameUser

Change the user’s login email address from `username` to `new_address`. E.g., change `john@sample.com` to `fred@newdomain.com`. Please note the following restrictions on this command: 1. Users cannot be renamed with the API in the following situations: 1. Users with account administration permission cannot be renamed. 2. If this user is currently HIPAA compliant, s/he cannot be renamed into a domain that is not HIPAA compliant 3. If this user does not have a SecureLine license, s/he cannot be renamed into a domain that is HIPAA- ompliant 4. Users with Secure Marketing user logins associated with them cannot be renamed. 5. Users cannot be renamed from a domain that does not have Premium Email Filtering or Archival into a domain that does. 2. The new domain name (e.g. `newdomain.com`) must exist in this account. 3. The user part of the new login (e.g. `fred`) must be valid for an email address and must not correspond to an existing user or email alias. 4. Any existing PGP or S/MIME certificates associated with this user in the system will be deleted and become inaccessible, as they are explicitly related to the user’s login email address.

Access control required to execute this endpoint: Account: Users - Enable / Disable / Delete Users


/perl/api/v2/account/{accountId}/users/{username}/rename

Parameters

Path parameters
Name Description
accountId*
String
Required
username*
String
Required
Header parameters
Name Description
Cookie
Body parameters
Name Description
body

Responses

Status: 200 - none


updateUser

Update contact information for the user. Same as `updateUserProfile`.

Access control required to execute this endpoint: User Settings - Write


/perl/api/v2/user/{username}

Parameters

Path parameters
Name Description
username*
String
Required
Header parameters
Name Description
Cookie
Body parameters
Name Description
body

Responses

Status: 200 - User profile


updateUserProfile

Update contact information for the user.

Access control required to execute this endpoint: User Settings - Write


/perl/api/v2/user/{username}/profile

Parameters

Path parameters
Name Description
username*
String
Required
Header parameters
Name Description
Cookie
Body parameters
Name Description
body

Responses

Status: 200 - User profile


updateUserSettings

Change one or more properties of the user.

Access control required to execute this endpoint: Account: Users - Modify


/perl/api/v2/account/{accountId}/users/{username}

Parameters

Path parameters
Name Description
accountId*
String
Required
username*
String
Required
Header parameters
Name Description
Cookie
Body parameters
Name Description
body

Responses

Status: 200 - none


WebAides

addUpdateWebAideEntries

Add/update multiple entries of a WebAide all at once. Address Book Imports: SecureLine data can be sent in this way as well (i.e. Escrow question and answer, PGP key, S/MIME key, etc.). SecureLine data is imported if and only if the “SecureLine Mode” field is present and not empty for an entry. Any entries that are updated and for which “SecureLine Mode” is left blank, will have their existing SecureLine settings left “as-is”. Note: Each WebAide is limited to 25,000 entries by default. If your WebAide has this many entries (or more), then this AddUpdateWebAideEntries command will return an error (even if you are only intending to do updates). If you need larger WebAides, please contact support. Very large WebAides may require use of a dedicated server. See also [WebAide definitions](/rest-api/webaides.html).

Access control required to execute this endpoint: Access to that specific type of WebAides; Add/Update Accessible WebAides and Entries


/perl/api/v2/user/{username}/webaides/{webaide_type}/{webaide_id}/entries/import

Parameters

Path parameters
Name Description
username*
String
Required
webaide_type*
String
Required
webaide_id*
String
Required
Header parameters
Name Description
Cookie
Body parameters
Name Description
body

Responses

Status: 200 - The response body for a successful request will have data in the “data” in the JSON response.


deleteWebAide

Delete a WebAide of type `webaide_type` whose unique ID is `webaide_id`. This WebAide must be owned by the user in question. See also [WebAide definitions](/rest-api/webaides.html).

Access control required to execute this endpoint: Access to that specific type of WebAides; Delete Accessible WebAides and Entries


/perl/api/v2/user/{username}/webaides/{webaide_type}/{webaide_id}

Parameters

Path parameters
Name Description
username*
String
Required
webaide_type*
String
Required
webaide_id*
String
Required
Header parameters
Name Description
Cookie

Responses

Status: 200 - nothing in data.


deleteWebAideEntries

Delete multiple entries from a WebAide all at once. (Since we are not deleting an individual entity at a specific address, this is a POST instead of a DELETE method). See also [WebAide definitions](/rest-api/webaides.html).

Access control required to execute this endpoint: Access to that specific type of WebAides; Delete Accessible WebAides and Entries


/perl/api/v2/user/{username}/webaides/{webaide_type}/{webaide_id}/entries/delete

Parameters

Path parameters
Name Description
username*
String
Required
webaide_type*
String
Required
webaide_id*
String
Required
Header parameters
Name Description
Cookie
Body parameters
Name Description
body

Responses

Status: 200 - ""


deleteWebAideEntry

Delete an existing WebAide Entry. See also [WebAide definitions](/rest-api/webaides.html).

Access control required to execute this endpoint: Access to that specific type of WebAides; Delete Accessible WebAides and Entries


/perl/api/v2/user/{username}/webaides/{webaide_type}/{webaide_id}/{entry_id}

Parameters

Path parameters
Name Description
username*
String
Required
webaide_type*
String
Required
webaide_id*
String
Required
entry_id*
String
Required
Header parameters
Name Description
Cookie

Responses

Status: 200 - The response body for a successful request will have data in the “data” in the JSON response.


getCalendarEntriesDateRange

Gets a list of entries in a specified Calendar WebAide that fall within a specified range of dates. For recurring entries, the entry will be returned if any of its instances fall within the specified date range. The date range is taken to be dates in GMT. See also [WebAide definitions](/rest-api/webaides.html).

Access control required to execute this endpoint: Access to WebAide Calendars; Read Accessible WebAides and Entries


/perl/api/v2/user/{username}/webaides/calendar/{webaide_id}/entries/date_range

Parameters

Path parameters
Name Description
username*
String
Required
webaide_id*
String
Required
Header parameters
Name Description
Cookie
Query parameters
Name Description
before*
String
DATE: “YYYY-MM-DD” in GMT (where 00:00:00 GMT is implied) Required. Entries that contain events before this date.
Required
entries
String
Comma-delimited list of entry Unique IDs. e.g. “10786,77892,23”

Optional. If included, the search is restricted to only entries in this list.

Note, if you want to use a very long list of entries, you might want to use several requests so that you do not exceed the maximum URL query string size of 8190 bytes.
from*
String
DATE: “YYYY-MM-DD” in GMT (where 00:00:00 GMT is implied)

Required. Entries that contain events on or after this date.
Required

Responses

Status: 200 - The response body for a successful request will have data in the “data” in the JSON response.


getWebAide

This call is like `getWebAides`, except that the call is simplified and targeted at a specific, single WebAide. See also [WebAide definitions](/rest-api/webaides.html).

Access control required to execute this endpoint: Access to that specific type of WebAides; Read Accessible WebAides and Entries


/perl/api/v2/user/{username}/webaides/{webaide_type}/{webaide_id}

Parameters

Path parameters
Name Description
username*
String
Required
webaide_type*
String
Required
webaide_id*
String
Required
Header parameters
Name Description
Cookie
Query parameters
Name Description
changes
String
Optional. DateTime in GMT in the format: YYYY-MM-DD HH:MM:SS. If this is provided, a sub call to “GetWebAideChanges” will be made for each returned WebAide, giving you summary counts of numbers of entries and adds/updates/deletes since the specified date.

Specify an old date (e.g. “2000-01-01”) if all you care about is the total number of entries.

Use of “changes” is the recommended way to get the number of entries in one or more WebAides in an efficient manner.

Responses

Status: 200 - Results in the “data” component of the response. The result will be the same as that for `getWebAides`.


getWebAideChanges

Return all WebAide entries added, changed, or deleted since a particular time. See also [WebAide definitions](/rest-api/webaides.html).

Access control required to execute this endpoint: Access to that specific type of WebAides; Read Accessible WebAides and Entries


/perl/api/v2/user/{username}/webaides/{webaide_type}/{webaide_id}/entries/changes

Parameters

Path parameters
Name Description
username*
String
Required
webaide_type*
String
Required
webaide_id*
String
Required
Header parameters
Name Description
Cookie
Query parameters
Name Description
modified*
String
Timestamp “YYYYMMDDHHMMSS” in GMT or “YYYY-MM-DD HH:MM:SS” in GMT

Return all WebAide entries added, changed, or deleted since this timestamp. If you specify “0” here, it will return a list of all entries that exist now and all that have been deleted.
Required

Responses

Status: 200 - ""


getWebAideEntries

Retrieve the detailed contents of all WebAide entries matching a query. See also [WebAide definitions](/rest-api/webaides.html).

Access control required to execute this endpoint: Access to that specific type of WebAides; Read Accessible WebAides and Entries


/perl/api/v2/user/{username}/webaides/{webaide_type}/{webaide_id}/entries

Parameters

Path parameters
Name Description
username*
String
Required
webaide_type*
String
Required
webaide_id*
String
Required
Header parameters
Name Description
Cookie
Query parameters
Name Description
entries
array[String]
Optional. Comma-delimited list of entry Unique IDs. e.g. “10786,77892,23”. If included, the search is restricted to only entries in this list. Note, if you want to use a very long list of entries, you might want to use several requests so that you do not exceed the maximum URL query string size of 8190 bytes.
limit
Integer
Optional. Integer 1 to 500. How many entries to return (maximum). Default is 500.
resume
Integer
Integer:1 or 0. If 0 (the default), begin a new search. If 1, continue the previous search. When returning successive “pages” or entries, use resume for faster and more consistent results.
secureline
Integer
Integer 1 or 0 If specified as ‘1’, SecureLine-specific Address Book fields are included in the export. I.e., this includes the SecureLine Escrow Question/Answer pair and/or PGP and S/MIME public keys.
showcomplete
Integer
Integer 1 or 0 If specified as ‘1’, get completed tasks for ‘Tasks’ WebAides. By default, only uncompleted tasks are returned.
sort
String
Optional method by which the returned entries should be sorted.
start
Integer
Optional. The default is 0. Index in the list of all entries from which to start the result set. Use this to return successive “pages” of entries.
timezone
String
Time zone code. The time zone to use for Calendar/Task dates and times. The user’s default time zone is used if no time zone is specified.

Responses

Status: 200 - The response body for a successful request will have data in the “data” in the JSON response.


getWebAideEntry

Retrieve the detailed contents of a specific WebAide entry. See also [WebAide definitions](/rest-api/webaides.html).

Access control required to execute this endpoint: Access to that specific type of WebAides; Read Accessible WebAides and Entries


/perl/api/v2/user/{username}/webaides/{webaide_type}/{webaide_id}/{entry_id}

Parameters

Path parameters
Name Description
username*
String
Required
webaide_type*
String
Required
webaide_id*
String
Required
entry_id*
String
Required
Header parameters
Name Description
Cookie

Responses

Status: 200 - data contains the entry details as a object. See webaide entry data fields for the field names and meanings of the fields returned.


getWebAides

Return a list of all WebAides accessible to the specified user, that are also of the indicated type. You can use the query string to add filters to narrow down the results. See also [WebAide definitions](/rest-api/webaides.html).

Access control required to execute this endpoint: Access to that specific type of WebAides; Read Accessible WebAides and Entries


/perl/api/v2/user/{username}/webaides/{webaide_type}

Parameters

Path parameters
Name Description
username*
String
Required
webaide_type*
String
Required
Header parameters
Name Description
Cookie
Query parameters
Name Description
subscribed
String
Filter by WebAide subscription status
  • all - select all
  • subscribed - return those subscribed
  • unsubscribed - return those not subscribed
  • tosync - return those tagged for synchronization with MobileSync.
ids
array[String]
List of the numerical WebAide IDs eligible to be returned.
permissions
array[String]
Values can include those in the webaide_permission list. Select only WebAides where the user has all of the indicated permissions
modified
String
DateTime in GMT in the format: YYYY-MM-DD HH:MM:SS. Return all WebAides that have had any entry created, deleted, or modified on or after this date and time. Values can include those in the webaide_permission list.
changes
String
Optional. DateTime in GMT in the format: YYYY-MM-DD HH:MM:SS. If this is provided, a sub call to “GetWebAideChanges” will be made for each returned WebAide, giving you summary counts of numbers of entries and adds/ updates/deletes since the specified date.

Specify an old date (e.g. “2000-01-01”) if all you care about is the total number of entries.

Use of “changes” is the recommended way to get the number of entries in one or more WebAides in an efficient manner.

Responses

Status: 200 - The response body for a successful request will have a list of objects as the “data” in the JSON response.


newWebAide

Create a new WebAide of type webaide_type. E.g. creation of a new “Address Book”. Note: Each user is limited to 500 WebAides of each type. Trying to create more will result in an error being returned. See also [WebAide definitions](/rest-api/webaides.html).

Access control required to execute this endpoint: Access to that specific type of WebAides; Add/Update Accessible WebAides and Entries


/perl/api/v2/user/{username}/webaides/{webaide_type}

Parameters

Path parameters
Name Description
username*
String
Required
webaide_type*
String
Required
Header parameters
Name Description
Cookie
Body parameters
Name Description
body

Responses

Status: 200 - The response body for a successful request will have data in the “data” in the JSON response.


newWebAideEntry

Create a new WebAide Entry. Note that invalid fields may simply be ignored, rather than generate an actual error. E.g. an invalid “E-mail Address” field will simply result in that field being omitted in the new entry. We recommend that you validate your own data and not rely on request errors to do the validation for you. Note: Each WebAide is limited to 25,000 entries by default. If your WebAide has this many entries (or more), then this NewWebAideEntry command will return an error. If you need larger WebAides, please contact support. Very large WebAides may require the use of a dedicated server. See also [WebAide definitions](/rest-api/webaides.html).

Access control required to execute this endpoint: Access to that specific type of WebAides; Add/Change Accessible WebAides and Entries


/perl/api/v2/user/{username}/webaides/{webaide_type}/{webaide_id}

Parameters

Path parameters
Name Description
username*
String
Required
webaide_type*
String
Required
webaide_id*
String
Required
Header parameters
Name Description
Cookie
Body parameters
Name Description
body

Responses

Status: 200 - The response body for a successful request will have data in the “data” in the JSON response.


updateWebAideEntry

Update an existing WebAide Entry. This function will replace the data in all entry fields with the new data supplied. It is recommended that you retrieve the complete entry, alter it, and then update it – so that you update does not delete data from an entry simply because you did not include those fields in your update. File attachments on entries are unaffected by this command. See also [WebAide definitions](/rest-api/webaides.html).

Access control required to execute this endpoint: Access to that specific type of WebAides; Add/Change Accessible WebAides and Entries


/perl/api/v2/user/{username}/webaides/{webaide_type}/{webaide_id}/{entry_id}

Parameters

Path parameters
Name Description
username*
String
Required
webaide_type*
String
Required
webaide_id*
String
Required
entry_id*
String
Required
Header parameters
Name Description
Cookie
Body parameters
Name Description
body

Responses

Status: 200 - The response body for a successful request will have data in the “data” in the JSON response.