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.
See also Authentication.
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. This function allows you to check this without actually sending a message to these recipients.
Note that in order to issue API commands that access a particular kind of WebAide (e.g. Calendars), your API Interface must he enabled to access that type of WebAide in the API Interface access control area. E.g., your API Interface could be configured so it can only access Calendars and not Tasks or any of the others. Similarly, it could have only Read access to specific types of WebAides.
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.
Return details for a specific asynchronous reporting job.
Administrative functions for managing users and user logins. Note that administrators can also employ user-scope user API endpoints to further manage and modify users (e.g., to change a user's password).
Customers with Private Labeling and SecureLine may choose to setup NameSpace(s) to associate with their Private Labeled themes. These NameSpaces segregate the SecureSend users of these themes from the SecureSend users of other themes and of other LuxSci customers. These functions allow you to manage the users in a particular SecureSend NameSpace in your account.
You need your “namespace id” number to use these functions. This can be found in the “SecureSend User NameSpaces” page accessible in your Private Labeling configuration area. These API functions only permit you to manage users in NameSpaces in your account.
The LuxSci Secure Marketing API is a subset of the LuxSci Account API
with commands specifically for the LuxSci Secure Marketing system. Secure
Marketing API commands are “account” scope.
The API functions described herein allow your API client to
programmatically access, insert, add, update and delete resources
effectively within LuxSci Secure Marketing platform. This means you can
perform functions programmatically on specific contacts, contact lists,
and statistics automatically from third-party applications or custom code.
Linking the API to your Secure Marketing Login(s)
In order to use the LuxSci Secure Marketing API commands, you need to link
your API configuration to a specific user in the Secure Marketing
interface. The API commands will then operate through that user on that
user’s data and with that user’s level of access to the system.
To do this, you need to make a support ticket in the LuxSci web
interface requesting that this operation be performed for you.
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.
Returns details on the posts currently stored in the database table associated with a specific Secure Form 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).
This report allows you to retrieve specific current status of a specific server.
There are many reports available in the LuxSci user interface. Some
of these are account-wide and some are the same reports, but restricted to
a particular user's activity.
Access to all of these reports is very similar. They all use an HTTP
GET; account-wide reports use account scope; similar user-specific reports
are available under user scope. All reports use the same mechanism for
restricting date ranges and requesting particular "pages" of results. The
following section specifies the usage features common to all of these
report types. The subsequent sections discuss each of the particular
account scope reports available. See the User Reports
section for a list of the respective user-scope reports.