The CData Sync App provides a straightforward way to continuously pipeline your SendGrid data to any database, data lake, or data warehouse, making it easily available for Analytics, Reporting, AI, and Machine Learning.
The SendGrid connector can be used from the CData Sync application to pull data from SendGrid and move it to any of the supported destinations.
The Sync App models the SendGrid Web API as a relational database.
For required properties, see the Settings tab.
For connection properties that are not typically required, see the Advanced tab.
You must use an API key to authenticate through the SendGrid Sync App.
To obtain an API key, follow the steps below:
NOTE: If you want access to Email events, you must purchase the Email Activity History add-in of SendGrid. If using a Restricted Access key, you must give it the messages.read and email_activity.read scopes.
This section details a selection of advanced features of the SendGrid Sync App.
The Sync App supports the use of user defined views, virtual tables whose contents are decided by a pre-configured user defined query. These views are useful when you cannot directly control queries being issued to the drivers. For an overview of creating and configuring custom views, see User Defined Views .
Use SSL Configuration to adjust how Sync App handles TLS/SSL certificate negotiations. You can choose from various certificate formats;. For further information, see the SSLServerCert property under "Connection String Options" .
Configure the Sync App for compliance with Firewall and Proxy, including Windows proxies and HTTP proxies. You can also set up tunnel connections.
For further information, see Query Processing.
By default, the Sync App attempts to negotiate TLS with the server. The server certificate is validated against the default system trusted certificate store. You can override how the certificate gets validated using the SSLServerCert connection property.
To specify another certificate, see the SSLServerCert connection property.
To authenticate to an HTTP proxy, set the following:
Set the following properties:
The Sync App models SendGrid APIs as relational tables, views, and stored procedures. Most tables, views, and stored procedures are defined in schema files, which are simple, text-based configuration files.
However, the Recipients table is dynamic: The Sync App connects to SendGrid and gets the metadata for this table by calling the appropriate Web services. Any changes you make to the custom filters you define for Recipients are available when you connect; you can use these custom filters as columns in the WHERE clause. These custom filters are surfaced in the CustomFields table.
The Sync App uses the SendGrid API to process supported filters. The Sync App processes other filters client-side within the Sync App.
See New Marketing Campaigns Data Model for the available entities in the New Marketing Campaigns API.
See Legacy Data Model for the available entities in the Legacy API.
The CData Sync App models the New Marketing Campaigns API as relational tables, views, and stored procedures. Most tables, views, and stored procedures are defined in schema files, which are simple, text-based configuration files. The Sync App uses the SendGrid API to process supported filters. The Sync App processes other filters client-side within the Sync App.
To use the New Marketing Campaigns Data Model, simply set Schema to NMC.
Tables describes the available tables that are easy to query and update.
Views are tables that cannot be modified. Typically, read-only data are shown as views.
Stored Procedures are function-like interfaces to Sendgrid. They can be used to search, update, and modify information.
The Sync App models the data in SendGrid as a list of tables in a relational database that can be queried using standard SQL statements.
| Name | Description |
| Alerts | Create, update, delete, and query Alerts in SendGrid. |
| ApiKeys | Query, Create, Update and Delete the available ApiKeys in SendGrid. |
| Blocks | Query and Delete the available Blocks in SendGrid. |
| Bounces | Query and Delete the available Bounces in SendGrid. |
| CancelScheduledSends | Update, delete, and query Cancel Scheduled Sends in SendGrid. |
| GlobalUnsubscribes | Query Global Unsubscribes in SendGrid. |
| InvalidEmails | Query and Delete invalid emails in SendGrid. |
| NMCCustomFields | Create, delete, and query New Marketing Campaign Custom Fields in SendGrid. |
| NMCLists | Create, update, delete, and query the available New Marketing Campaign Lists in SendGrid. |
| NMCSegments | Create, update, delete, and query New Marketing Campaign Segments in SendGrid. |
| NMCSenders | Create, update, delete, and query New Marketing Campaign Senders in SendGrid. |
| NMCSingleSends | Create, update, delete, and query the available New Marketing Campaign Single Sends in SendGrid. |
| Spam | Query and delete Spam reports in SendGrid. |
| Teammates | Query Teammates in SendGrid. |
| UnsubscribeGroups | Create, update, delete, and query Unsubscribe Groups in SendGrid. |
| Users | Query the available Users in SendGrid. |
Create, update, delete, and query Alerts in SendGrid.
This table only supports filtering by Id. The following are the only possible SELECT queries:
SELECT * FROM Alerts SELECT * FROM Alerts WHERE Id = '148825'
The following columns are required in an insert for Stats Notification: Type, EmailTo, Frequency.
INSERT INTO Alerts (Type, EmailTo, Frequency) VALUES ('stats_notification', '[email protected]', 'daily')
The following columns are required in an insert for Usage Limit: Type, EmailTo, Percentage.
INSERT INTO Alerts (Type, EmailTo, Percentage) VALUES ('usage_limit', '[email protected]', 20)
You can only update EmailTo by specifying an Id.
UPDATE Alerts SET EmailTo = '[email protected]' WHERE Id = 1310789
You can only delete from Alerts by specifying an Id.
DELETE FROM Alerts WHERE Id = 1310789
| Name | Type | ReadOnly | References | Description |
| Id [KEY] | Integer | True |
The ID of the alert. | |
| CreatedAt | Datetime | True |
Date when the alert was created. | |
| UpdatedAt | Datetime | True |
Date when the alert was updated. | |
| EmailTo | String | False |
The email address that the alert will be sent to. | |
| Percentage | Integer | False |
The email address that the alert will be sent to. | |
| Type | String | False |
The type of alert. Allowed values (usage_limit, stats_notification). | |
| Frequency | String | False |
If the alert is of type stats_notification, this indicates how frequently the stats notifications will be sent.(daily, weekly, monthly). |
Pseudo column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.
| Name | Type | Description |
| AccountId | String |
The ID of the account. |
| SubuserUsername | String |
The username of the subuser. |
Query, Create, Update and Delete the available ApiKeys in SendGrid.
To get all the Api Keys
SELECT * FROM ApiKeys
To get information about a specific Api Key
SELECT * FROM Apikeys WHERE ApiKeyId = 'Dqdvdvdvdv4yLeuVQqO3rFxN5ktUxA'
The following columns are required in an insert: Name.
VALUES for Scopes are:
alerts.create, alerts.read, alerts.update, alerts.delete, asm.groups.create, asm.groups.read, asm.groups.update, asm.groups.delete, ips.pools.ips.read, mail.send, mail_settings.bcc.read, mail_settings.bcc.update, mail_settings.address_whitelist.read, mail_settings.address_whitelist.update, mail_settings.footer.read,
mail_settings.footer.update, mail_settings.forward_spam.read, mail_settings.forward_spam.update, mail_settings.plain_content.read, mail_settings.plain_content.update, mail_settings.spam_check.read, mail_settings.spam_check.update, mail_settings.bounce_purge.read, mail_settings.bounce_purge.update, mail_settings.forward_bounce.read,
mail_settings.forward_bounce.update, partner_settings.new_relic.read, partner_settings.new_relic.update, partner_settings.sendwithus.read, partner_settings.sendwithus.update, tracking_settings.click.read, tracking_settings.click.update, tracking_settings.subscription.read, tracking_settings.subscription.update, tracking_settings.open.read,
tracking_settings.open.update, tracking_settings.google_analytics.read, tracking_settings.google_analytics.update, user.webhooks.event.settings.read, user.webhooks.event.settings.update, user.webhooks.event.test.create, user.webhooks.event.test.read, user.webhooks.event.test.update, user.webhooks.parse.settings.create, user.webhooks.parse.settings.read,
user.webhooks.parse.settings.update, user.webhooks.parse.settings.delete, stats.read, stats.global.read, categories.stats.read, categories.stats.sums.read, devices.stats.read, clients.stats.read, clients.phone.stats.read, clients.tablet.stats.read, clients.webmail.stats.read, clients.desktop.stats.read, geo.stats.read, mailbox_providers.stats.read,
browsers.stats.read, user.webhooks.parse.stats.read, templates.create, templates.read, templates.update, templates.delete, templates.versions.create, templates.versions.read, templates.versions.update, templates.versions.delete, templates.versions.activate.create, user.timezone.read, user.timezone.update, user.settings.enforced_tls.read, user.settings.enforced_tls.update,
api_keys.create, api_keys.read, api_keys.update, api_keys.delete, email_activity.read, categories.create, categories.read, categories.update, categories.delete, mail_settings.template.read, mail_settings.template.update, marketing_campaigns.create, marketing_campaigns.read, marketing_campaigns.update, marketing_campaigns.delete, mail.batch.create, mail.batch.read, mail.batch.update,
mail.batch.delete, user.scheduled_sends.create, user.scheduled_sends.read, user.scheduled_sends.update, user.scheduled_sends.delete, access_settings.whitelist.create, access_settings.whitelist.read, access_settings.whitelist.update, access_settings.whitelist.delete, access_settings.activity.read, whitelabel.create, whitelabel.read, whitelabel.update, whitelabel.delete, suppression.create,
suppression.read, suppression.update, suppression.delete, messages.read
INSERT INTO Apikeys (Name) VALUES ('apiname')
INSERT INTO Apikeys (Name, Scopes, Sample) VALUES ('apiname', 'alerts.create,alerts.read', 'test')
You can update ApiKeys by specifying an ApiKeyid.You need to specify both the name and the scopes during the UPDATE even if you don't want to update it.
UPDATE Apikeys SET Name = 'apiname2', Scopes = 'alerts.create,alerts.read' WHERE apikeyid = 'Dqdvdvdvdv4yLeuVQqO3rFxN5kscsctUxA-P_Q'
You can Delete ApiKeys by specifying an ApiKeyid.
DELETE FROM ApiKeys WHERE apikeyid = 'CMp4C8klscscscsQ0GxqvxtK2-P_Q'
| Name | Type | ReadOnly | References | Description |
| ApiKeyId [KEY] | String | False |
The ID of your API Key. | |
| Name | String | False |
The name of your API Key. | |
| Scopes | String | False |
The permissions this API Key has access to. This is populated only when Id is specified. |
Pseudo column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.
| Name | Type | Description |
| AccountId | String |
The ID of the account. |
| SubuserUsername | String |
The username of the subuser. |
Query and Delete the available Blocks in SendGrid.
You need to specify a time span to select from this table. If you do not specify one, a default span of the past 120 days is used. The CreatedAt column supports the >, <, =, <=, and >= operators.
SELECT * FROM Blocks WHERE CreatedAt > '2016-01-01' AND CreatedAt < '2016-01-30'
You can only delete from Blocks by specifying an Email.
DELETE FROM Blocks WHERE Email = '[email protected]'
| Name | Type | ReadOnly | References | Description |
| CreatedAt | Datetime | True |
The time the block was created. | |
| Reason | String | False |
The reason for the block. | |
| Email [KEY] | String | False |
The email that blocked. | |
| Status | String | False |
The enhanced SMTP block response. |
Pseudo column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.
| Name | Type | Description |
| AccountId | String |
The ID of the account. |
| SubuserUsername | String |
The username of the subuser. |
Query and Delete the available Bounces in SendGrid.
You need to specify a time span to select from this table. If you do not specify one, a default span of the past 120 days is used. The CreatedAt column supports the >, <, =, <=, and >= operators.
SELECT * FROM Bounces WHERE CreatedAt > '2016-01-01' AND CreatedAt < '2016-01-30'
You can only delete from Bounces by specifying an Email.
DELETE FROM Bounces WHERE Email = '[email protected]'
| Name | Type | ReadOnly | References | Description |
| CreatedAt | Datetime | True |
The time the bounce was created. | |
| Reason | String | False |
The reason for the bounce. | |
| Email [KEY] | String | False |
The email that bounced. | |
| Status | String | False |
The enhanced SMTP bounce response. |
Pseudo column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.
| Name | Type | Description |
| AccountId | String |
The ID of the account. |
| SubuserUsername | String |
The username of the subuser. |
Update, delete, and query Cancel Scheduled Sends in SendGrid.
This table only supports filtering by BatchId. The following are the only possible SELECT queries:
SELECT * FROM CancelScheduledSends SELECT * FROM CancelScheduledSends WHERE BatchId = 148825
You can update CancelScheduledSends by specifying an BatchId.
Allowed Values : cancel, pause
UPDATE CancelScheduledSends SET Status = 'cancel' WHERE BatchId = 1310789
You can only delete from CancelScheduledSends by specifying an BatchId.
DELETE FROM CancelScheduledSends WHERE BatchId = 1310789
| Name | Type | ReadOnly | References | Description |
| BatchId [KEY] | String | False |
The Id of the batch. | |
| Status | String | False |
The status of the scheduled send.Allowed Values: cancel, pause |
Pseudo column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.
| Name | Type | Description |
| AccountId | String |
The ID of the account. |
| SubuserUsername | String |
The username of the subuser. |
Query Global Unsubscribes in SendGrid.
You need to specify a time span to select from this table. However this filter is optional. The CreatedAt column supports the >, <, =, <=, and >= operators.
SELECT * FROM GlobalUnsubscribes WHERE CreatedAt > '2016-01-01' AND CreatedAt < '2016-01-30'
Performing an Insert operation in this table you need to specify an email which will be added to the GlobalUnsubscribes list. For example:
INSERT INTO GlobalUnsubscribes (Email) VALUES ('[email protected]')
Performing a Delete operation in this table you need to specify an email which will be removed from the GlobalUnsubscribes list. For example:
DELETE FROM GlobalUnsubscribes WHERE Email = '[email protected]'
| Name | Type | ReadOnly | References | Description |
| Email [KEY] | String | False |
Email of the unsubscriber. | |
| CreatedAt | Datetime | True |
The time the unsubscriber was created. |
Pseudo column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.
| Name | Type | Description |
| AccountId | String |
The ID of the account. |
| SubuserUsername | String |
The username of the subuser. |
Query and Delete invalid emails in SendGrid.
This table only supports filtering by Email. The following are the only possible SELECT queries:
SELECT * FROM InvalidEmails SELECT * FROM InvalidEmails WHERE Email = '[email protected]'
You can only delete from InvalidEmails by specifying an Email.
DELETE FROM InvalidEmails WHERE Email = '[email protected]'
| Name | Type | ReadOnly | References | Description |
| Created | Datetime | True |
The time the when the email address was added to the invalid emails list. | |
| Reason | String | False |
A reason explaining why the email address was marked as invalid.. | |
| Email [KEY] | String | False |
The email address that was marked as invalid. |
Pseudo column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.
| Name | Type | Description |
| AccountId | String |
The ID of the account. |
| SubuserUsername | String |
The username of the subuser. |
Create, delete, and query New Marketing Campaign Custom Fields in SendGrid.
New Marketing Campaign Custom fields are filters for a Contact that are defined by the user. NMC prefix stands for New Marketing Campaign.
You can retrieve all the NMCCustomFields or filter them by Id:
SELECT * FROM NMCCustomFields WHERE Id = '1'
Use quotations to filter on NMC Custom Fields regardless of type.
To insert on NMCCustomFields specify the Name of the field and its Type. The Type can be text, date, or number.
INSERT INTO NMCCustomFields (name, type) VALUES ('age', 'number')
UPDATE NMCCustomFields SET name = 'updated name' WHERE Id = '123'
You can only delete from NMCCustomFields by specifying an Id:
DELETE FROM NMCCustomFields WHERE Id = '1'
| Name | Type | ReadOnly | References | Description |
| Id [KEY] | String | True |
The Id of the custom field. | |
| Name | String | False |
The name of the custom field. | |
| Type | String | False |
The type of the custom field. Allowed values are number, text, or date. |
Create, update, delete, and query the available New Marketing Campaign Lists in SendGrid.
NMC prefix stands for New Marketing Campaign.
The NMCLists table can only filtered by its Id.
SELECT * FROM NMCLists WHERE Id = '123'
Only the Name for the NMCLists is required to insert into this table.
INSERT INTO NMCLists (Name) VALUES ('TestList')
You can only update from NMCLists by specifying an Id.
UPDATE NMCLists SET Name = 'New Name' WHERE Id = '123'
You can only delete from NMCLists by specifying an Id.
DELETE FROM NMCLists WHERE Id = '123'
| Name | Type | ReadOnly | References | Description |
| Id [KEY] | String | True |
The Id of the list. | |
| Name | String | False |
The name of the list. | |
| ContactCount | Integer | True |
The recipient count of the list. | |
| ItemUrl | String | True |
The URL of the List Item. |
Create, update, delete, and query New Marketing Campaign Segments in SendGrid.
NMC prefix stands for New Marketing Campaign.
You can retrieve all the segments or filter them by Id.
SELECT * FROM NMCSegments WHERE Id = '1'
A Segment divides NMCContacts by certain criteria. To specify these criteria use the QueryDSL filter.
INSERT INTO NMCSegments (Name, QueryDSL) VALUES ("New Segment", "Segment Cdata", "first_name LIKE '%test%'"))
The statement above creates NMCSegments containing NMCContacts with FirstName containing the value "test".
You can update the name or the conditions. Since the whole set will be overwritten, specify a full set.
UPDATE NMCSegments SET Name = "Name Updated", QueryDSL = "first_name LIKE '%test update%'" WHERE Id = '123'
You can only delete NMCSegments by Id:
DELETE FROM NMCSegments WHERE Id = '123'
| Name | Type | ReadOnly | References | Description |
| Id [KEY] | String | True |
The Id of the segment. | |
| Name | String | False |
The name of the segment. | |
| ParentListId | String | False |
The Id of the list associated with the segment. | |
| ContactsCount | Integer | True |
The recipient count of the segment. | |
| CreatedAt | Datetime | True |
Field name for the first condition. | |
| SampleUpdatedAt | Datetime | False |
Field name for the first condition. | |
| UpdatedAt | Datetime | True |
Field name for the first condition. | |
| QueryDSL | String | False |
Field name for the first condition. | |
| NextSampleUpdate | Datetime | True |
The last updated samples date. | |
| ItemUrl | String | True |
The URL of the Segment item. | |
| ContactSampleAggregate | String | True |
The aggregate of the contact sample. |
Create, update, delete, and query New Marketing Campaign Senders in SendGrid.
NMC stands for New Marketing Campaign.
This table only supports filtering by Id. The following are the only possible SELECT queries:
SELECT * FROM NMCSenders SELECT * FROM NMCSenders WHERE Id = '148825'
The following columns are required in an insert: Nickname, FromEmail, FromName, ReplytoEmail, Address, City, Country.
INSERT INTO NMCSenders (Nickname, FromEmail, FromName, ReplytoEmail, Address, City, Country) VALUES ('Nickname', 'FromEmail', 'FromName', 'ReplytoEmail', 'Address', 'City', 'Country')
You can update NMCSenders by specifying an Id.
UPDATE NMCSenders SET Nickname = 'Nickname', FromEmail = 'FromEmail', FromName = 'FromName', ReplytoEmail = 'ReplytoEmail', Address = 'Address', City = 'City', Country = 'Country' WHERE Id = 1310789
You can only delete from Alerts by specifying an Id.
DELETE FROM NMCSenders WHERE Id = 1310789
| Name | Type | ReadOnly | References | Description |
| Id [KEY] | Integer | True |
The unique identifier of the sender identity. | |
| Nickname | String | False |
A nickname for the sender identity. Not used for sending.. | |
| FromEmail | String | False |
This is where the email will appear to originate from for your recipient. | |
| FromName | String | False |
This is the name appended to the from email field. IE - Your name or company name. | |
| ReplytoEmail | String | False |
This is the email that your recipient will reply to. | |
| ReplytoName | String | False |
This is the name appended to the reply to email field. IE - Your name or company name. | |
| Address | String | False |
The physical address of the sender identity. | |
| Address2 | String | False |
Additional sender identity address information. | |
| City | String | False |
The city of the sender identity. | |
| State | String | False |
The state of the sender identity. | |
| Zip | String | False |
The zipcode of the sender identity. | |
| Locked | String | True |
Indicator if the sender is locked. | |
| VerifiedStatus | String | True |
Verified status of the sender. | |
| VerifiedReason | String | True |
Verified reason of the sender. | |
| Country | String | False |
The country of the sender identity. | |
| CreatedAt | Datetime | True |
The end of the time range when the bounce was created. | |
| UpdatedAt | Datetime | True |
The end of the time range when the bounce was created. |
Pseudo column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.
| Name | Type | Description |
| AccountId | String |
The ID of the account. |
| SubuserUsername | String |
The username of the subuser. |
Create, update, delete, and query the available New Marketing Campaign Single Sends in SendGrid.
NMC stands for New Marketing Campaign.
This table only supports filtering by Id. The following are the only possible SELECT queries:
SELECT * FROM NMCSingleSends SELECT * FROM NMCSingleSends WHERE Id = '148825'
The following columns are required in an insert: Name.
INSERT INTO NMCSingleSends (Name) VALUES ('SingleSend Name')
You can update NMCSingleSends by specifying an Id.
UPDATE NMCSingleSends SET Name = 'SingleSend Updated' WHERE Id = 1310789
You can only delete from NMCSingleSends by specifying an Id.
DELETE FROM NMCSingleSends WHERE Id = 1310789
| Name | Type | ReadOnly | References | Description |
| Id [KEY] | String | True |
The Id of the single send. | |
| Name | String | False |
The name of the single send. | |
| Categories | String | False |
The name of the single send. | |
| Status | String | False |
The status of the single send. | |
| CreatedAt | String | True |
The created timestamp of the single send. | |
| UpdatedAt | String | True |
The updated timestamp of the single send. | |
| IsABTest | Boolean | False |
Indicator showing if the single send is an AB Test. | |
| SendAt | Datetime | False |
The ISO 8601 time at which to send the single send. | |
| EmailConfigCustomUnsubscribeUrl | String | False |
The URL allowing recipients to unsubscribe. | |
| EmailConfigEditor | String | False |
The editor, design or code, used to modify the Single Send's design in the Marketing Campaigns application user interface. This is populated only when Id is specified. | |
| EmailConfigGeneratePlainContent | Boolean | False |
If this property is set to true, plain_content is always generated from html_content. If it's set to false, plain_content is not altered. This is populated only when Id is specified. | |
| EmailConfigHtmlContent | String | False |
The HTML content of the Single Send. This property is not used when a design_id value is set. This is populated only when Id is specified. | |
| EmailConfigIpPool | String | False |
The name of the IP Pool from which the Single Send emails are sent. This is populated only when Id is specified. | |
| EmailConfigPlainContent | String | False |
The plain text content of the Single Send. This is populated only when Id is specified. | |
| EmailConfigSenderId | Integer | False |
The ID of the verified sender from whom the Single Send will be sent. This is populated only when Id is specified. | |
| EmailConfigSubject | String | False |
The subject line of the Single Send. This is populated only when Id is specified. | |
| EmailConfigSuppressionGroupId | Integer | False |
The ID of the Suppression Group to allow recipients to unsubscribe. This is populated only when Id is specified. | |
| SendToListIds | String | False |
The IDs of each contact list to which the Single Send will be sent. This is populated only when Id is specified. | |
| SendToSegmentIds | String | False |
The IDs of each segment to which the Single Send will be sent. This is populated only when Id is specified. | |
| SendToAll | Boolean | False |
If this property is set to true, the Single Send will be sent to all of your contacts. This is populated only when Id is specified. | |
| ItemUrl | String | True |
The URL of the Single Send Item. |
Query and delete Spam reports in SendGrid.
This table only supports filtering by Email. The following are the only possible SELECT queries:
SELECT * FROM Spam SELECT * FROM Spam WHERE Email = '[email protected]'
Delete from Spam
You can delete from Spam by specifying an Email.
DELETE FROM Spam WHERE Email = '[email protected]'
| Name | Type | ReadOnly | References | Description |
| CreatedAt | Datetime | True |
The time when the spam report was made. | |
| Email [KEY] | String | False |
The email address of the recipient who marked your message as spam. | |
| Ip | String | False |
The IP address that the message was sent on. |
Pseudo column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.
| Name | Type | Description |
| AccountId | String |
The ID of the account. |
| SubuserUsername | String |
The username of the subuser. |
Query Teammates in SendGrid.
For example, the following queries are processed server side:
SELECT * FROM Teammates WHERE Username = 'test'
SELECT * FROM Teammates WHERE Username IN ('test', 'test2')
The following columns are required in an insert: Email and Scopes. Scopes column accepts a comma separated list of values. The accepted values are: user.account.read, user.credits.read, user.email.create, user.email.read, user.email.update, user.email.delete, user.profile.create, user.profile.read, user.profile.update, user.profile.delete.
The IsAdmin is optional and by default is accepted as false from the API.
INSERT INTO Teammates (Email, Scopes) VALUES ('[email protected]', 'user.profile.read,user.profile.update')
INSERT INTO Teammates (Email, Scopes, IsAdmin) VALUES ('[email protected]', 'user.profile.read,user.profile.update', 'true')
The following columns are required in an update: Username and Scopes. Scopes column accepts a comma separated list of values. The accepted values are: user.account.read, user.credits.read, user.email.create, user.email.read, user.email.update, user.email.delete, user.profile.create, user.profile.read, user.profile.update, user.profile.delete.
UPDATE Teammates SET Scopes = 'user.profile.read' WHERE Username = 'testuser'
Only the username column is required to delete a record from Teammates table. For example:
DELETE FROM Teammates WHERE Username = 'testuser'
| Name | Type | ReadOnly | References | Description |
| Username [KEY] | String | False |
The username of the teammate. | |
| String | False |
Email of the teammate. | ||
| FirstName | String | False |
First name of the teammate. | |
| LastName | String | False |
Last name of the teammate. | |
| UserType | String | False |
User type of the teammate. | |
| IsAdmin | Boolean | False |
Indicator if the teammate is admin. | |
| Phone | String | False |
Phone of the teammate. | |
| Website | String | False |
Website of the teammate. | |
| Company | String | False |
Company of the teammate. | |
| Address | String | False |
Address of the teammate. | |
| Address2 | String | False |
Address 2 of the teammate. | |
| City | String | False |
City of the teammate. | |
| State | String | False |
State of the teammate. | |
| Country | String | False |
Country of the teammate. | |
| Zip | String | False |
Zip of the teammate. | |
| Scopes | String | False |
Scope of the permissions for the new teammate. Multiple values are allowed and should be split by a comma symbol. Possible values are: user.account.read,user.credits.read,user.email.create,user.email.read,user.email.update,user.email.delete,user.profile.create,user.profile.read,user.profile.update,user.profile.delete | |
| IsPartnerSSO | Boolean | False |
Indicator if the teammate partner is SSO. | |
| IsSSO | Boolean | False |
Indicator if the teammate is SSO. | |
| IsUnified | Boolean | False |
Indicator if the teammate is unified. |
Pseudo column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.
| Name | Type | Description |
| AccountId | String |
The ID of the account. |
| SubuserUsername | String |
The username of the subuser. |
Create, update, delete, and query Unsubscribe Groups in SendGrid.
UnsubscribeGroups can only be filtered by Id.
SELECT * FROM UnsubscribeGroups WHERE Id = '1'
Provide a Name and a Description to insert into UnsubscribeGroups:
INSERT INTO UnsubscribeGroups (Name, Description, IsDefault) VALUES ('Unsubscribe1', 'General Unsubscribe', true)
You can only update UnsubscribeGroups by specifying an Id.
UPDATE UnsubscribeGroups SET Name = 'New Name', Description = 'New Description' WHERE Id = '1'
You can only delete from UnsubscribeGroups by specifying an Id.
DELETE FROM UnsubscribeGroups WHERE Id = '1'
| Name | Type | ReadOnly | References | Description |
| Id [KEY] | Integer | True |
Id of the unsubscribe group. | |
| Name | String | False |
The name of the unsubscribe group. | |
| Description | String | False |
The description of the unsubscribe group. | |
| LastEmailSentAt | Datetime | True |
The last time an email was sent to the unsubscribe group. | |
| IsDefault | Boolean | False |
If the unsubscribe group is the default group or not. | |
| Unsubscribes | Integer | True |
The number of unsubscribes from this group. |
Pseudo column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.
| Name | Type | Description |
| AccountId | String |
The ID of the account. |
| SubuserUsername | String |
The username of the subuser. |
Query the available Users in SendGrid.
Query this table to retrieve your current profile details.
SELECT * FROM Users
You can update the all the columns marked as readonly false.
UPDATE Users Set Address='Milpitas', Address2='North Carolina' WHERE id='38713966'
| Name | Type | ReadOnly | References | Description |
| Id [KEY] | String | True |
The Id of the user. | |
| Address | String | False |
The address of the user. | |
| Address2 | String | False |
The secondary address field for the user. | |
| City | String | False |
The city of the user. | |
| Company | String | False |
The company of the user. | |
| Country | String | False |
The country of the user. | |
| FirstName | String | False |
The first name of the user. | |
| LastName | String | False |
The last name of the user. | |
| Phone | String | False |
The phone number of the user. | |
| State | String | False |
The state the user is located in. | |
| Website | String | False |
The Web site URL of the user. | |
| Zip | String | False |
The ZIP code of the user. | |
| String | True |
The Email Address of the user. | ||
| Type | String | True |
The type of the user. |
Pseudo column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.
| Name | Type | Description |
| AccountId | String |
The ID of the account. |
| SubuserUsername | String |
The username of the subuser. |
Views are similar to tables in the way that data is represented; however, views are read-only.
Queries can be executed against a view as if it were a normal table.
| Name | Description |
| AutomationStats | Get All Automation Stats |
| Categories | Query the available Categories in SendGrid. |
| CategoryStats | Query the available Category Stats in SendGrid. |
| Designs | List Designs |
| DynamicTemplates | Query Teammates in SendGrid. |
| GlobalStats | Query the available Global Stats in SendGrid. |
| GroupSuppressions | Query group suppressions in SendGrid. |
| IPAccessManagement | Query Global Unsubscribes in SendGrid. |
| MailSettings | Query all the mail settings in SendGrid. |
| MessageEvents | List of events related to email message in SendGrid. |
| Messages | Query Email Activities in SendGrid. |
| NMCContacts | Query New Marketing Campaign Contacts in SendGrid. |
| NMCReservedFields | Query the available New Marketing Campaign Reserved Fields in SendGrid. |
| NMCSegmentsContacts | Query New Marketing Campaign Segments Contacts sample in SendGrid. |
| PartnerSettings | Query all the partner settings in SendGrid. |
| SingleSendClickTrackingStats | Retrieves Single Send click tracking statistics by Id. |
| SingleSendsStats | Get all Single Sends statistics. |
| StatsByBrowser | Query Browser Statistics in SendGrid. |
| StatsByClient | Query Client Statistics in SendGrid. |
| StatsByDevice | Query Device Statistics in SendGrid. |
| StatsByLocation | Query Location Statistics in SendGrid. |
| StatsByMailboxProvider | Query Mailbox Provider Statistics in SendGrid. |
| Subusers | Query all the subusers in sendgrid. |
| SubuserStats | Query Subuser Statistics in SendGrid. |
| Templates | Retrieve paged transactional templates |
Get All Automation Stats
The following is an example to query the AutomationStats view:
SELECT * FROM AutomationStats
| Name | Type | References | Description |
| Id | String | This is the ID of the Automation you are requesting stats for. | |
| Aggregation | String | This describes the time unit to which the stat is rolled up. It is based on the aggregated_by parameter included in the request. It can be 'total' or the date (in YYYY-MM-DD format) the stats are for. | |
| StepId | String | This is the ID of the step if the stats were requested to be grouped by step_id. | |
| BounceDrops | Integer | BounceDrops | |
| Bounces | Integer | Bounces | |
| Clicks | Integer | Clicks | |
| Delivered | Integer | Delivered | |
| InvalidEmails | Integer | InvalidEmails | |
| Opens | Integer | Opens | |
| Requests | Integer | Requests | |
| SpamReportDrops | Integer | SpamReportDrops | |
| SpamReports | Integer | SpamReports | |
| UniqueClicks | Integer | UniqueClicks | |
| UniqueOpens | Integer | UniqueOpens | |
| Unsubscribes | Integer | Unsubscribes |
Query the available Categories in SendGrid.
Query this table to get available categories in SendGrid.
SELECT * FROM Categories
| Name | Type | References | Description |
| Name | String | The name of the categories. |
Pseudo column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.
| Name | Type | Description | |
| AccountId | String | The ID of the account. | |
| SubuserUsername | String | The username of the subuser. |
Query the available Category Stats in SendGrid.
The following is an example to query the CategoryStats view:
SELECT * FROM CategoryStats WHERE Name = 'news'
You can also filter by Date. If you do not specify one, a default span of the past 1 year is used. The operators =, >=, <=, <, and > are supported for this column.
SELECT * FROM CategoryStats WHERE Name = 'news' AND Date > '2016-01-01' AND Date < '2016-01-30'
| Name | Type | References | Description |
| Type | String | The type of the statistic. | |
| Name | String | The name of the category. | |
| Date | Date | The time the global statistic was created. | |
| Blocks | Integer | The number of emails that were not allowed to be delivered by ISPs. | |
| Drops | Integer | The number of emails automatically dropped by SendGrid because they appear on one of the suppression lists. | |
| Bounces | Integer | The number of emails that bounced instead of being delivered. | |
| Clicks | Integer | The number of links clicked in your emails. | |
| Deferred | Integer | The number of emails temporarily refused by the receiving server. | |
| Delivered | Integer | The number of emails confirmed delivered. | |
| InvalidEmails | Integer | The number of emails with a malformed address or reported as invalid by the receiving server. | |
| Opens | Integer | The number of times your emails were opened by recipients. | |
| Processed | Integer | The number of emails pushed to SendGrid. | |
| Requests | Integer | The number of emails you requested to send via SendGrid. | |
| SpamReportDrops | Integer | The number of emails automatically dropped because the emails were marked as spam by the recipients. | |
| SpamReports | Integer | The number of emails marked as spam by recipients. | |
| UniqueClicks | Integer | The number of unique recipients who clicked links in your emails. | |
| UniqueOpens | Integer | The number of unique recipients who opened your emails. | |
| UnsubscribeDrops | Integer | The number of emails in this category dropped by SendGrid because the recipient unsubscribed from your emails. | |
| Unsubscribes | Integer | The number of recipients who unsubscribed from your emails. |
Pseudo column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.
| Name | Type | Description | |
| AccountId | String | The ID of the account. | |
| SubuserUsername | String | The username of the subuser. |
List Designs
The following is an example to query the Designs view:
SELECT * FROM Designs SELECT * FROM Designs WHERE ID = 'd0ceee19-e773-403b-a72c-8d7c58ec6065'
| Name | Type | References | Description |
| Id [KEY] | String | ID of the Design. | |
| UpdatedAt | String | Datetime that Design was last updated. | |
| CreatedAt | String | Datetime that Design was created. | |
| ThumbnailURL | String | A Thumbnail preview of the template's html content. | |
| Name | String | The name of the new design. | |
| Editor | String | The editor used in the UI. | |
| ItemUrl | String | The URL of the Design Item. | |
| Subject | String | The subject of the Design Item. | |
| GeneratePlainContent | Boolean | Indicates whether plain content is to be generated. |
Query Teammates in SendGrid.
| Name | Type | References | Description |
| Id [KEY] | String | The ID of the template. | |
| Name | String | Name of the template. | |
| Generation | String | Generation of the template. (dynamic) | |
| UpdatedAt | Datetime | The last time the template was updated. |
Query the available Global Stats in SendGrid.
You need to specify a time span to select from this table. If you do not specify one, a default span of the past 1 year is used. The Date column supports the >, <, =, <=, and >= operators.
SELECT * FROM GlobalStats
SELECT * FROM GlobalStats WHERE Date > '2016-01-01' AND Date < '2016-03-30'
| Name | Type | References | Description |
| Date | Date | The time the global statistic was created. | |
| Blocks | Integer | The number of emails that were not allowed to be delivered by ISPs. | |
| BounceDrops | Integer | The number of emails automatically dropped by SendGrid because they appear on one of the suppression lists. | |
| Bounces | Integer | The number of emails that bounced instead of being delivered. | |
| Clicks | Integer | The number of links clicked in your emails. | |
| Deferred | Integer | The number of emails temporarily refused by the receiving server. | |
| Delivered | Integer | The number of emails confirmed delivered. | |
| InvalidEmails | Integer | The number of emails with a malformed address or reported as invalid by the receiving server. | |
| Opens | Integer | The number of times your emails were opened by recipients. | |
| Processed | Integer | The number of emails pushed to SendGrid. | |
| Requests | Integer | The number of emails you requested to send via SendGrid. | |
| SpamReportDrops | Integer | The number of emails automatically dropped because the emails were marked as spam by the recipients. | |
| SpamReports | Integer | The number of emails marked as spam by recipients. | |
| UniqueClicks | Integer | The number of unique recipients who clicked links in your emails. | |
| UniqueOpens | Integer | The number of unique recipients who opened your emails. | |
| UnsubscribeDrops | Integer | The number of emails globally dropped by SendGrid because the recipient unsubscribed from your emails. | |
| Unsubscribes | Integer | The number of recipients who unsubscribed from your emails. |
Pseudo column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.
| Name | Type | Description | |
| AccountId | String | The ID of the account. | |
| SubuserUsername | String | The username of the subuser. |
Query group suppressions in SendGrid.
The following are examples to query the GroupSuppressions table:
SELECT * FROM GroupSuppressions WHERE GroupId = 391 SELECT * FROM GroupSuppressions WHERE GroupId IN (391, 392, 393)
| Name | Type | References | Description |
| GroupId [KEY] | Integer | Email of the unsubscriber. | |
| Emails | String | The time the unsubscriber was created. |
Pseudo column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.
| Name | Type | Description | |
| AccountId | String | The ID of the account. | |
| SubuserUsername | String | The username of the subuser. |
Query Global Unsubscribes in SendGrid.
Only the following query is processed server side:
SELECT * FROM IPAccessManagement
| Name | Type | References | Description |
| IP | String | IP Address. | |
| Allowed | Boolean | Indicator if this IP is allowed for access. | |
| AuthMethod | String | Authentication method. | |
| FirstAt | Timestamp | First time when IP has accessed the account. | |
| LastAt | Timestamp | Last time when IP has accessed the account. | |
| Location | String | Location of the IP. |
Pseudo column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.
| Name | Type | Description | |
| AccountId | String | The ID of the account. | |
| SubuserUsername | String | The username of the subuser. |
Query all the mail settings in SendGrid.
You can retrieve all the mail settings.
SELECT * FROM MailSettings
| Name | Type | References | Description |
| Title | String | The title of the mail setting. | |
| Enabled | String | Indicates if this mail setting is currently enabled. | |
| Name | String | The name of the mail setting. | |
| Description | String | A description of the mail setting. |
Pseudo column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.
| Name | Type | Description | |
| AccountId | String | The ID of the account. | |
| SubuserUsername | String | The username of the subuser. |
List of events related to email message in SendGrid.
NOTE: If you want access to Email events, you must purchase the Email Activity History add-in of SendGrid. If using a Restricted Access key, you must give it the messages.read and email_activity.read scopes.
SELECT * FROM MessageEvents WHERE MessageId = '1234'
NOTE: The query below will return message events only for the first 1000 message IDs retrieved from the messages endpoint.
SELECT * FROM MessageEvents;
| Name | Type | References | Description |
| MessageId | String | The Id of the message. | |
| EventName | String | Name of event.
The allowed values are bounced, opened, clicked, processed, dropped, delivered, deferred, spam_report, unsubscribe, group_unsubscribe, group_resubscribe. | |
| Processed | Datetime | The date when the event was processed. | |
| Reason | String | Explanation of what caused the message to be 'bounced', 'deferred', or 'blocked'. | |
| AttemptNum | Integer | Used with 'deferred' events to indicate the attempt number out of 10. | |
| Url | String | Used with 'clicked' event to indicate which url the user clicked. | |
| BounceType | String | Use to distinguish between types of bounces.
The allowed values are soft, hard. | |
| HttpUserAgent | String | Client recipient used to click or open message. | |
| MXServer | String | The MX server that received the email. | |
| ApiKeyId | String | Id of the API Key. | |
| AsmGroupId | String | ASM Group Id. | |
| Categories | String | Categories users associated to the message. | |
| UniqueArgs | String | JSON hash of key-value pairs associated with the message. | |
| OriginatingIp | String | This is the IP address of the person sending the message | |
| OutboundIp | String | This is the SendGrid dedicated IP address used to send the email | |
| OutboundIpType | String | The type of the outbound IP. | |
| Teammate | String | Username of the teammate. | |
| TemplateId | String | Template ID of the email. |
Query Email Activities in SendGrid.
NOTE: If you want access to Email activities, you must purchase the Email Activity History add-in of SendGrid. If using a Restricted Access key, you must give it the messages.read and email_activity.read scopes.
Note: The API will return only 1000 records. Please choose from the available filters to restrict the search.
For example, the following queries are processed server side:
SELECT * FROM Messages WHERE Id = '1234'
SELECT * FROM Messages WHERE Id IN ('1234', '4567')
SELECT * FROM Messages WHERE Status = 'not_delivered'
SELECT * FROM Messages WHERE LastEventTime BETWEEN '2020-01-01' AND '2020-01-15'
NOTE: Pagination is not available on this view. Any query—whether filtered or not—will return a maximum of 1000 records. If your filtered query matches more than 1000 records, only the first 1000 will be returned.
| Name | Type | References | Description |
| Id [KEY] | String | The Id of the message. | |
| Status | String | Status of the email. | |
| Subject | String | Subject of the email. | |
| FromEmail | String | The email of the sender. | |
| ToEmail | String | The email of the receiver. | |
| ClicksCount | Integer | The number of clicks. | |
| OpensCount | Integer | The number of times that the email was opened. | |
| LastEventTime | Datetime | The datetime of the event. | |
| ApiKeyId | String | Id of the API Key. | |
| AsmGroupId | String | ASM Group Id. | |
| MarketingCampaignId | String | The id of the marketing campaign. | |
| MarketingCampaignName | String | The name of the marketing campaign. | |
| MarketingCampaignSplitId | String | Split id of the campaign. | |
| MarketingCampaignVersion | String | Version of the campaign. | |
| OriginatingIp | String | This is the IP address of the person sending the message | |
| OutboundIp | String | This is the SendGrid dedicated IP address used to send the email | |
| OutboundIpType | String | The type of the outbound IP. | |
| Teammate | String | Username of the teammate. | |
| TemplateId | String | Template ID of the email. | |
| Events | String | List of events related to email message in SendGrid. |
Query New Marketing Campaign Contacts in SendGrid.
New Marketing Campaign contacts are recepients that are managed by the user. NMC prefix stands for New Marketing Campaign.
You can retrieve all the NMCContacts or filter them by Id, ListId or SegmentId:
SELECT * FROM NMCCustomFields WHERE Id = 'pe37d765-ba38-46d9-be55-1e45a1ee8c84'
SELECT * FROM NMCCustomFields WHERE Id IN ('pe37d765-ba38-46d9-be55-1e45a1ee8c84', 'fe37d765-ba38-46d9-be55-1e45a1ee8c84')
SELECT * FROM NMCCustomFields WHERE ListId = 't6d51a34-3981-4fa6-bd3f-abdd4de8ff9f'
SELECT * FROM NMCCustomFields WHERE ListId IN ('j6d51a34-3981-4fa6-bd3f-abdd4de8ff9f', 'f6d51b34-3981-4fa6-bd3f-abdd4de8ff9f')
SELECT * FROM NMCCustomFields WHERE SegmentId = '82aeee2d-2870-41e4-b43c-0dcf63481589'
SELECT * FROM NMCCustomFields WHERE SegmentId IN ('82aeee2d-2870-41e4-b43c-0dcf63481589', 'j9d51a34-3981-4fa6-bd3f-abdd4de8ff9f')
| Name | Type | References | Description |
| Id [KEY] | String | This column is dynamic and maps to the corresponding field in the API. | |
| AddressLine1 | String | This column is dynamic and maps to the corresponding field in the API. | |
| AddressLine2 | String | This column is dynamic and maps to the corresponding field in the API. | |
| City | String | This column is dynamic and maps to the corresponding field in the API. | |
| Country | String | This column is dynamic and maps to the corresponding field in the API. | |
| PostalCode | String | This column is dynamic and maps to the corresponding field in the API. | |
| StateProvinceRegion | String | This column is dynamic and maps to the corresponding field in the API. | |
| Line | String | This column is dynamic and maps to the corresponding field in the API. | |
| String | This column is dynamic and maps to the corresponding field in the API. | ||
| PhoneNumber | String | This column is dynamic and maps to the corresponding field in the API. | |
| UniqueName | String | This column is dynamic and maps to the corresponding field in the API. | |
| String | This column is dynamic and maps to the corresponding field in the API. | ||
| String | This column is dynamic and maps to the corresponding field in the API. | ||
| FirstName | String | This column is dynamic and maps to the corresponding field in the API. | |
| LastName | String | This column is dynamic and maps to the corresponding field in the API. | |
| CreatedAt | Datetime | This column is dynamic and maps to the corresponding field in the API. | |
| UpdatedAt | Datetime | This column is dynamic and maps to the corresponding field in the API. | |
| ItemUrl | String | This column is dynamic and maps to the corresponding field in the API. |
Pseudo column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.
| Name | Type | Description | |
| SegmentId | String | This column is dynamic and maps to the corresponding field in the API. | |
| ListId | Uuid | This column is dynamic and maps to the corresponding field in the API. |
Query the available New Marketing Campaign Reserved Fields in SendGrid.
This table does not support filtering. NMC prefix stands for New Marketing Campaign.
SELECT * FROM NMCReservedFields
| Name | Type | References | Description |
| Id | String | The Id of the reserved field. | |
| Name | String | The name of the reserved field. | |
| Type | String | The type of the reserved field. |
Query New Marketing Campaign Segments Contacts sample in SendGrid.
| Name | Type | References | Description |
| Id [KEY] | String | The Id of the contact sample. | |
| String | The email of the contact sample. | ||
| FirstName | String | The first name of the contact sample. | |
| LastName | String | The last name of the contact sample. | |
| NMCSegmentId | String |
NMCSegments.Id | Segment id of the contacts table. |
Query all the partner settings in SendGrid.
You can retrieve all the partner settings.
SELECT * FROM PartnerSettings
| Name | Type | References | Description |
| Title | String | The title of the partner. | |
| Enabled | String | Indicates if this partner setting has been enabled. | |
| Name | String | The name of the partner setting. | |
| Description | String | A description of this partner setting. |
Pseudo column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.
| Name | Type | Description | |
| AccountId | String | The ID of the account. | |
| SubuserUsername | String | The username of the subuser. |
Retrieves Single Send click tracking statistics by Id.
Get Single Send Click Tracking statistics. To access the view, you need to provide the Single Send ID.
SELECT * FROM SingleSendClickTrackingStats where SingleSendId = '74550809-66a2-11ef-ad7f-460f539623db'
| Name | Type | References | Description |
| SingleSendId | String | The Id of Single Send for which you want to retrieve click tracking statistics. | |
| Url | String | The URL of the link clicked. If {{custom_fields}} are part of the URL, they are included. | |
| UrlLocation | Integer | The location of the link clicked in each Single Send A/B variation, or if there are no variations, the Single Send itself. Links are numbered from the top down; the topmost link is index 0. | |
| ABvariation | String | The A/B variation of the Single Send statistic returned. It is set to 'all' if the ab_variation query parameter was not set in the request and group_by does not contain ab_variation. | |
| ABphase | String | The A/B phase of the Single Send statistic returned. If the ab_phase query parameter was not provided, it returns 'all'. | |
| Clicks | Integer | The number of clicks on this particular link. |
Get all Single Sends statistics.
The Sync App uses the SendGrid API to process search criteria that refer to the Id column, while other filters are processed client side within the Sync App.
Get all Single Sends statistics:
SELECT * FROM SingleSendsStats
Get Single Send statistics by ID:
SELECT * FROM SingleSendsStats where id = '25723e10-669e-11ef-b50f-0e4b6974e9ad'
| Name | Type | References | Description |
| Id [KEY] | String | The ID of the Single Send you require stats for. | |
| ABvariation | String | The A/B variation of the Single Send statistic returned. If the group_by parameter doesn't include ab_variation in the request, then the value is 'all'. | |
| ABphase | String | This is the A/B phase of the Single Send statistic returned. If the group_by parameter doesn't include ab_phase in the request, then the value is 'all'. | |
| Aggregation | String | The time unit to which the statistic is rolled up. It is based on the aggregated_by parameter included in the request. It can be 'total' or the date (in YYYY-MM-DD format) the statistics are for. | |
| BounceDrops | Integer | The number of dropped messages due to previous bounces. | |
| Bounces | Integer | The number of email messages that bounced (not delivered to recipients). | |
| Clicks | Integer | The total number of times links in the email were clicked. | |
| Delivered | Integer | The total number of messages successfully delivered to recipient inboxes. | |
| InvalidEmails | Integer | The number of email addresses that were invalid or did not exist. | |
| Opens | Integer | The total number of times the email was opened. | |
| Requests | Integer | The total number of email send requests made for the Single Send campaign. | |
| SpamReportDrops | Integer | The number of messages not sent because recipients previously marked your emails as spam. | |
| SpamReports | Integer | The number of times recipients reported the email as spam. | |
| UniqueClicks | Integer | The number of unique recipients who clicked at least one link in the email. | |
| UniqueOpens | Integer | The number of unique recipients who opened the email at least once. | |
| Unsubscribes | Integer | The number of recipients who unsubscribed using the unsubscribe link in the email. |
Query Browser Statistics in SendGrid.
You need to specify a time span to select from this table. If you do not specify one, a default span of the past 1 year is used. The Date column supports the >, <, =, <=, and >= operators.
If any date within the specified range has statistical data, the API will include that data in the resultset and return 0 for other dates. If no dates have non-zero stats within the specified date range, the API will return an empty result set.
SELECT * FROM StatsByBrowser WHERE Date > '2016-01-01' AND Date < '2016-03-30'
To query Browser Statistics by name.
SELECT * FROM StatsByBrowser WHERE Name = 'Firefox'
| Name | Type | References | Description |
| Type | String | The type of the statistic. | |
| Name | String | The name of the statistic. | |
| Date | Date | The time the global statistic was created. | |
| Clicks | Integer | The number of links clicked in your emails. | |
| UniqueClicks | Integer | The number of unique recipients who clicked links in your emails. |
Pseudo column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.
| Name | Type | Description | |
| AccountId | String | The ID of the account. | |
| SubuserUsername | String | The username of the subuser. |
Query Client Statistics in SendGrid.
You need to specify a time span to select from this table. If you do not specify one, a default span of the past 1 year is used. The Date column supports the >, <, =, <=, and >= operators.
If any date within the specified range has statistical data, the API will include that data in the resultset and return 0 for other dates. If no dates have non-zero stats within the specified date range, the API will return an empty result set.
SELECT * FROM StatsByClient WHERE Date > '2016-01-01' AND Date < '2016-03-30'
To query Client Statistics by name.
SELECT * FROM StatsByClient WHERE Name = 'Other'
| Name | Type | References | Description |
| Type | String | The type of the statistic. | |
| Name | String | The name of the statistic. | |
| Date | Date | The time the global statistic was created. | |
| Opens | Integer | The number of times your emails were opened by recipients. | |
| UniqueOpens | Integer | The number of unique recipients who opened your emails. |
Pseudo column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.
| Name | Type | Description | |
| AccountId | String | The ID of the account. | |
| SubuserUsername | String | The username of the subuser. |
Query Device Statistics in SendGrid.
You need to specify a time span to select from this table. If you do not specify one, a default span of the past 1 year is used. The Date column supports the >, <, =, <=, and >= operators.
If any date within the specified range has statistical data, the API will include that data in the resultset and return 0 for other dates. If no dates have non-zero stats within the specified date range, the API will return an empty result set.
SELECT * FROM StatsByDevice WHERE Date > '2016-01-01' AND Date < '2016-03-30'
To query Device Statistics by name.
SELECT * FROM StatsByDevice WHERE Name = 'Phone'
| Name | Type | References | Description |
| Type | String | The type of the statistic. | |
| Name | String | The name of the statistic. | |
| Date | Date | The time the global statistic was created. | |
| Opens | Integer | The number of times your emails were opened by recipients. | |
| UniqueOpens | Integer | The number of unique recipients who opened your emails. |
Pseudo column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.
| Name | Type | Description | |
| AccountId | String | The ID of the account. | |
| SubuserUsername | String | The username of the subuser. |
Query Location Statistics in SendGrid.
You need to specify a time span to select from this table. If you do not specify one, a default span of the past 1 year is used. The Date column supports the >, <, =, <=, and >= operators.
If any date within the specified range has statistical data, the API will include that data in the resultset and return 0 for other dates. If no dates have non-zero stats within the specified date range, the API will return an empty result set.
SELECT * FROM StatsByLocation WHERE Date > '2016-01-01' AND Date < '2016-03-30'
To query Location Statistics by name.
SELECT * FROM StatsByLocation WHERE Name = 'US'
To query Location Statistics by type.
SELECT * FROM StatsByLocation WHERE Type = 'country'
| Name | Type | References | Description |
| Type | String | The type of the statistic. | |
| Name | String | The name of the statistic. | |
| Date | Date | The time the global statistic was created. | |
| Clicks | Integer | The number of links clicked in your emails. | |
| Opens | Integer | The number of times your emails were opened by recipients. | |
| UniqueClicks | Integer | The number of unique recipients who clicked links in your emails. | |
| UniqueOpens | Integer | The number of unique recipients who opened your emails. |
Pseudo column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.
| Name | Type | Description | |
| AccountId | String | The ID of the account. | |
| SubuserUsername | String | The username of the subuser. |
Query Mailbox Provider Statistics in SendGrid.
You need to specify a time span to select from this table. If you do not specify one, a default span of the past 1 year is used. The Date column supports the >, <, =, <=, and >= operators.
If any date within the specified range has statistical data, the API will include that data in the resultset and return 0 for other dates. If no dates have non-zero stats within the specified date range, the API will return an empty result set.
SELECT * FROM StatsByMailboxProvider WHERE Date > '2016-01-01' AND Date < '2016-03-30'
To query Mailbox Provider Statistics by name.
SELECT * FROM StatsByMailboxProvider WHERE Name = 'Microsoft Outlook Live'
| Name | Type | References | Description |
| Type | String | The type of the statistic. | |
| Name | String | The name of the statistic. | |
| Date | Date | The time the global statistic was created. | |
| Blocks | Integer | The number of emails that were not allowed to be delivered by ISPs. | |
| Drops | Integer | The number of emails automatically dropped by SendGrid because they appear on one of the suppression lists. | |
| Bounces | Integer | The number of emails that bounced instead of being delivered. | |
| Clicks | Integer | The number of links clicked in your emails. | |
| Deferred | Integer | The number of emails temporarily refused by the receiving server. | |
| Delivered | Integer | The number of emails confirmed delivered. | |
| Opens | Integer | The number of times your emails were opened by recipients. | |
| Processed | Integer | The number of emails pushed to SendGrid. | |
| Requests | Integer | The number of emails you requested to send via SendGrid. | |
| SpamReports | Integer | The number of emails marked as spam by recipients. | |
| UniqueClicks | Integer | The number of unique recipients who clicked links in your emails. | |
| UniqueOpens | Integer | The number of unique recipients who opened your emails. |
Pseudo column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.
| Name | Type | Description | |
| AccountId | String | The ID of the account. | |
| SubuserUsername | String | The username of the subuser. |
Query all the subusers in sendgrid.
Query this table to retrieve all subusers.
SELECT * FROM Subusers
You can filter by Username to retrieve a specific subuser.
SELECT * FROM Subusers WHERE Username = 'Example'
| Name | Type | References | Description |
| Id | Integer | The Id of the subuser. | |
| String | The email of the subuser. | ||
| Username | String | The username of the subuser. | |
| Disabled | Boolean | Indicates whether the subuser is enabled or disabled. |
Query Subuser Statistics in SendGrid.
You can filter by SubuserName to retrieve stats of a specific subuser.
SELECT * FROM SubuserStats WHERE SubuserName = 'Example'
You can also filter by Date. Operators =, >=, <=, <, and > are supported for this column. If you do not specify one, a default span of the past 1 year is used.
SELECT * FROM SubuserStats WHERE SubuserName = 'News' AND Date > '2016-01-01' AND Date < '2016-01-30'
| Name | Type | References | Description |
| Date | Date | The time the subuser statistic was created. | |
| Blocks | Integer | The number of emails that were not allowed to be delivered by ISPs. | |
| Drops | Integer | The number of emails automatically dropped because they appear on one of the suppression lists. | |
| Bounces | Integer | The number of emails that bounced instead of being delivered. | |
| Clicks | Integer | The number of links that were clicked in the emails from this subuser. | |
| Deferred | Integer | The number of emails temporarily refused by the receiving server. | |
| Delivered | Integer | The number of emails from this subsuer that were confirmed delivered. | |
| InvalidEmails | Integer | The number of emails with a malformed address or reported as invalid by the receiving server. | |
| Opens | Integer | The number of times emails from this subuser were opened by recipients. | |
| Processed | Integer | The number of emails pushed to SendGrid by this subuser. | |
| Requests | Integer | The number of emails that you requested to send via SendGrid from this subuser. | |
| SpamReportDrops | Integer | The number of emails automatically dropped because the emails were marked as spam by the recipients. | |
| SpamReports | Integer | The number of emails from this subuser that were marked as spam by recipients. | |
| UniqueClicks | Integer | The number of unique recipients who clicked on links in your emails from this subuser. | |
| UniqueOpens | Integer | The number of unique recipients who opened your emails from this subuser. | |
| UnsubscribeDrops | Integer | The number of emails from this subuser dropped by SendGrid because the recipients unsubscribed from your emails. | |
| Unsubscribes | Integer | The number of recipients who unsubscribed from your emails from this subuser. | |
| SubuserName | String | The name of the statistic. | |
| Type | String | The type of the statistic. |
Retrieve paged transactional templates
The following is an example to query the Templates view:
SELECT * FROM Templates
The Sync App will use the SendGrid API to process WHERE clause conditions built with the following column and operator.
SELECT * FROM Templates WHERE Generation = 'dynamic'
| Name | Type | References | Description |
| ID [KEY] | String | The ID of the transactional template. | |
| Generation | String | Defines the generation of the template. By default, we will get data for both dynamic and legacy.
The allowed values are dynamic, legacy. | |
| Name | String | The name for the transactional template. | |
| UpdatedAt | String | The date and time that this transactional template version was updated. | |
| Versions | String | The different versions of this transactional template. |
Stored procedures are function-like interfaces that extend the functionality of the Sync App beyond simple SELECT/INSERT/UPDATE/DELETE operations with SendGrid.
Stored procedures accept a list of parameters, perform their intended function, and then return any relevant response data from SendGrid, along with an indication of whether the procedure succeeded or failed.
| Name | Description |
| AddRecipientToList | Adds a recipient to a list. |
| GetImportContactsStatus | Gets the Import contacts status |
| GetScopes | Returns a list of all scopes that this user has access to. |
| ImportMarketingContacts | Import contacts to sendgrid account from CSV file. |
| SendMail | Sends a mail. |
| SendMail2 | Sends a mail. This Stored Procedure is used to handle aggregates. |
| SendTestCampaign | Sends a test campaign. |
Adds a recipient to a list.
| Name | Type | Required | Description |
| ListId | String | True | The unique identifier for the list. |
| RecipientId | String | True | The Id of the recipient. |
| AccountId | String | False | The ID of the account. |
| SubuserUsername | String | False | The username of the subuser. |
| Name | Type | Description |
| Success | String | Whether or not the recipient was successfully added to the list. |
Download Marketing Campaign Stats for Automations
The DownloadCampaignAutomationStats Stored Procedure requires CampaignID and the DownloadTo parameters to download the campaign automation stats in specific folder.
For Example:
EXEC DownloadCampaignAutomationStats Campaignid= 3091688, DownloadTo= 'C:\dev\tests\v20\ProviderSendGrid\'
| Name | Type | Required | Description |
| CampaignID | String | True | Comma seperated list of campaignIds. |
| Timezone | String | False | TimeZone of the location. |
| DownloadTo | String | False | Where to store the file. |
| Encoding | String | False | The FileData input encoding type.
The allowed values are NONE, BASE64. The default value is BASE64. |
| Name | Type | Description |
| Success | String | Whether or not the campaign was downloaded successfully. |
| FileData | String | If the DownloadTo and FileStream are not provided, this contains the content of the file. |
Gets the Import contacts status
The GetImportContactsStatus Stored Procedure requires JobId of the Import Contacts, which we can get by executing ImportMarketingContacts stored procedure.
Example:
EXEC GetImportContactsStatus JobId= '1234'
| Name | Type | Required | Description |
| JobId | String | True | The Id of the Import Contacts Job |
| Name | Type | Description |
| Success | String | The Staus of the corresponding Import Contacts Job. |
| RequestedCount | String | The Number of contacts requested to modify through API. |
| CreatedCount | String | The Number of contacts created. |
| UpdatedCount | String | The Number of Updated contacts. |
| DeletedCount | String | The Number of Deleted contacts. |
Returns a list of all scopes that this user has access to.
| Name | Type | Required | Description |
| AccountId | String | False | The Id of the account on whose behalf the call is made. |
| SubuserUsername | String | False | The username of the Subuser on whose behalf the call is made. |
| Name | Type | Description |
| Scopes | String | List of all scopes. |
Import contacts to sendgrid account from CSV file.
The ImportMarketingContacts Stored Procedure requires Field Mapping Ids and path of the File which contains contacts data.
We can Use custom_field ids or reserved_field ids for Field Mapping and We can get these ids using "Get All Field Definitions" endpoint.
NOTE:
1. Email field mapping is mandatory to import contacts from file.
2. As of now only csv file format is supported for this operation.
Example:
EXEC ImportMarketingContacts FileType= 'csv' , FieldMappings= '_rf2_T,_rf9_T' , FilePath = 'C:\Dev\Tests\v20\ProviderSendgrid\example.csv'
| Name | Type | Required | Description |
| FileType | String | False | The type of the file
The allowed values are csv. |
| FieldMappings | String | True | Comma separated list of field_definition IDs |
| ListIds | String | False | Comma separated list of List id's |
| FilePath | String | False | The absolute path of the File to import contacts |
| Name | Type | Description |
| JobId | String | The Id of the Import Contacts Job |
Sends a mail.
The DynamicTemplateData input requires information about dynamic data of the template. Value for the different variables put into templates.
Example: {"fullname":"Test","paymenttotal":"Test","description":"Test"}
NOTE: The TemplateId column is required when using Dynamic Templates.
SendMail Requires atleast one personalizations object in the request body and it can be added using the aggregate function.
For Example:
Using TEMP Tables.
INSERT INTO To#TEMP (ToEmail, ToName) VALUES ('[email protected]', 'abc')
INSERT INTO To#TEMP (ToEmail, ToName) VALUES ('[email protected]', 'xyz')
INSERT INTO To#TEMP (ToEmail) VALUES ('[email protected]')
INSERT INTO ToCC#TEMP (ToCCName, ToCCEmail) VALUES ('[email protected]', 'xyz')
INSERT INTO ToBCC#TEMP (ToBCCEmail, ToBCCName) VALUES ('[email protected]', 'abc')
INSERT INTO Content#TEMP (ContentValue, ContentType) VALUES ('[email protected]', 'text/plain')
INSERT INTO Personalizations#TEMP (FromEmail, SendAt, FromName, Subject, To, ToCC, ToBCC) VALUES ('[email protected]', '2017-10-30T10:57:00+01:00', 'hi', 'Test Subject2', 'To#TEMP', 'ToCC#TEMP', 'ToBCC#TEMP')
EXEC SendMail Personalizations = 'Personalizations#TEMP', FromEmail = '[email protected]', Subject = 'hello', Content = 'Content#TEMP'
Using Aggregate values.
Send Mail to single Mail Address.
INSERT INTO Personalizations#TEMP (FromEmail, SendAt, FromName, Subject, To, ToCC, ToBCC) VALUES ('[email protected]', '2017-10-30T10:57:00+01:00', 'hi', 'Test Subject2',
'[
{
"ToEmail": "[email protected]",
"ToName": "abc"
}
]',
'[
{
"ToCCName": "xyz",
"ToCCEmail": "[email protected]"
}
]',
'[
{
"ToBCCEmail": "[email protected]",
"ToBCCName": "abcd"
}
]')
EXEC SendMail Personalizations = 'Personalizations#TEMP', FromEmail = '[email protected]', Subject = 'hello', Content =
'{
"ContentValue":"content",
"ContentType":"text/plain"
}'
Send Mail to Multiple Mail Addresses.
INSERT INTO Personalizations#TEMP (FromEmail, SendAt, FromName, Subject, To, ToCC, ToBCC) VALUES ('[email protected]', '2017-10-30T10:57:00+01:00', 'hi', 'Test Subject2',
'[
{
"ToEmail": "[email protected]",
"ToName": "abc"
},
{
"ToEmail": "[email protected]",
"ToName": "xyz"
},
{
"ToEmail": "[email protected]"
}
]',
'[
{
"ToCCName": "sac",
"ToCCEmail": "[email protected]"
}
]',
'[
{
"ToBCCEmail": "xyz",
"ToBCCName": "[email protected]"
}
]')
EXEC SendMail Personalizations = 'Personalizations#TEMP', FromEmail = '[email protected]', Subject = 'hello', Content =
'{
"ContentValue":"content",
"ContentType":"text/html"
}'
Send Mail using attachment.
INSERT INTO To#TEMP (ToEmail, ToName) VALUES ('[email protected]', 'abc')
INSERT INTO To#TEMP (ToEmail, ToName) VALUES ('[email protected]', 'xyz')
INSERT INTO To#TEMP (ToEmail) VALUES ('[email protected]')
INSERT INTO ToCC#TEMP (ToCCName, ToCCEmail) VALUES ('[email protected]', 'xyz')
INSERT INTO ToBCC#TEMP (ToBCCEmail, ToBCCName) VALUES ('[email protected]', 'abc')
INSERT INTO Content#TEMP (ContentValue, ContentType) VALUES ('[email protected]', 'text/plain')
INSERT INTO Attachments#TEMP (AttachmentContent, AttachmentFilename) VALUES ('abcdefghijklmn', 'Test2.png')
INSERT INTO Personalizations#TEMP (FromEmail, SendAt, FromName, Subject, To, ToCC, ToBCC) VALUES ('[email protected]', '2017-10-30T10:57:00+01:00', 'hi', 'Test Subject2', 'To#TEMP', 'ToCC#TEMP', 'ToBCC#TEMP')
EXEC SendMail Personalizations = 'Personalizations#TEMP', FromEmail = '[email protected]', Subject = 'hello', Content = 'Content#TEMP', Attachments = 'Attachments#TEMP'
| Name | Type | Required | Description |
| Subject | String | True | The subject of the mail to be sent. |
| ContentValue | String | False | The content of the mail to be sent. |
| ContentType | String | False | The type of content to be sent. supported values are text/plain and text/html |
| Content | String | True | The aggregate for Content object |
| SendAt | String | False | The date and time when you want your email to be delivered. Scheduling more than 72 hours in advance is forbidden. |
| FromEmail | String | True | The email address of the sender. |
| FromName | String | False | The name of the sender. |
| ToEmail | String | False | Email address to send the mail to |
| ToName | String | False | Email's respective names to send the mail to. |
| To | String | False | The aggregate for To recipients |
| ToCCEmail | String | False | Email address of the recipients who will receive a copy of your email |
| ToCCName | String | False | Name of the recipients who will receive a copy of your email. |
| ToCC | String | False | The aggregate for ToCC recipients. |
| ToBCCEmail | String | False | Email address of the recipients who will receive a blind carbon copy of your email. |
| ToBCCName | String | False | Name of the recipients who will receive a blind carbon copy of your email. |
| ToBCC | String | False | The aggregate for ToBCC recipients. |
| ReplyToEmail | String | False | The email address of the person to whom you are replying to. |
| ReplyToName | String | False | The name of the person to whom you are replying to. |
| AttachmentPaths | String | False | Path of the file to attach to the mail to be sent |
| TemplateId | String | False | The Id of the template that you may want to send |
| DynamicTemplateData | String | False | The data of the dynamic template. |
| Personalizations | String | True | An array of messages and their metadata. Each object within personalizations can be thought of as an envelope - it defines who should receive an individual message and how that message should be handled. |
| AttachmentFilename | String | False | The attachment's filename. Specify only when you don't specify the AttachmentPaths. |
| Attachments | String | False | An array of objects where you can specify any attachments you want to include. Specify only when you don't specify the AttachmentPaths. |
| Name | Type | Description |
| Success | String | Whether or not the mail was sent successfully. |
Sends a mail. This Stored Procedure is used to handle aggregates.
SendMail2 Stored Procedure is specifically made for handling the aggregates. User has to provide the whole json structure in order to execute this Stored Procedure.
For Example:
EXECUTE SendMail2 Personalizations = '[{"to": [{"email": "[email protected]", "name": "John Doe"}, {"email": "[email protected]", "name": "Julia Doe"}], "cc": [{"email": "[email protected]", "name": "Jane Doe"}], "bcc": [{"email": "[email protected]", "name": "Jim Doe"}]}, {"from": {"email": "[email protected]", "name": "Example Sales Team"}, "to": [{"email": "[email protected]", "name": "Janice Doe"}], "bcc": [{"email": "[email protected]", "name": "Jordan Doe"}]}]', FromEmail = '[email protected]', FromName = 'Example Order Confirmation', Subject = 'Test Subject', Content = '[{"type": "text/html", "value": "test value"}]', Categories = '["cake", "pie"]'
| Name | Type | Required | Description |
| Personalizations | String | True | An array of messages and their metadata. Each object within personalizations can be thought of as an envelope - it defines who should receive an individual message and how that message should be handled. |
| FromEmail | String | True | The email address of the sender. |
| FromName | String | True | The name of the sender. |
| ReplyToEmail | String | False | The email address of the person to whom you are replying to. |
| ReplyToName | String | False | The name of the person to whom you are replying to. |
| Subject | String | True | The global or 'message level' subject of your email. |
| Content | String | True | An array where you can specify the content of your email. |
| Attachments | String | False | An array of objects where you can specify any attachments you want to include. |
| Categories | String | False | An array of category names for this message. Each category name may not exceed 255 characters. |
| SendAt | String | False | A unix timestamp allowing you to specify when you want your email to be delivered. |
| BatchId | String | False | An ID representing a batch of emails to be sent at the same time. |
| AsmGroupId | String | False | The unsubscribe group to associate with this email. |
| AsmGroupsToDisplay | String | False | An array containing the unsubscribe groups that you would like to be displayed on the unsubscribe preferences page. |
| IpPoolName | String | False | The IP Pool that you would like to send this email from. |
| MailSettingsByPassListManagementEnable | String | False | A collection of different mail settings that you can use to specify how you would like this email to be handled. Indicates if this setting is enabled. |
| MailSettingsFooterEnable | String | False | The default footer that you would like included on every email. Indicates if this setting is enabled. |
| MailSettingsSandboxModeEnable | String | False | Sandbox Mode allows you to send a test email to ensure that your request body is valid and formatted correctly. Indicates if this setting is enabled. |
| TrackingSettingsClickTrackingEnable | String | False | Allows you to track if a recipient clicked a link in your email. Indicates if this setting is enabled. |
| TrackingSettingsClickTrackingEnableText | String | False | Allows you to track if a recipient clicked a link in your email. Indicates if this setting should be included in the text/plain portion of your email. |
| TrackingSettingsOpenTrackingEnable | String | False | Allows you to track if the email was opened by including a single pixel image in the body of the content. When the pixel is loaded, Twilio SendGrid can log that the email was opened. Indicates if this setting is enabled. |
| TrackingSettingsOpenTrackingSubstitutionTag | String | False | Allows you to track if the email was opened by including a single pixel image in the body of the content. When the pixel is loaded, Twilio SendGrid can log that the email was opened. Allows you to specify a substitution tag that you can insert in the body of your email at a location that you desire. This tag will be replaced by the open tracking pixel. |
| TrackingSettingsSubscriptionTrackingEnable | String | False | Allows you to insert a subscription management link at the bottom of the text and HTML bodies of your email. Indicates if this setting is enabled. |
| TemplateId | String | False | The Id of the template that you may want to send |
| Name | Type | Description |
| Success | String | Whether or not the mail was sent successfully. |
Sends a test campaign.
| Name | Type | Required | Description |
| To | String | True | The email address to send the campaign to. |
| Campaign_ID | String | True | The Id of the campaign to send. |
| AccountId | String | False | The ID of the account. |
| SubuserUsername | String | False | The username of the subuser. |
| Name | Type | Description |
| Success | String | Whether or not the campaign was sent successfully. |
The CData Sync App models the Legacy API as relational tables, views, and stored procedures. Most tables, views, and stored procedures are defined in schema files, which are simple, text-based configuration files.
However, the Recipients table is dynamic: The Sync App connects to SendGrid and gets the metadata for this table by calling the appropriate Web services. Any changes you make to the custom filters you define for Recipients are available when you connect; you can use these custom filters as columns in the WHERE clause. These custom filters are surfaced in the CustomFields table.
The Sync App uses the SendGrid API to process supported filters. The Sync App processes other filters client-side within the Sync App.
To use the Legacy Data Model, simply set Schema to Legacy.
Tables describes the available tables that are easy to query and update.
Views are tables that cannot be modified. Typically, read-only data are shown as views.
Stored Procedures are function-like interfaces to Sendgrid. They can be used to search, update, and modify information.
The Sync App models the data in SendGrid as a list of tables in a relational database that can be queried using standard SQL statements.
| Name | Description |
| Alerts | Create, update, delete, and query Alerts in SendGrid. |
| ApiKeys | Query, Create, Update and Delete the available ApiKeys in SendGrid. |
| Blocks | Query and Delete the available Blocks in SendGrid. |
| Bounces | Query and Delete the available Bounces in SendGrid. |
| CancelScheduledSends | Update, delete, and query Cancel Scheduled Sends in SendGrid. |
| CustomFields | Create, delete, and query Custom Fields in SendGrid. |
| GlobalUnsubscribes | Query Global Unsubscribes in SendGrid. |
| InvalidEmails | Query and Delete invalid emails in SendGrid. |
| Lists | Create, update, delete, and query the available Lists in SendGrid. |
| MarketingCampaigns | Create, update, delete, and query Marketing Campaigns in SendGrid. |
| Recipients | The SendGrid table Recipients. |
| Schedules | Create, update, delete, and query Campaign Schedules in SendGrid. |
| Segments | Create, update, delete, and query Segments in SendGrid. |
| SenderIdentities | Create, update, delete, and query Sender Identities in SendGrid. |
| Spam | Query and delete Spam reports in SendGrid. |
| Teammates | Query Teammates in SendGrid. |
| UnsubscribeGroups | Create, update, delete, and query Unsubscribe Groups in SendGrid. |
| Users | Query the available Users in SendGrid. |
Create, update, delete, and query Alerts in SendGrid.
This table only supports filtering by Id. The following are the only possible SELECT queries:
SELECT * FROM Alerts WHERE Id = '148825'
The following columns are required in an insert for Stats Notification: Type, EmailTo, Frequency.
INSERT INTO Alerts (Type, EmailTo, Frequency) VALUES ('stats_notification', '[email protected]', 'daily')
The following columns are required in an insert for Usage Limit: Type, EmailTo, Percentage.
INSERT INTO Alerts (Type, EmailTo, Percentage) VALUES ('usage_limit', '[email protected]', 20)
You can only update EmailTo by specifying an Id.
UPDATE Alerts SET EmailTo = '[email protected]' WHERE Id = 1310789
You can only delete from Alerts by specifying an Id.
DELETE FROM Alerts WHERE Id = 1310789
| Name | Type | ReadOnly | References | Description |
| Id [KEY] | Integer | True |
The ID of the alert. | |
| CreatedAt | Datetime | True |
Date when the alert was created. | |
| UpdatedAt | Datetime | True |
Date when the alert was updated. | |
| EmailTo | String | False |
The email address that the alert will be sent to. | |
| Percentage | Integer | False |
The email address that the alert will be sent to. | |
| Type | String | False |
The type of alert. Allowed values (usage_limit, stats_notification). | |
| Frequency | String | False |
If the alert is of type stats_notification, this indicates how frequently the stats notifications will be sent.(daily, weekly, monthly). |
Pseudo column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.
| Name | Type | Description |
| AccountId | String |
The ID of the account. |
| SubuserUsername | String |
The username of the subuser. |
Query, Create, Update and Delete the available ApiKeys in SendGrid.
To get all the Api Keys
SELECT * FROM ApiKeys
To get information about a specific Api Key
SELECT * FROM Apikeys WHERE ApiKeyId = 'Dqdvdvdvdv4yLeuVQqO3rFxN5ktUxA'
The following columns are required in an insert: Name.
VALUES for Scopes are:
alerts.create, alerts.read, alerts.update, alerts.delete, asm.groups.create, asm.groups.read, asm.groups.update, asm.groups.delete, ips.pools.ips.read, mail.send, mail_settings.bcc.read, mail_settings.bcc.update, mail_settings.address_whitelist.read, mail_settings.address_whitelist.update, mail_settings.footer.read,
mail_settings.footer.update, mail_settings.forward_spam.read, mail_settings.forward_spam.update, mail_settings.plain_content.read, mail_settings.plain_content.update, mail_settings.spam_check.read, mail_settings.spam_check.update, mail_settings.bounce_purge.read, mail_settings.bounce_purge.update, mail_settings.forward_bounce.read,
mail_settings.forward_bounce.update, partner_settings.new_relic.read, partner_settings.new_relic.update, partner_settings.sendwithus.read, partner_settings.sendwithus.update, tracking_settings.click.read, tracking_settings.click.update, tracking_settings.subscription.read, tracking_settings.subscription.update, tracking_settings.open.read,
tracking_settings.open.update, tracking_settings.google_analytics.read, tracking_settings.google_analytics.update, user.webhooks.event.settings.read, user.webhooks.event.settings.update, user.webhooks.event.test.create, user.webhooks.event.test.read, user.webhooks.event.test.update, user.webhooks.parse.settings.create, user.webhooks.parse.settings.read,
user.webhooks.parse.settings.update, user.webhooks.parse.settings.delete, stats.read, stats.global.read, categories.stats.read, categories.stats.sums.read, devices.stats.read, clients.stats.read, clients.phone.stats.read, clients.tablet.stats.read, clients.webmail.stats.read, clients.desktop.stats.read, geo.stats.read, mailbox_providers.stats.read,
browsers.stats.read, user.webhooks.parse.stats.read, templates.create, templates.read, templates.update, templates.delete, templates.versions.create, templates.versions.read, templates.versions.update, templates.versions.delete, templates.versions.activate.create, user.timezone.read, user.timezone.update, user.settings.enforced_tls.read, user.settings.enforced_tls.update,
api_keys.create, api_keys.read, api_keys.update, api_keys.delete, email_activity.read, categories.create, categories.read, categories.update, categories.delete, mail_settings.template.read, mail_settings.template.update, marketing_campaigns.create, marketing_campaigns.read, marketing_campaigns.update, marketing_campaigns.delete, mail.batch.create, mail.batch.read, mail.batch.update,
mail.batch.delete, user.scheduled_sends.create, user.scheduled_sends.read, user.scheduled_sends.update, user.scheduled_sends.delete, access_settings.whitelist.create, access_settings.whitelist.read, access_settings.whitelist.update, access_settings.whitelist.delete, access_settings.activity.read, whitelabel.create, whitelabel.read, whitelabel.update, whitelabel.delete, suppression.create,
suppression.read, suppression.update, suppression.delete, messages.read
INSERT INTO Apikeys (Name) VALUES ('apiname')
INSERT INTO Apikeys (Name, Scopes, Sample) VALUES ('apiname', 'alerts.create,alerts.read', 'test')
You can update ApiKeys by specifying an ApiKeyid.You need to specify both the name and the scopes during the UPDATE even if you don't want to update it.
UPDATE Apikeys SET Name = 'apiname2', Scopes = 'alerts.create,alerts.read' WHERE apikeyid = 'Dqdvdvdvdv4yLeuVQqO3rFxN5kscsctUxA-P_Q'
You can Delete ApiKeys by specifying an ApiKeyid.
DELETE FROM ApiKeys WHERE apikeyid = 'CMp4C8klscscscsQ0GxqvxtK2-P_Q'
| Name | Type | ReadOnly | References | Description |
| ApiKeyId [KEY] | String | False |
The ID of your API Key. | |
| Name | String | False |
The name of your API Key. | |
| Scopes | String | False |
The permissions this API Key has access to. This is populated only when Id is specified. |
Pseudo column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.
| Name | Type | Description |
| AccountId | String |
The ID of the account. |
| SubuserUsername | String |
The username of the subuser. |
Query and Delete the available Blocks in SendGrid.
You need to specify a time span to select from this table. If you do not specify one, a default span of the past 120 days is used. The CreatedAt column supports the >, <, =, <=, and >= operators.
SELECT * FROM Blocks WHERE CreatedAt > '2016-01-01' AND CreatedAt < '2016-01-30'
You can only delete from Blocks by specifying an Email.
DELETE FROM Blocks WHERE Email = '[email protected]'
| Name | Type | ReadOnly | References | Description |
| CreatedAt | Datetime | True |
The time the block was created. | |
| Reason | String | False |
The reason for the block. | |
| Email [KEY] | String | False |
The email that blocked. | |
| Status | String | False |
The enhanced SMTP block response. |
Pseudo column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.
| Name | Type | Description |
| AccountId | String |
The ID of the account. |
| SubuserUsername | String |
The username of the subuser. |
Query and Delete the available Bounces in SendGrid.
You need to specify a time span to select from this table. If you do not specify one, a default span of the past 120 days is used. The CreatedAt column supports the >, <, =, <=, and >= operators.
SELECT * FROM Bounces WHERE CreatedAt > '2016-01-01' AND CreatedAt < '2016-01-30'
You can only delete from Bounces by specifying an Email.
DELETE FROM Bounces WHERE Email = '[email protected]'
| Name | Type | ReadOnly | References | Description |
| CreatedAt | Datetime | True |
The time the bounce was created. | |
| Reason | String | False |
The reason for the bounce. | |
| Email [KEY] | String | False |
The email that bounced. | |
| Status | String | False |
The enhanced SMTP bounce response. |
Pseudo column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.
| Name | Type | Description |
| AccountId | String |
The ID of the account. |
| SubuserUsername | String |
The username of the subuser. |
Update, delete, and query Cancel Scheduled Sends in SendGrid.
This table only supports filtering by BatchId. The following are the only possible SELECT queries:
SELECT * FROM CancelScheduledSends SELECT * FROM CancelScheduledSends WHERE BatchId = 148825
You can update CancelScheduledSends by specifying an BatchId.
Allowed Values : cancel, pause
UPDATE CancelScheduledSends SET Status = 'cancel' WHERE BatchId = 1310789
You can only delete from CancelScheduledSends by specifying an BatchId.
DELETE FROM CancelScheduledSends WHERE BatchId = 1310789
| Name | Type | ReadOnly | References | Description |
| BatchId [KEY] | String | False |
The Id of the batch. | |
| Status | String | False |
The status of the scheduled send.Allowed Values: cancel, pause |
Pseudo column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.
| Name | Type | Description |
| AccountId | String |
The ID of the account. |
| SubuserUsername | String |
The username of the subuser. |
Create, delete, and query Custom Fields in SendGrid.
Custom fields are filters for a Recipient that are defined by the user.
You can retrieve all the CustomFields or filter them by Id:
SELECT * FROM CustomFields WHERE Id = '1'
Use quotations to filter on Custom Fields regardless of type.
To insert on CustomFields specify the Name of the field and its Type. The Type can be text, date, or number.
INSERT INTO CustomFields (name, type) VALUES ('age', 'number')
This table does not support updating.
You can only delete from CustomFields by specifying an Id:
DELETE FROM CustomFields WHERE Id = '1'
| Name | Type | ReadOnly | References | Description |
| Id [KEY] | String | False |
The Id of the custom field. | |
| Name | String | False |
The name of the custom field. | |
| Type | String | False |
The type of the custom field. Allowed values are number, text, or date. |
Pseudo column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.
| Name | Type | Description |
| AccountId | String |
The ID of the account. |
| SubuserUsername | String |
The username of the subuser. |
Query Global Unsubscribes in SendGrid.
You need to specify a time span to select from this table. However this filter is optional. The CreatedAt column supports the >, <, =, <=, and >= operators.
SELECT * FROM GlobalUnsubscribes WHERE CreatedAt > '2016-01-01' AND CreatedAt < '2016-01-30'
Performing an Insert operation in this table you need to specify an email which will be added to the GlobalUnsubscribes list. For example:
INSERT INTO GlobalUnsubscribes (Email) VALUES ('[email protected]')
Performing a Delete operation in this table you need to specify an email which will be removed from the GlobalUnsubscribes list. For example:
DELETE FROM GlobalUnsubscribes WHERE Email = '[email protected]'
| Name | Type | ReadOnly | References | Description |
| Email [KEY] | String | False |
Email of the unsubscriber. | |
| CreatedAt | Datetime | True |
The time the unsubscriber was created. |
Pseudo column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.
| Name | Type | Description |
| AccountId | String |
The ID of the account. |
| SubuserUsername | String |
The username of the subuser. |
Query and Delete invalid emails in SendGrid.
This table only supports filtering by Email. The following are the only possible SELECT queries:
SELECT * FROM InvalidEmails SELECT * FROM InvalidEmails WHERE Email = '[email protected]'
You can only delete from InvalidEmails by specifying an Email.
DELETE FROM InvalidEmails WHERE Email = '[email protected]'
| Name | Type | ReadOnly | References | Description |
| Created | Datetime | True |
The time the when the email address was added to the invalid emails list. | |
| Reason | String | False |
A reason explaining why the email address was marked as invalid.. | |
| Email [KEY] | String | False |
The email address that was marked as invalid. |
Pseudo column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.
| Name | Type | Description |
| AccountId | String |
The ID of the account. |
| SubuserUsername | String |
The username of the subuser. |
Create, update, delete, and query the available Lists in SendGrid.
The Lists table can only filtered by its Id.
SELECT * FROM Lists WHERE Id = '123'
Only the Name for the List is required to insert into this table.
INSERT INTO Lists (Name) VALUES ('TestList')
You can only update from Lists by specifying an Id.
UPDATE Lists SET Name = 'New Name' WHERE Id = '123'
You can only delete from Lists by specifying an Id.
DELETE FROM Lists WHERE Id = '123'
| Name | Type | ReadOnly | References | Description |
| Id [KEY] | Integer | True |
The Id of the list. | |
| Name | String | False |
The name of the list. | |
| RecipientCount | Integer | True |
The recipient count of the list. |
Pseudo column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.
| Name | Type | Description |
| AccountId | String |
The ID of the account. |
| SubuserUsername | String |
The username of the subuser. |
Create, update, delete, and query Marketing Campaigns in SendGrid.
This table only supports filtering by Id. The following are the only possible SELECT queries:
SELECT * FROM MarketingCampaigns SELECT * FROM MarketingCampaigns WHERE Id = '1'
The following columns are required in an insert: Title, Subject, SenderId, ListIds, SegmentIds, Categories, SuppressionGroupId, HtmlContent, and PlainContent.
Note that a CustomUnsubscribeUrl can be used in place of a SuppressionGroupId. However, SendGrid highly recommends to use SuppressionGroupId.
Use the check points below to find the SenderId and SuppressionGroupId inputs:
INSERT INTO MarketingCampaigns (Title, Subject, SenderId, ListIds, Categories, SuppressionGroupId, HtmlContent, PlainContent) VALUES ('Test Campaign', 'March Newsletter', '123', '1,2', 'fruits, health', '12', '<b>Eat Healthy</b>', 'Eat healthy')
You can only update MarketingCampaigns by specifying an Id.
UPDATE MarketingCampaigns SET PlainContent = 'Eat healthier' WHERE Id = '123'
You can only delete from MarketingCampaigns by specifying an Id.
DELETE FROM MarketingCampaigns WHERE Id = '123'
| Name | Type | ReadOnly | References | Description |
| Id [KEY] | String | True |
The Id of the marketing campaign. | |
| Title | String | False |
The title of the marketing campaign. | |
| Subject | String | False |
The subject of the marketing campaign. | |
| SenderId | Integer | False |
The sender Ids of the marketing campaign, separated by a comma. | |
| ListIds | String | False |
The list of list Ids of the marketing campaign, separated by a comma. | |
| SegmentIds | String | False |
The list of segment Ids of the marketing campaign, separated by a comma. | |
| Categories | String | False |
The categories of the marketing campaign. | |
| SuppressionGroupId | Integer | False |
The suppression group Id of the marketing campaign. | |
| CustomUnsubscribeUrl | String | False |
The custom unsubscribe URL of the marketing campaign. | |
| IpPool | String | False |
The IP pool of the marketing campaign. | |
| HtmlContent | String | False |
The HTML content of the marketing campaign. | |
| PlainContent | String | False |
The content of the marketing campaign. | |
| Status | String | True |
The status of the marketing campaign. | |
| Editor | String | False |
The editor used in the UI. The allowed values are code, design. |
Pseudo column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.
| Name | Type | Description |
| AccountId | String |
The ID of the account. |
| SubuserUsername | String |
The username of the subuser. |
The SendGrid table Recipients.
SendGrid has the ability to categorize Recipients with filters defined by the user. Accordingly, you can execute statements to the Recipients table to search by and insert these filters. However, these filters are reported as attributes of the Custom Fields table.
The following query retrieves only the default fields of the Recipients table, not the Custom Fields that you have created. To retrieve the values of the Custom Fields of a Recipient, query the Custom Fields table.
You can also retrieve all Recipients inside a certain List or a Segment, but it is not possible to filter by both. Use multiple queries instead:
SELECT * FROM Recipients WHERE SegmentId = '1' SELECT * FROM Recipients WHERE ListId = '2'
You can build criteria depending on a Custom Field. When querying use quotations regardless of type.This kind of filtering is done client side. In this case Age is a CustomField created by the user.
SELECT * FROM Recipients WHERE Age = '30'
To insert into Recipients Email is required.
You can insert Custom Fields into the Recipients table. See the CustomFields section for more information about how to create custom fields.
INSERT INTO Recipients (Email, FirstName, LastName, Age, Department ... Other Custom Fields as necessary) VALUES ('[email protected]', 'name', 'surname', '30', 'Education' ... Other Custom Field values)
You can only update from this table by specifying an Id. Additionally, the Email column cannot be updated.
UPDATE Recipients SET Age = '12' WHERE Id = '1'
You can only delete from this table by specifying an Id.
DELETE FROM Recipients WHERE Id = '1'
| Name | Type | ReadOnly | References | Description |
| Id [KEY] | String | False |
This column is dynamic and maps to the corresponding field in the API. | |
| SegmentId | Int32 | False |
This column is dynamic and maps to the corresponding field in the API. | |
| ListId | Int32 | False |
This column is dynamic and maps to the corresponding field in the API. | |
| String | False |
This column is dynamic and maps to the corresponding field in the API. | ||
| FirstName | String | False |
This column is dynamic and maps to the corresponding field in the API. | |
| LastName | String | False |
This column is dynamic and maps to the corresponding field in the API. | |
| CreatedAt | Datetime | True |
This column is dynamic and maps to the corresponding field in the API. | |
| LastClicked | Datetime | True |
This column is dynamic and maps to the corresponding field in the API. | |
| LastEmailed | Datetime | False |
This column is dynamic and maps to the corresponding field in the API. | |
| LastOpened | Datetime | True |
This column is dynamic and maps to the corresponding field in the API. | |
| UpdatedAt | Datetime | True |
This column is dynamic and maps to the corresponding field in the API. | |
| Age | String | False |
This column is dynamic and maps to the corresponding field in the API. | |
| Department | String | False |
This column is dynamic and maps to the corresponding field in the API. | |
| University | String | False |
This column is dynamic and maps to the corresponding field in the API. |
Create, update, delete, and query Campaign Schedules in SendGrid.
The following is an example to query the Schedules table:
SELECT * FROM Schedules WHERE MarketingCampaignId = '123'
Provide MarketingCampaignId and SendAt to schedule a campaign at a specific time. You can simply specify SendAt to immediately send a campaign. SendGrid requires that both the html and plain text content have an [unsubscribe] tag in them for a campaign to be sent.
INSERT INTO Schedules (MarketingCampaignId) VALUES (3091692)
INSERT INTO Schedules (MarketingCampaignId, SendAt) VALUES (1, '11/11/2018')
You can only update Schedules by specifying a MarketingCampaignId.
UPDATE Schedules SET SendAt = '01-01-2016' WHERE MarketingCampaignId = '123'
You can only delete Schedules by specifying a MarketingCampaignId.
DELETE FROM Schedules WHERE MarketingCampaignId = '123'
| Name | Type | ReadOnly | References | Description |
| MarketingCampaignId [KEY] | Integer | False |
Id of the campaign. | |
| Status | String | True |
Status of the campaign. | |
| SendAt | Datetime | False |
Date to start the campaign. |
Pseudo column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.
| Name | Type | Description |
| AccountId | String |
The ID of the account. |
| SubuserUsername | String |
The username of the subuser. |
Create, update, delete, and query Segments in SendGrid.
You can retrieve all the segments or filter them by Id.
SELECT * FROM Segments WHERE Id = '1'
A Segment divides Recipients by certain criteria. To specify these criteria use the ConditionsField columns and the Id of the List to apply these criteria to.
The ConditionsAndOr columns connect the given Field with the previous one.
INSERT INTO Segments (Name, ListId, ConditionsField1, ConditionsValue1, ConditionsOperator1, ConditionsAndOr1, ConditionsField2, ConditionsValue2, ConditionsOperator2, ConditionsAndOr2) VALUES ("New Segment", 123, 'age', '20', '>', '', 'age', '30', '<', 'and')
The statement above creates Segments containing Recipients between age 20 and 30.
You can update the name or the conditions. Since the whole set will be overwritten, specify a full set.
UPDATE Segments SET Name = 'Name Updated', ConditionsField1 = 'age', ConditionsOperator1 = '<=', ConditionsAndOr1 = '', ConditionsValue1 = '30' WHERE Id = '123'
You can only delete Segments by Id:
DELETE FROM Segments WHERE Id = '123'
| Name | Type | ReadOnly | References | Description |
| Id [KEY] | Integer | True |
The Id of the segment. | |
| Name | String | False |
The name of the segment. | |
| ListId | Integer | False |
The Id of the list associated with the segment. | |
| RecipientCount | Integer | True |
The recipient count of the segment. | |
| ConditionsField1 | String | False |
Field name for the first condition. | |
| ConditionsValue1 | String | False |
Field value for the first condition. | |
| ConditionsOperator1 | String | False |
Condition operator for the first condition. | |
| ConditionsAndOr1 | String | False |
How to connect to the previous condition. Allowed values are AND or OR. | |
| ConditionsField2 | String | False |
Field name for the second condition. | |
| ConditionsValue2 | String | False |
Field value for the second condition. | |
| ConditionsOperator2 | String | False |
Condition operator for the second condition. | |
| ConditionsAndOr2 | String | False |
How to connect to the previous condition. Allowed values are AND or OR. | |
| ConditionsField3 | String | False |
Field name for the third condition. | |
| ConditionsValue3 | String | False |
Field value for the third condition. | |
| ConditionsOperator3 | String | False |
Condition operator for the third condition. | |
| ConditionsAndOr3 | String | False |
How to connect to the previous condition. Allowed values are AND or OR. | |
| ConditionsField4 | String | False |
Field name for the fourth condition. | |
| ConditionsValue4 | String | False |
Field value for the fourth condition. | |
| ConditionsOperator4 | String | False |
Condition operator for the fourth condition. | |
| ConditionsAndOr4 | String | False |
How to connect to the previous condition. Allowed values are AND or OR. | |
| ConditionsField5 | String | False |
Field name for the fifth condition. | |
| ConditionsValue5 | String | False |
Field value for the fifth condition. | |
| ConditionsOperator5 | String | False |
Condition operator for the fifth condition. | |
| ConditionsAndOr5 | String | False |
How to connect to the previous condition. Allowed values are AND or OR. |
Pseudo column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.
| Name | Type | Description |
| AccountId | String |
The ID of the account. |
| SubuserUsername | String |
The username of the subuser. |
Create, update, delete, and query Sender Identities in SendGrid.
This table only supports filtering by Id. The following are the only possible SELECT queries:
SELECT * FROM SenderIdentities SELECT * FROM SenderIdentities WHERE Id = '148825'
The following columns are required in an insert: Nickname, FromEmail, FromName, ReplytoEmail, Address, City, Country.
INSERT INTO SenderIdentities (Nickname, FromEmail, FromName, ReplytoEmail, Address, City, Country) VALUES ('Nickname', 'FromEmail', 'FromName', 'ReplytoEmail', 'Address', 'City', 'Country')
You can update SenderIdentities by specifying an Id.
UPDATE SenderIdentities SET Nickname = 'Nickname', FromEmail = 'FromEmail', FromName = 'FromName', ReplytoEmail = 'ReplytoEmail', Address = 'Address', City = 'City', Country = 'Country' WHERE Id = 1310789
You can only delete from Alerts by specifying an Id.
DELETE FROM SenderIdentities WHERE Id = 1310789
| Name | Type | ReadOnly | References | Description |
| Id [KEY] | Integer | False |
The unique identifier of the sender identity. | |
| Nickname | String | False |
A nickname for the sender identity. Not used for sending.. | |
| FromEmail | String | False |
This is where the email will appear to originate from for your recipient. | |
| FromName | String | False |
This is the name appended to the from email field. IE - Your name or company name. | |
| ReplytoEmail | String | False |
This is the email that your recipient will reply to. | |
| ReplytoName | String | False |
This is the name appended to the reply to email field. IE - Your name or company name. | |
| Address | String | False |
The physical address of the sender identity. | |
| Address2 | String | False |
Additional sender identity address information. | |
| City | String | False |
The city of the sender identity. | |
| State | String | False |
The state of the sender identity. | |
| Zip | String | False |
The zipcode of the sender identity. | |
| Country | String | False |
The country of the sender identity. | |
| CreatedAt | Datetime | True |
The end of the time range when the bounce was created. | |
| UpdatedAt | Datetime | True |
The end of the time range when the bounce was created. | |
| Locked | Boolean | True |
A boolean flag that is true when the Sender is associated with a campaign in Draft, Scheduled, or In Progress status. You cannot update or delete a locked Sender. | |
| VerifiedReason | String | True |
The reason for verifying the sender | |
| VerifiedStatus | Boolean | True |
A boolean flag indicating whether the Sender is verified or not. Only verified Senders can be used to send email. |
Pseudo column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.
| Name | Type | Description |
| AccountId | String |
The ID of the account. |
| SubuserUsername | String |
The username of the subuser. |
Query and delete Spam reports in SendGrid.
This table only supports filtering by Email. The following are the only possible SELECT queries:
SELECT * FROM Spam SELECT * FROM Spam WHERE Email = '[email protected]'
Delete from Spam
You can delete from Spam by specifying an Email.
DELETE FROM Spam WHERE Email = '[email protected]'
| Name | Type | ReadOnly | References | Description |
| CreatedAt | Datetime | True |
The time when the spam report was made. | |
| Email [KEY] | String | False |
The email address of the recipient who marked your message as spam. | |
| Ip | String | False |
The IP address that the message was sent on. |
Pseudo column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.
| Name | Type | Description |
| AccountId | String |
The ID of the account. |
| SubuserUsername | String |
The username of the subuser. |
Query Teammates in SendGrid.
For example, the following queries are processed server side:
SELECT * FROM Teammates WHERE Username = 'test'
SELECT * FROM Teammates WHERE Username IN ('test', 'test2')
The following columns are required in an insert: Email and Scopes. Scopes column accepts a comma separated list of values. The accepted values are: user.account.read, user.credits.read, user.email.create, user.email.read, user.email.update, user.email.delete, user.profile.create, user.profile.read, user.profile.update, user.profile.delete.
The IsAdmin is optional and by default is accepted as false from the API.
INSERT INTO Teammates (Email, Scopes) VALUES ('[email protected]', 'user.profile.read, user.profile.update')
INSERT INTO Teammates (Email, Scopes, IsAdmin) VALUES ('[email protected]', 'user.profile.read, user.profile.update', 'true')
The following columns are required in an update: Username and Scopes. Scopes column accepts a comma separated list of values. The accepted values are: user.account.read, user.credits.read, user.email.create, user.email.read, user.email.update, user.email.delete, user.profile.create, user.profile.read, user.profile.update, user.profile.delete.
UPDATE Teammates SET Scopes = 'user.profile.read' WHERE Username = 'testuser'
Only the username column is required to delete a record from Teammates table. For example:
DELETE FROM Teammates WHERE Username = 'testuser'
| Name | Type | ReadOnly | References | Description |
| Username [KEY] | String | False |
The username of the teammate. | |
| String | False |
Email of the teammate. | ||
| FirstName | String | False |
First name of the teammate. | |
| LastName | String | False |
Last name of the teammate. | |
| UserType | String | False |
User type of the teammate. | |
| IsAdmin | Boolean | False |
Indicator if the teammate is admin. | |
| Phone | String | False |
Phone of the teammate. | |
| Website | String | False |
Website of the teammate. | |
| Company | String | False |
Company of the teammate. | |
| Address | String | False |
Address of the teammate. | |
| Address2 | String | False |
Address 2 of the teammate. | |
| City | String | False |
City of the teammate. | |
| State | String | False |
State of the teammate. | |
| Country | String | False |
Country of the teammate. | |
| Zip | String | False |
Zip of the teammate. | |
| Scopes | String | False |
Scope of the permissions for the new teammate. Multiple values are allowed and should be split by a comma symbol. Possible values are: user.account.read,user.credits.read,user.email.create,user.email.read,user.email.update,user.email.delete,user.profile.create,user.profile.read,user.profile.update,user.profile.delete | |
| IsPartnerSSO | Boolean | False |
Indicator if the teammate partner is SSO. | |
| IsSSO | Boolean | False |
Indicator if the teammate is SSO. | |
| IsUnified | Boolean | False |
Indicator if the teammate is unified. |
Pseudo column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.
| Name | Type | Description |
| AccountId | String |
The ID of the account. |
| SubuserUsername | String |
The username of the subuser. |
Create, update, delete, and query Unsubscribe Groups in SendGrid.
UnsubscribeGroups can only be filtered by Id.
SELECT * FROM UnsubscribeGroups WHERE Id = '1'
Provide a Name and a Description to insert into UnsubscribeGroups:
INSERT INTO UnsubscribeGroups (Name, Description, IsDefault) VALUES ('Unsubscribe1', 'General Unsubscribe', true)
You can only update UnsubscribeGroups by specifying an Id.
UPDATE UnsubscribeGroups SET Name = 'New Name', Description = 'New Description' WHERE Id = '1'
You can only delete from UnsubscribeGroups by specifying an Id.
DELETE FROM UnsubscribeGroups WHERE Id = '1'
| Name | Type | ReadOnly | References | Description |
| Id [KEY] | Integer | True |
Id of the unsubscribe group. | |
| Name | String | False |
The name of the unsubscribe group. | |
| Description | String | False |
The description of the unsubscribe group. | |
| LastEmailSentAt | Datetime | True |
The last time an email was sent to the unsubscribe group. | |
| IsDefault | Boolean | False |
If the unsubscribe group is the default group or not. | |
| Unsubscribes | Integer | True |
The number of unsubscribes from this group. |
Pseudo column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.
| Name | Type | Description |
| AccountId | String |
The ID of the account. |
| SubuserUsername | String |
The username of the subuser. |
Query the available Users in SendGrid.
Query this table to retrieve your current profile details.
SELECT * FROM Users
You can update the all the columns marked as readonly false.
UPDATE Users Set Address='Milpitas', Address2='North Carolina' WHERE id='38713966'
| Name | Type | ReadOnly | References | Description |
| Id [KEY] | String | True |
The Id of the user. | |
| Address | String | False |
The address of the user. | |
| Address2 | String | False |
The secondary address field for the user. | |
| City | String | False |
The city of the user. | |
| Company | String | False |
The company of the user. | |
| Country | String | False |
The country of the user. | |
| FirstName | String | False |
The first name of the user. | |
| LastName | String | False |
The last name of the user. | |
| Phone | String | False |
The phone number of the user. | |
| State | String | False |
The state the user is located in. | |
| Website | String | False |
The Web site URL of the user. | |
| Zip | String | False |
The ZIP code of the user. | |
| String | True |
The Email Address of the user. | ||
| Type | String | True |
The type of the user. |
Pseudo column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.
| Name | Type | Description |
| AccountId | String |
The ID of the account. |
| SubuserUsername | String |
The username of the subuser. |
Views are similar to tables in the way that data is represented; however, views are read-only.
Queries can be executed against a view as if it were a normal table.
| Name | Description |
| Categories | Query the available Categories in SendGrid. |
| CategoryStats | Query the available Category Stats in SendGrid. |
| DynamicTemplates | Query Teammates in SendGrid. |
| GlobalStats | Query the available Global Stats in SendGrid. |
| GroupSuppressions | Query group suppressions in SendGrid. |
| IPAccessManagement | Query Global Unsubscribes in SendGrid. |
| MailSettings | Query all the mail settings in SendGrid. |
| MessageEvents | List of events related to email message in SendGrid. |
| Messages | Query Email Activities in SendGrid. |
| PartnerSettings | Query all the partner settings in SendGrid. |
| ReservedFields | Query the available Reserved Fields in SendGrid. |
| StatsByBrowser | Query Browser Statistics in SendGrid. |
| StatsByClient | Query Client Statistics in SendGrid. |
| StatsByDevice | Query Device Statistics in SendGrid. |
| StatsByLocation | Query Location Statistics in SendGrid. |
| StatsByMailboxProvider | Query Mailbox Provider Statistics in SendGrid. |
| Subusers | Query all the subusers in sendgrid. |
| SubuserStats | Query Subuser Statistics in SendGrid. |
Query the available Categories in SendGrid.
Query this table to get available categories in SendGrid.
SELECT * FROM Categories
| Name | Type | References | Description |
| Name | String | The name of the categories. |
Pseudo column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.
| Name | Type | Description | |
| AccountId | String | The ID of the account. | |
| SubuserUsername | String | The username of the subuser. |
Query the available Category Stats in SendGrid.
The following is an example to query the CategoryStats view:
SELECT * FROM CategoryStats WHERE Name = 'news'
You can also filter by Date. If you do not specify one, a default span of the past 1 year is used. The operators =, >=, <=, <, and > are supported for this column.
SELECT * FROM CategoryStats WHERE Name = 'news' AND Date > '2016-01-01' AND Date < '2016-01-30'
| Name | Type | References | Description |
| Type | String | The type of the statistic. | |
| Name | String | The name of the category. | |
| Date | Date | The time the global statistic was created. | |
| Blocks | Integer | The number of emails that were not allowed to be delivered by ISPs. | |
| Drops | Integer | The number of emails automatically dropped by SendGrid because they appear on one of the suppression lists. | |
| Bounces | Integer | The number of emails that bounced instead of being delivered. | |
| Clicks | Integer | The number of links clicked in your emails. | |
| Deferred | Integer | The number of emails temporarily refused by the receiving server. | |
| Delivered | Integer | The number of emails confirmed delivered. | |
| InvalidEmails | Integer | The number of emails with a malformed address or reported as invalid by the receiving server. | |
| Opens | Integer | The number of times your emails were opened by recipients. | |
| Processed | Integer | The number of emails pushed to SendGrid. | |
| Requests | Integer | The number of emails you requested to send via SendGrid. | |
| SpamReportDrops | Integer | The number of emails automatically dropped because the emails were marked as spam by the recipients. | |
| SpamReports | Integer | The number of emails marked as spam by recipients. | |
| UniqueClicks | Integer | The number of unique recipients who clicked links in your emails. | |
| UniqueOpens | Integer | The number of unique recipients who opened your emails. | |
| UnsubscribeDrops | Integer | The number of emails in this category dropped by SendGrid because the recipient unsubscribed from your emails. | |
| Unsubscribes | Integer | The number of recipients who unsubscribed from your emails. |
Pseudo column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.
| Name | Type | Description | |
| AccountId | String | The ID of the account. | |
| SubuserUsername | String | The username of the subuser. |
Query Teammates in SendGrid.
| Name | Type | References | Description |
| Id [KEY] | String | The ID of the template. | |
| Name | String | Name of the template. | |
| Generation | String | Generation of the template. (dynamic) | |
| UpdatedAt | Datetime | The last time the template was updated. |
Query the available Global Stats in SendGrid.
You need to specify a time span to select from this table. If you do not specify one, a default span of the past 1 year is used. The Date column supports the >, <, =, <=, and >= operators.
SELECT * FROM GlobalStats
SELECT * FROM GlobalStats WHERE Date > '2016-01-01' AND Date < '2016-03-30'
| Name | Type | References | Description |
| Date | Date | The time the global statistic was created. | |
| Blocks | Integer | The number of emails that were not allowed to be delivered by ISPs. | |
| BounceDrops | Integer | The number of emails automatically dropped by SendGrid because they appear on one of the suppression lists. | |
| Bounces | Integer | The number of emails that bounced instead of being delivered. | |
| Clicks | Integer | The number of links clicked in your emails. | |
| Deferred | Integer | The number of emails temporarily refused by the receiving server. | |
| Delivered | Integer | The number of emails confirmed delivered. | |
| InvalidEmails | Integer | The number of emails with a malformed address or reported as invalid by the receiving server. | |
| Opens | Integer | The number of times your emails were opened by recipients. | |
| Processed | Integer | The number of emails pushed to SendGrid. | |
| Requests | Integer | The number of emails you requested to send via SendGrid. | |
| SpamReportDrops | Integer | The number of emails automatically dropped because the emails were marked as spam by the recipients. | |
| SpamReports | Integer | The number of emails marked as spam by recipients. | |
| UniqueClicks | Integer | The number of unique recipients who clicked links in your emails. | |
| UniqueOpens | Integer | The number of unique recipients who opened your emails. | |
| UnsubscribeDrops | Integer | The number of emails globally dropped by SendGrid because the recipient unsubscribed from your emails. | |
| Unsubscribes | Integer | The number of recipients who unsubscribed from your emails. |
Pseudo column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.
| Name | Type | Description | |
| AccountId | String | The ID of the account. | |
| SubuserUsername | String | The username of the subuser. |
Query group suppressions in SendGrid.
The following are examples to query the GroupSuppressions table:
SELECT * FROM GroupSuppressions WHERE GroupId = 391 SELECT * FROM GroupSuppressions WHERE GroupId IN (391, 392, 393)
| Name | Type | References | Description |
| GroupId [KEY] | Integer | Email of the unsubscriber. | |
| Emails | String | The time the unsubscriber was created. |
Pseudo column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.
| Name | Type | Description | |
| AccountId | String | The ID of the account. | |
| SubuserUsername | String | The username of the subuser. |
Query Global Unsubscribes in SendGrid.
Only the following query is processed server side:
SELECT * FROM IPAccessManagement
| Name | Type | References | Description |
| IP | String | IP Address. | |
| Allowed | Boolean | Indicator if this IP is allowed for access. | |
| AuthMethod | String | Authentication method. | |
| FirstAt | Timestamp | First time when IP has accessed the account. | |
| LastAt | Timestamp | Last time when IP has accessed the account. | |
| Location | String | Location of the IP. |
Pseudo column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.
| Name | Type | Description | |
| AccountId | String | The ID of the account. | |
| SubuserUsername | String | The username of the subuser. |
Query all the mail settings in SendGrid.
You can retrieve all the mail settings.
SELECT * FROM MailSettings
| Name | Type | References | Description |
| Title | String | The title of the mail setting. | |
| Enabled | String | Indicates if this mail setting is currently enabled. | |
| Name | String | The name of the mail setting. | |
| Description | String | A description of the mail setting. |
Pseudo column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.
| Name | Type | Description | |
| AccountId | String | The ID of the account. | |
| SubuserUsername | String | The username of the subuser. |
List of events related to email message in SendGrid.
NOTE: If you want access to Email events, you must purchase the Email Activity History add-in of SendGrid. If using a Restricted Access key, you must give it the messages.read and email_activity.read scopes.
SELECT * FROM MessageEvents WHERE MessageId = '1234'
NOTE: The query below will return message events only for the first 1000 message IDs retrieved from the messages endpoint.
SELECT * FROM MessageEvents;
| Name | Type | References | Description |
| MessageId | String | The Id of the message. | |
| EventName | String | Name of event.
The allowed values are bounced, opened, clicked, processed, dropped, delivered, deferred, spam_report, unsubscribe, group_unsubscribe, group_resubscribe. | |
| Processed | Datetime | The date when the event was processed. | |
| Reason | String | Explanation of what caused the message to be 'bounced', 'deferred', or 'blocked'. | |
| AttemptNum | Integer | Used with 'deferred' events to indicate the attempt number out of 10. | |
| Url | String | Used with 'clicked' event to indicate which url the user clicked. | |
| BounceType | String | Use to distinguish between types of bounces.
The allowed values are soft, hard. | |
| HttpUserAgent | String | Client recipient used to click or open message. | |
| MXServer | String | The MX server that received the email. | |
| ApiKeyId | String | Id of the API Key. | |
| AsmGroupId | String | ASM Group Id. | |
| Categories | String | Categories users associated to the message. | |
| UniqueArgs | String | JSON hash of key-value pairs associated with the message. | |
| OriginatingIp | String | This is the IP address of the person sending the message | |
| OutboundIp | String | This is the SendGrid dedicated IP address used to send the email | |
| OutboundIpType | String | The type of the outbound IP. | |
| Teammate | String | Username of the teammate. | |
| TemplateId | String | Template ID of the email. |
Query Email Activities in SendGrid.
NOTE: If you want access to Email activities, you must purchase the Email Activity History add-in of SendGrid. If using a Restricted Access key, you must give it the messages.read and email_activity.read scopes.
Note: The API will return only 1000 records. Please choose from the available filters to restrict the search.
For example, the following queries are processed server side:
SELECT * FROM Messages WHERE Id = '1234'
SELECT * FROM Messages WHERE Id IN ('1234', '4567')
SELECT * FROM Messages WHERE Status = 'not_delivered'
SELECT * FROM Messages WHERE LastEventTime BETWEEN '2020-01-01' AND '2020-01-15'
NOTE: Pagination is not available on this view. Any query—whether filtered or not—will return a maximum of 1000 records. If your filtered query matches more than 1000 records, only the first 1000 will be returned.
| Name | Type | References | Description |
| Id [KEY] | String | The Id of the message. | |
| Status | String | Status of the email. | |
| Subject | String | Subject of the email. | |
| FromEmail | String | The email of the sender. | |
| ToEmail | String | The email of the receiver. | |
| ClicksCount | Integer | The number of clicks. | |
| OpensCount | Integer | The number of times that the email was opened. | |
| LastEventTime | Datetime | The datetime of the event. | |
| ApiKeyId | String | Id of the API Key. | |
| AsmGroupId | String | ASM Group Id. | |
| MarketingCampaignId | String | The id of the marketing campaign. | |
| MarketingCampaignName | String | The name of the marketing campaign. | |
| MarketingCampaignSplitId | String | Split id of the campaign. | |
| MarketingCampaignVersion | String | Version of the campaign. | |
| OriginatingIp | String | This is the IP address of the person sending the message | |
| OutboundIp | String | This is the SendGrid dedicated IP address used to send the email | |
| OutboundIpType | String | The type of the outbound IP. | |
| Teammate | String | Username of the teammate. | |
| TemplateId | String | Template ID of the email. | |
| Events | String | List of events related to email message in SendGrid. |
Query all the partner settings in SendGrid.
You can retrieve all the partner settings.
SELECT * FROM PartnerSettings
| Name | Type | References | Description |
| Title | String | The title of the partner. | |
| Enabled | String | Indicates if this partner setting has been enabled. | |
| Name | String | The name of the partner setting. | |
| Description | String | A description of this partner setting. |
Pseudo column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.
| Name | Type | Description | |
| AccountId | String | The ID of the account. | |
| SubuserUsername | String | The username of the subuser. |
Query the available Reserved Fields in SendGrid.
This table does not support filtering.
SELECT * FROM ReservedFields
| Name | Type | References | Description |
| Name | String | The name of the reserved field. | |
| Type | String | The type of the reserved field. |
Pseudo column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.
| Name | Type | Description | |
| AccountId | String | The ID of the account. | |
| SubuserUsername | String | The username of the subuser. |
Query Browser Statistics in SendGrid.
You need to specify a time span to select from this table. If you do not specify one, a default span of the past 1 year is used. The Date column supports the >, <, =, <=, and >= operators.
If any date within the specified range has statistical data, the API will include that data in the resultset and return 0 for other dates. If no dates have non-zero stats within the specified date range, the API will return an empty result set.
SELECT * FROM StatsByBrowser WHERE Date > '2016-01-01' AND Date < '2016-03-30'
To query Browser Statistics by name.
SELECT * FROM StatsByBrowser WHERE Name = 'Firefox'
| Name | Type | References | Description |
| Type | String | The type of the statistic. | |
| Name | String | The name of the statistic. | |
| Date | Date | The time the global statistic was created. | |
| Clicks | Integer | The number of links clicked in your emails. | |
| UniqueClicks | Integer | The number of unique recipients who clicked links in your emails. |
Pseudo column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.
| Name | Type | Description | |
| AccountId | String | The ID of the account. | |
| SubuserUsername | String | The username of the subuser. |
Query Client Statistics in SendGrid.
You need to specify a time span to select from this table. If you do not specify one, a default span of the past 1 year is used. The Date column supports the >, <, =, <=, and >= operators.
If any date within the specified range has statistical data, the API will include that data in the resultset and return 0 for other dates. If no dates have non-zero stats within the specified date range, the API will return an empty result set.
SELECT * FROM StatsByClient WHERE Date > '2016-01-01' AND Date < '2016-03-30'
To query Client Statistics by name.
SELECT * FROM StatsByClient WHERE Name = 'Other'
| Name | Type | References | Description |
| Type | String | The type of the statistic. | |
| Name | String | The name of the statistic. | |
| Date | Date | The time the global statistic was created. | |
| Opens | Integer | The number of times your emails were opened by recipients. | |
| UniqueOpens | Integer | The number of unique recipients who opened your emails. |
Pseudo column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.
| Name | Type | Description | |
| AccountId | String | The ID of the account. | |
| SubuserUsername | String | The username of the subuser. |
Query Device Statistics in SendGrid.
You need to specify a time span to select from this table. If you do not specify one, a default span of the past 1 year is used. The Date column supports the >, <, =, <=, and >= operators.
If any date within the specified range has statistical data, the API will include that data in the resultset and return 0 for other dates. If no dates have non-zero stats within the specified date range, the API will return an empty result set.
SELECT * FROM StatsByDevice WHERE Date > '2016-01-01' AND Date < '2016-03-30'
To query Device Statistics by name.
SELECT * FROM StatsByDevice WHERE Name = 'Phone'
| Name | Type | References | Description |
| Type | String | The type of the statistic. | |
| Name | String | The name of the statistic. | |
| Date | Date | The time the global statistic was created. | |
| Opens | Integer | The number of times your emails were opened by recipients. | |
| UniqueOpens | Integer | The number of unique recipients who opened your emails. |
Pseudo column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.
| Name | Type | Description | |
| AccountId | String | The ID of the account. | |
| SubuserUsername | String | The username of the subuser. |
Query Location Statistics in SendGrid.
You need to specify a time span to select from this table. If you do not specify one, a default span of the past 1 year is used. The Date column supports the >, <, =, <=, and >= operators.
If any date within the specified range has statistical data, the API will include that data in the resultset and return 0 for other dates. If no dates have non-zero stats within the specified date range, the API will return an empty result set.
SELECT * FROM StatsByLocation WHERE Date > '2016-01-01' AND Date < '2016-03-30'
To query Location Statistics by name.
SELECT * FROM StatsByLocation WHERE Name = 'US'
To query Location Statistics by type.
SELECT * FROM StatsByLocation WHERE Type = 'country'
| Name | Type | References | Description |
| Type | String | The type of the statistic. | |
| Name | String | The name of the statistic. | |
| Date | Date | The time the global statistic was created. | |
| Clicks | Integer | The number of links clicked in your emails. | |
| Opens | Integer | The number of times your emails were opened by recipients. | |
| UniqueClicks | Integer | The number of unique recipients who clicked links in your emails. | |
| UniqueOpens | Integer | The number of unique recipients who opened your emails. |
Pseudo column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.
| Name | Type | Description | |
| AccountId | String | The ID of the account. | |
| SubuserUsername | String | The username of the subuser. |
Query Mailbox Provider Statistics in SendGrid.
You need to specify a time span to select from this table. If you do not specify one, a default span of the past 1 year is used. The Date column supports the >, <, =, <=, and >= operators.
If any date within the specified range has statistical data, the API will include that data in the resultset and return 0 for other dates. If no dates have non-zero stats within the specified date range, the API will return an empty result set.
SELECT * FROM StatsByMailboxProvider
SELECT * FROM StatsByMailboxProvider WHERE Date > '2016-01-01' AND Date < '2016-03-30'
To query Mailbox Provider Statistics by name.
SELECT * FROM StatsByMailboxProvider WHERE Name = 'Microsoft Outlook Live'
| Name | Type | References | Description |
| Type | String | The type of the statistic. | |
| Name | String | The name of the statistic. | |
| Date | Date | The time the global statistic was created. | |
| Blocks | Integer | The number of emails that were not allowed to be delivered by ISPs. | |
| Drops | Integer | The number of emails automatically dropped by SendGrid because they appear on one of the suppression lists. | |
| Bounces | Integer | The number of emails that bounced instead of being delivered. | |
| Clicks | Integer | The number of links clicked in your emails. | |
| Deferred | Integer | The number of emails temporarily refused by the receiving server. | |
| Delivered | Integer | The number of emails confirmed delivered. | |
| Opens | Integer | The number of times your emails were opened by recipients. | |
| Processed | Integer | The number of emails pushed to SendGrid. | |
| Requests | Integer | The number of emails you requested to send via SendGrid. | |
| SpamReports | Integer | The number of emails marked as spam by recipients. | |
| UniqueClicks | Integer | The number of unique recipients who clicked links in your emails. | |
| UniqueOpens | Integer | The number of unique recipients who opened your emails. |
Pseudo column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.
| Name | Type | Description | |
| AccountId | String | The ID of the account. | |
| SubuserUsername | String | The username of the subuser. |
Query all the subusers in sendgrid.
Query this table to retrieve all subusers.
SELECT * FROM Subusers
You can filter by Username to retrieve a specific subuser.
SELECT * FROM Subusers WHERE Username = 'Example'
| Name | Type | References | Description |
| Id | Integer | The Id of the subuser. | |
| String | The email of the subuser. | ||
| Username | String | The username of the subuser. | |
| Disabled | Boolean | Indicates whether the subuser is enabled or disabled. |
Query Subuser Statistics in SendGrid.
You can filter by SubuserName to retrieve stats of a specific subuser.
SELECT * FROM SubuserStats WHERE SubuserName = 'Example'
You can also filter by Date. Operators =, >=, <=, <, and > are supported for this column. If you do not specify one, a default span of the past 1 year is used.
SELECT * FROM SubuserStats WHERE SubuserName = 'News' AND Date > '2016-01-01' AND Date < '2016-01-30'
| Name | Type | References | Description |
| Date | Date | The time the subuser statistic was created. | |
| Blocks | Integer | The number of emails that were not allowed to be delivered by ISPs. | |
| Drops | Integer | The number of emails automatically dropped because they appear on one of the suppression lists. | |
| Bounces | Integer | The number of emails that bounced instead of being delivered. | |
| Clicks | Integer | The number of links that were clicked in the emails from this subuser. | |
| Deferred | Integer | The number of emails temporarily refused by the receiving server. | |
| Delivered | Integer | The number of emails from this subsuer that were confirmed delivered. | |
| InvalidEmails | Integer | The number of emails with a malformed address or reported as invalid by the receiving server. | |
| Opens | Integer | The number of times emails from this subuser were opened by recipients. | |
| Processed | Integer | The number of emails pushed to SendGrid by this subuser. | |
| Requests | Integer | The number of emails that you requested to send via SendGrid from this subuser. | |
| SpamReportDrops | Integer | The number of emails automatically dropped because the emails were marked as spam by the recipients. | |
| SpamReports | Integer | The number of emails from this subuser that were marked as spam by recipients. | |
| UniqueClicks | Integer | The number of unique recipients who clicked on links in your emails from this subuser. | |
| UniqueOpens | Integer | The number of unique recipients who opened your emails from this subuser. | |
| UnsubscribeDrops | Integer | The number of emails from this subuser dropped by SendGrid because the recipients unsubscribed from your emails. | |
| Unsubscribes | Integer | The number of recipients who unsubscribed from your emails from this subuser. | |
| SubuserName | String | The name of the statistic. | |
| Type | String | The type of the statistic. |
Stored procedures are function-like interfaces that extend the functionality of the Sync App beyond simple SELECT/INSERT/UPDATE/DELETE operations with SendGrid.
Stored procedures accept a list of parameters, perform their intended function, and then return any relevant response data from SendGrid, along with an indication of whether the procedure succeeded or failed.
| Name | Description |
| AddRecipientToList | Adds a recipient to a list. |
| GetImportContactsStatus | Gets the Import contacts status |
| GetScopes | Returns a list of all scopes that this user has access to. |
| ImportMarketingContacts | Import contacts to sendgrid account from CSV file. |
| SendMail | Sends a mail. |
| SendMail2 | Sends a mail. This Stored Procedure is used to handle aggregates. |
| SendTestCampaign | Sends a test campaign. |
Adds a recipient to a list.
| Name | Type | Required | Description |
| ListId | String | True | The unique identifier for the list. |
| RecipientId | String | True | The Id of the recipient. |
| AccountId | String | False | The ID of the account. |
| SubuserUsername | String | False | The username of the subuser. |
| Name | Type | Description |
| Success | String | Whether or not the recipient was successfully added to the list. |
Download Marketing Campaign Stats for Automations
The DownloadCampaignAutomationStats Stored Procedure requires CampaignID and the DownloadTo parameters to download the campaign automation stats in specific folder.
For Example:
EXEC DownloadCampaignAutomationStats Campaignid= 3091688, DownloadTo= 'C:\dev\tests\v20\ProviderSendGrid\'
| Name | Type | Required | Description |
| CampaignID | String | True | Comma seperated list of campaignIds. |
| Timezone | String | False | TimeZone of the location. |
| DownloadTo | String | False | Where to store the file. |
| Encoding | String | False | The FileData input encoding type.
The allowed values are NONE, BASE64. The default value is BASE64. |
| Name | Type | Description |
| Success | String | Whether or not the campaign was downloaded successfully. |
| FileData | String | If the DownloadTo and FileStream are not provided, this contains the content of the file. |
Gets the Import contacts status
The GetImportContactsStatus Stored Procedure requires JobId of the Import Contacts, which we can get by executing ImportMarketingContacts stored procedure.
Example:
EXEC GetImportContactsStatus JobId= '1234'
| Name | Type | Required | Description |
| JobId | String | True | The Id of the Import Contacts Job |
| Name | Type | Description |
| Success | String | The Staus of the corresponding Import Contacts Job. |
| RequestedCount | String | The Number of contacts requested to modify through API. |
| CreatedCount | String | The Number of contacts created. |
| UpdatedCount | String | The Number of Updated contacts. |
| DeletedCount | String | The Number of Deleted contacts. |
Returns a list of all scopes that this user has access to.
| Name | Type | Required | Description |
| AccountId | String | False | The Id of the account on whose behalf the call is made. |
| SubuserUsername | String | False | The username of the Subuser on whose behalf the call is made. |
| Name | Type | Description |
| Scopes | String | List of all scopes. |
Import contacts to sendgrid account from CSV file.
The ImportMarketingContacts Stored Procedure requires Field Mapping Ids and path of the File which contains contacts data.
We can Use custom_field ids or reserved_field ids for Field Mapping and We can get these ids using "Get All Field Definitions" endpoint.
NOTE:
1. Email field mapping is mandatory to import contacts from file.
2. As of now only csv file format is supported for this operation.
Example:
EXEC ImportMarketingContacts FileType= 'csv' , FieldMappings= '_rf2_T,_rf9_T' , FilePath = 'C:\Dev\Tests\v20\ProviderSendgrid\example.csv'
| Name | Type | Required | Description |
| FileType | String | False | The type of the file
The allowed values are csv. |
| FieldMappings | String | True | Comma separated list of field_definition IDs |
| ListIds | String | False | Comma separated list of List id's |
| FilePath | String | False | The absolute path of the File to import contacts |
| Name | Type | Description |
| JobId | String | The Id of the Import Contacts Job |
Sends a mail.
The DynamicTemplateData input requires information about dynamic data of the template. Value for the different variables put into templates.
Example: {"fullname":"Test","paymenttotal":"Test","description":"Test"}
NOTE: The TemplateId column is required when using Dynamic Templates.
SendMail Requires atleast one personalizations object in the request body and it can be added using the aggregate function.
For Example:
Using TEMP Tables.
INSERT INTO To#TEMP (ToEmail, ToName) VALUES ('[email protected]', 'abc')
INSERT INTO To#TEMP (ToEmail, ToName) VALUES ('[email protected]', 'xyz')
INSERT INTO To#TEMP (ToEmail) VALUES ('[email protected]')
INSERT INTO ToCC#TEMP (ToCCName, ToCCEmail) VALUES ('[email protected]', 'xyz')
INSERT INTO ToBCC#TEMP (ToBCCEmail, ToBCCName) VALUES ('[email protected]', 'abc')
INSERT INTO Content#TEMP (ContentValue, ContentType) VALUES ('[email protected]', 'text/plain')
INSERT INTO Personalizations#TEMP (FromEmail, SendAt, FromName, Subject, To, ToCC, ToBCC) VALUES ('[email protected]', '2017-10-30T10:57:00+01:00', 'hi', 'Test Subject2', 'To#TEMP', 'ToCC#TEMP', 'ToBCC#TEMP')
EXEC SendMail Personalizations = 'Personalizations#TEMP', FromEmail = '[email protected]', Subject = 'hello', Content = 'Content#TEMP'
Using Aggregate values.
Send Mail to single Mail Address.
INSERT INTO Personalizations#TEMP (FromEmail, SendAt, FromName, Subject, To, ToCC, ToBCC) VALUES ('[email protected]', '2017-10-30T10:57:00+01:00', 'hi', 'Test Subject2',
'[
{
"ToEmail": "[email protected]",
"ToName": "abc"
}
]',
'[
{
"ToCCName": "xyz",
"ToCCEmail": "[email protected]"
}
]',
'[
{
"ToBCCEmail": "[email protected]",
"ToBCCName": "abcd"
}
]')
EXEC SendMail Personalizations = 'Personalizations#TEMP', FromEmail = '[email protected]', Subject = 'hello', Content =
'{
"ContentValue":"content",
"ContentType":"text/plain"
}'
Send Mail to Multiple Mail Addresses.
INSERT INTO Personalizations#TEMP (FromEmail, SendAt, FromName, Subject, To, ToCC, ToBCC) VALUES ('[email protected]', '2017-10-30T10:57:00+01:00', 'hi', 'Test Subject2',
'[
{
"ToEmail": "[email protected]",
"ToName": "abc"
},
{
"ToEmail": "[email protected]",
"ToName": "xyz"
},
{
"ToEmail": "[email protected]"
}
]',
'[
{
"ToCCName": "sac",
"ToCCEmail": "[email protected]"
}
]',
'[
{
"ToBCCEmail": "xyz",
"ToBCCName": "[email protected]"
}
]')
EXEC SendMail Personalizations = 'Personalizations#TEMP', FromEmail = '[email protected]', Subject = 'hello', Content =
'{
"ContentValue":"content",
"ContentType":"text/html"
}'
Send Mail using attachment.
INSERT INTO To#TEMP (ToEmail, ToName) VALUES ('[email protected]', 'abc')
INSERT INTO To#TEMP (ToEmail, ToName) VALUES ('[email protected]', 'xyz')
INSERT INTO To#TEMP (ToEmail) VALUES ('[email protected]')
INSERT INTO ToCC#TEMP (ToCCName, ToCCEmail) VALUES ('[email protected]', 'xyz')
INSERT INTO ToBCC#TEMP (ToBCCEmail, ToBCCName) VALUES ('[email protected]', 'abc')
INSERT INTO Content#TEMP (ContentValue, ContentType) VALUES ('[email protected]', 'text/plain')
INSERT INTO Attachments#TEMP (AttachmentContent, AttachmentFilename) VALUES ('abcdefghijklmn', 'Test2.png')
INSERT INTO Personalizations#TEMP (FromEmail, SendAt, FromName, Subject, To, ToCC, ToBCC) VALUES ('[email protected]', '2017-10-30T10:57:00+01:00', 'hi', 'Test Subject2', 'To#TEMP', 'ToCC#TEMP', 'ToBCC#TEMP')
EXEC SendMail Personalizations = 'Personalizations#TEMP', FromEmail = '[email protected]', Subject = 'hello', Content = 'Content#TEMP', Attachments = 'Attachments#TEMP'
| Name | Type | Required | Description |
| Subject | String | True | The subject of the mail to be sent. |
| ContentValue | String | False | The content of the mail to be sent. |
| ContentType | String | False | The type of content to be sent. supported values are text/plain and text/html |
| Content | String | True | The aggregate for Content object |
| SendAt | String | False | The date and time when you want your email to be delivered. Scheduling more than 72 hours in advance is forbidden. |
| FromEmail | String | True | The email address of the sender. |
| FromName | String | False | The name of the sender. |
| ToEmail | String | False | Email address to send the mail to |
| ToName | String | False | Email's respective names to send the mail to. |
| To | String | False | The aggregate for To recipients |
| ToCCEmail | String | False | Email address of the recipients who will receive a copy of your email |
| ToCCName | String | False | Name of the recipients who will receive a copy of your email. |
| ToCC | String | False | The aggregate for ToCC recipients. |
| ToBCCEmail | String | False | Email address of the recipients who will receive a blind carbon copy of your email. |
| ToBCCName | String | False | Name of the recipients who will receive a blind carbon copy of your email. |
| ToBCC | String | False | The aggregate for ToBCC recipients. |
| ReplyToEmail | String | False | The email address of the person to whom you are replying to. |
| ReplyToName | String | False | The name of the person to whom you are replying to. |
| AttachmentPaths | String | False | Path of the file to attach to the mail to be sent |
| TemplateId | String | False | The Id of the template that you may want to send |
| DynamicTemplateData | String | False | The data of the dynamic template. |
| Personalizations | String | True | An array of messages and their metadata. Each object within personalizations can be thought of as an envelope - it defines who should receive an individual message and how that message should be handled. |
| AttachmentFilename | String | False | The attachment's filename. Specify only when you don't specify the AttachmentPaths. |
| Attachments | String | False | An array of objects where you can specify any attachments you want to include. Specify only when you don't specify the AttachmentPaths. |
| Name | Type | Description |
| Success | String | Whether or not the mail was sent successfully. |
Sends a mail. This Stored Procedure is used to handle aggregates.
SendMail2 Stored Procedure is specifically made for handling the aggregates. User has to provide the whole json structure in order to execute this Stored Procedure.
For Example:
EXECUTE SendMail2 Personalizations = '[{"to": [{"email": "[email protected]", "name": "John Doe"}, {"email": "[email protected]", "name": "Julia Doe"}], "cc": [{"email": "[email protected]", "name": "Jane Doe"}], "bcc": [{"email": "[email protected]", "name": "Jim Doe"}]}, {"from": {"email": "[email protected]", "name": "Example Sales Team"}, "to": [{"email": "[email protected]", "name": "Janice Doe"}], "bcc": [{"email": "[email protected]", "name": "Jordan Doe"}]}]', FromEmail = '[email protected]', FromName = 'Example Order Confirmation', Subject = 'Test Subject', Content = '[{"type": "text/html", "value": "test value"}]', Categories = '["cake", "pie"]'
| Name | Type | Required | Description |
| Personalizations | String | True | An array of messages and their metadata. Each object within personalizations can be thought of as an envelope - it defines who should receive an individual message and how that message should be handled. |
| FromEmail | String | True | The email address of the sender. |
| FromName | String | True | The name of the sender. |
| ReplyToEmail | String | False | The email address of the person to whom you are replying to. |
| ReplyToName | String | False | The name of the person to whom you are replying to. |
| Subject | String | True | The global or 'message level' subject of your email. |
| Content | String | True | An array where you can specify the content of your email. |
| Attachments | String | False | An array of objects where you can specify any attachments you want to include. |
| Categories | String | False | An array of category names for this message. Each category name may not exceed 255 characters. |
| SendAt | String | False | A unix timestamp allowing you to specify when you want your email to be delivered. |
| BatchId | String | False | An ID representing a batch of emails to be sent at the same time. |
| AsmGroupId | String | False | The unsubscribe group to associate with this email. |
| AsmGroupsToDisplay | String | False | An array containing the unsubscribe groups that you would like to be displayed on the unsubscribe preferences page. |
| IpPoolName | String | False | The IP Pool that you would like to send this email from. |
| MailSettingsByPassListManagementEnable | String | False | A collection of different mail settings that you can use to specify how you would like this email to be handled. Indicates if this setting is enabled. |
| MailSettingsFooterEnable | String | False | The default footer that you would like included on every email. Indicates if this setting is enabled. |
| MailSettingsSandboxModeEnable | String | False | Sandbox Mode allows you to send a test email to ensure that your request body is valid and formatted correctly. Indicates if this setting is enabled. |
| TrackingSettingsClickTrackingEnable | String | False | Allows you to track if a recipient clicked a link in your email. Indicates if this setting is enabled. |
| TrackingSettingsClickTrackingEnableText | String | False | Allows you to track if a recipient clicked a link in your email. Indicates if this setting should be included in the text/plain portion of your email. |
| TrackingSettingsOpenTrackingEnable | String | False | Allows you to track if the email was opened by including a single pixel image in the body of the content. When the pixel is loaded, Twilio SendGrid can log that the email was opened. Indicates if this setting is enabled. |
| TrackingSettingsOpenTrackingSubstitutionTag | String | False | Allows you to track if the email was opened by including a single pixel image in the body of the content. When the pixel is loaded, Twilio SendGrid can log that the email was opened. Allows you to specify a substitution tag that you can insert in the body of your email at a location that you desire. This tag will be replaced by the open tracking pixel. |
| TrackingSettingsSubscriptionTrackingEnable | String | False | Allows you to insert a subscription management link at the bottom of the text and HTML bodies of your email. Indicates if this setting is enabled. |
| TemplateId | String | False | The Id of the template that you may want to send |
| Name | Type | Description |
| Success | String | Whether or not the mail was sent successfully. |
Sends a test campaign.
| Name | Type | Required | Description |
| To | String | True | The email address to send the campaign to. |
| Campaign_ID | String | True | The Id of the campaign to send. |
| AccountId | String | False | The ID of the account. |
| SubuserUsername | String | False | The username of the subuser. |
| Name | Type | Description |
| Success | String | Whether or not the campaign was sent successfully. |
The connection string properties are the various options that can be used to establish a connection. This section provides a complete list of the options you can configure in the connection string for this provider. Click the links for further details.
For more information on establishing a connection, see Establishing a Connection.
| Property | Description |
| APIKey | The API key of the currently authenticated user. |
| Property | Description |
| SSLServerCert | Specifies the certificate to be accepted from the server when connecting using TLS/SSL. |
| Property | Description |
| FirewallType | Specifies the protocol the provider uses to tunnel traffic through a proxy-based firewall. |
| FirewallServer | Identifies the IP address, DNS name, or host name of a proxy used to traverse a firewall and relay user queries to network resources. |
| FirewallPort | Specifies the TCP port to be used for a proxy-based firewall. |
| FirewallUser | Identifies the user ID of the account authenticating to a proxy-based firewall. |
| FirewallPassword | Specifies the password of the user account authenticating to a proxy-based firewall. |
| Property | Description |
| ProxyAutoDetect | Specifies whether the provider checks your system proxy settings for existing proxy server configurations, rather than using a manually specified proxy server. |
| ProxyServer | Identifies the hostname or IP address of the proxy server through which you want to route HTTP traffic. |
| ProxyPort | Identifies the TCP port on your specified proxy server that has been reserved for routing HTTP traffic to and from the client. |
| ProxyAuthScheme | Specifies the authentication method the provider uses when authenticating to the proxy server specified in the ProxyServer connection property. |
| ProxyUser | Provides the username of a user account registered with the proxy server specified in the ProxyServer connection property. |
| ProxyPassword | Specifies the password of the user specified in the ProxyUser connection property. |
| ProxySSLType | Specifies the SSL type to use when connecting to the proxy server specified in the ProxyServer connection property. |
| ProxyExceptions | Specifies a semicolon-separated list of destination hostnames or IPs that are exempt from connecting through the proxy server set in the ProxyServer connection property. |
| Property | Description |
| LogModules | Specifies the core modules to include in the log file. Use a semicolon-separated list of module names. By default, all modules are logged. |
| Property | Description |
| Location | Specifies the location of a directory containing schema files that define tables, views, and stored procedures. Depending on your service's requirements, this may be expressed as either an absolute path or a relative path. |
| BrowsableSchemas | Optional setting that restricts the schemas reported to a subset of all available schemas. For example, BrowsableSchemas=SchemaA,SchemaB,SchemaC . |
| Tables | Optional setting that restricts the tables reported to a subset of all available tables. For example, Tables=TableA,TableB,TableC . |
| Views | Optional setting that restricts the views reported to a subset of the available tables. For example, Views=ViewA,ViewB,ViewC . |
| Schema | The type of schema to use. |
| Property | Description |
| IncludeCustomFields | A boolean indicating if you would like to include custom fields in the column listing. |
| MaxRows | Specifies the maximum number of rows returned for queries that do not include either aggregation or GROUP BY. |
| Other | Specifies advanced connection properties for specialized scenarios. Use this property only under the guidance of our Support team to address specific issues. |
| PseudoColumns | Specifies the pseudocolumns to expose as table columns, expressed as a string in the format 'TableName=ColumnName;TableName=ColumnName'. |
| Timeout | Specifies the maximum time, in seconds, that the provider waits for a server response before throwing a timeout error. |
| UserDefinedViews | Specifies a filepath to a JSON configuration file that defines custom views. The provider automatically detects and uses the views specified in this file. |
This section provides a complete list of the Authentication properties you can configure in the connection string for this provider.
| Property | Description |
| APIKey | The API key of the currently authenticated user. |
The API key of the currently authenticated user.
The API key of the currently authenticated user. Note that it is a manadatory parameter to authenticate through SendGrid Sync App.
This section provides a complete list of the SSL properties you can configure in the connection string for this provider.
| Property | Description |
| SSLServerCert | Specifies the certificate to be accepted from the server when connecting using TLS/SSL. |
Specifies the certificate to be accepted from the server when connecting using TLS/SSL.
If you are using a TLS/SSL connection, use this property to specify the TLS/SSL certificate to be accepted from the server. If you specify a value for this property, all other certificates that are not trusted by the machine are rejected.
This property can take the following forms:
| Description | Example |
| A full PEM Certificate (example shortened for brevity) | -----BEGIN CERTIFICATE----- MIIChTCCAe4CAQAwDQYJKoZIhv......Qw== -----END CERTIFICATE----- |
| A path to a local file containing the certificate | C:\cert.cer |
| The public key (example shortened for brevity) | -----BEGIN RSA PUBLIC KEY----- MIGfMA0GCSq......AQAB -----END RSA PUBLIC KEY----- |
| The MD5 Thumbprint (hex values can also be either space- or colon-separated) | ecadbdda5a1529c58a1e9e09828d70e4 |
| The SHA1 Thumbprint (hex values can also be either space- or colon-separated) | 34a929226ae0819f2ec14b4a3d904f801cbb150d |
Note: It is possible to use '*' to signify that all certificates should be accepted, but due to security concerns this is not recommended.
This section provides a complete list of the Firewall properties you can configure in the connection string for this provider.
| Property | Description |
| FirewallType | Specifies the protocol the provider uses to tunnel traffic through a proxy-based firewall. |
| FirewallServer | Identifies the IP address, DNS name, or host name of a proxy used to traverse a firewall and relay user queries to network resources. |
| FirewallPort | Specifies the TCP port to be used for a proxy-based firewall. |
| FirewallUser | Identifies the user ID of the account authenticating to a proxy-based firewall. |
| FirewallPassword | Specifies the password of the user account authenticating to a proxy-based firewall. |
Specifies the protocol the provider uses to tunnel traffic through a proxy-based firewall.
A proxy-based firewall (or proxy firewall) is a network security device that acts as an intermediary between user requests and the resources they access. The proxy accepts the request of an authenticated user, tunnels through the firewall, and transmits the request to the appropriate server.
Because the proxy evaluates and transfers data backets on behalf of the requesting users, the users never connect directly with the servers, only with the proxy.
Note: By default, the Sync App connects to the system proxy. To disable this behavior and connect to one of the following proxy types, set ProxyAutoDetect to false.
The following table provides port number information for each of the supported protocols.
| Protocol | Default Port | Description |
| TUNNEL | 80 | The port where the Sync App opens a connection to SendGrid. Traffic flows back and forth via the proxy at this location. |
| SOCKS4 | 1080 | The port where the Sync App opens a connection to SendGrid. SOCKS 4 then passes theFirewallUser value to the proxy, which determines whether the connection request should be granted. |
| SOCKS5 | 1080 | The port where the Sync App sends data to SendGrid. If the SOCKS 5 proxy requires authentication, set FirewallUser and FirewallPassword to credentials the proxy recognizes. |
To connect to HTTP proxies, use ProxyServer and ProxyPort. To authenticate to HTTP proxies, use ProxyAuthScheme, ProxyUser, and ProxyPassword.
Identifies the IP address, DNS name, or host name of a proxy used to traverse a firewall and relay user queries to network resources.
A proxy-based firewall (or proxy firewall) is a network security device that acts as an intermediary between user requests and the resources they access. The proxy accepts the request of an authenticated user, tunnels through the firewall, and transmits the request to the appropriate server.
Because the proxy evaluates and transfers data backets on behalf of the requesting users, the users never connect directly with the servers, only with the proxy.
Specifies the TCP port to be used for a proxy-based firewall.
A proxy-based firewall (or proxy firewall) is a network security device that acts as an intermediary between user requests and the resources they access. The proxy accepts the request of an authenticated user, tunnels through the firewall, and transmits the request to the appropriate server.
Because the proxy evaluates and transfers data backets on behalf of the requesting users, the users never connect directly with the servers, only with the proxy.
Identifies the user ID of the account authenticating to a proxy-based firewall.
A proxy-based firewall (or proxy firewall) is a network security device that acts as an intermediary between user requests and the resources they access. The proxy accepts the request of an authenticated user, tunnels through the firewall, and transmits the request to the appropriate server.
Because the proxy evaluates and transfers data backets on behalf of the requesting users, the users never connect directly with the servers, only with the proxy.
Specifies the password of the user account authenticating to a proxy-based firewall.
A proxy-based firewall (or proxy firewall) is a network security device that acts as an intermediary between user requests and the resources they access. The proxy accepts the request of an authenticated user, tunnels through the firewall, and transmits the request to the appropriate server.
Because the proxy evaluates and transfers data backets on behalf of the requesting users, the users never connect directly with the servers, only with the proxy.
This section provides a complete list of the Proxy properties you can configure in the connection string for this provider.
| Property | Description |
| ProxyAutoDetect | Specifies whether the provider checks your system proxy settings for existing proxy server configurations, rather than using a manually specified proxy server. |
| ProxyServer | Identifies the hostname or IP address of the proxy server through which you want to route HTTP traffic. |
| ProxyPort | Identifies the TCP port on your specified proxy server that has been reserved for routing HTTP traffic to and from the client. |
| ProxyAuthScheme | Specifies the authentication method the provider uses when authenticating to the proxy server specified in the ProxyServer connection property. |
| ProxyUser | Provides the username of a user account registered with the proxy server specified in the ProxyServer connection property. |
| ProxyPassword | Specifies the password of the user specified in the ProxyUser connection property. |
| ProxySSLType | Specifies the SSL type to use when connecting to the proxy server specified in the ProxyServer connection property. |
| ProxyExceptions | Specifies a semicolon-separated list of destination hostnames or IPs that are exempt from connecting through the proxy server set in the ProxyServer connection property. |
Specifies whether the provider checks your system proxy settings for existing proxy server configurations, rather than using a manually specified proxy server.
When this connection property is set to True, the Sync App checks your system proxy settings for existing proxy server configurations (no need to manually supply proxy server details).
This connection property takes precedence over other proxy settings. If you want to configure the Sync App to connect to a specific proxy server, set ProxyAutoDetect to False.
To connect to an HTTP proxy, see ProxyServer. For other proxies, such as SOCKS or tunneling, see FirewallType.
Identifies the hostname or IP address of the proxy server through which you want to route HTTP traffic.
The Sync App only routes HTTP traffic through the proxy server specified in this connection property when ProxyAutoDetect is set to False.
If ProxyAutoDetect is set to True (the default), the Sync App instead routes HTTP traffic through the proxy server specified in your system proxy settings.
Identifies the TCP port on your specified proxy server that has been reserved for routing HTTP traffic to and from the client.
The Sync App only routes HTTP traffic through the ProxyServer port specified in this connection property when ProxyAutoDetect is set to False.
If ProxyAutoDetect is set to True (the default), the Sync App instead routes HTTP traffic through the proxy server port specified in your system proxy settings.
For other proxy types, see FirewallType.
Specifies the authentication method the provider uses when authenticating to the proxy server specified in the ProxyServer connection property.
Supported authentication types :
For all values other than NONE, you must also set the ProxyUser and ProxyPassword connection properties.
If you need to use another authentication type, such as SOCKS 5 authentication, see FirewallType.
Provides the username of a user account registered with the proxy server specified in the ProxyServer connection property.
The ProxyUser and ProxyPassword connection properties are used to connect and authenticate against the HTTP proxy specified in ProxyServer.
After selecting one of the available authentication types in ProxyAuthScheme, set this property as follows:
| ProxyAuthScheme Value | Value to set for ProxyUser |
| BASIC | The username of a user registered with the proxy server. |
| DIGEST | The username of a user registered with the proxy server. |
| NEGOTIATE | The username of a Windows user who is a valid user in the domain or trusted domain that the proxy server is part of, in the format user@domain or domain\user. |
| NTLM | The username of a Windows user who is a valid user in the domain or trusted domain that the proxy server is part of, in the format user@domain or domain\user. |
| NONE | Do not set the ProxyPassword connection property. |
Note: The Sync App only uses this username if ProxyAutoDetect is set to False. If ProxyAutoDetect is set to True (the default), the Sync App instead uses the username specified in your system proxy settings.
Specifies the password of the user specified in the ProxyUser connection property.
The ProxyUser and ProxyPassword connection properties are used to connect and authenticate against the HTTP proxy specified in ProxyServer.
After selecting one of the available authentication types in ProxyAuthScheme, set this property as follows:
| ProxyAuthScheme Value | Value to set for ProxyPassword |
| BASIC | The password associated with the proxy server user specified in ProxyUser. |
| DIGEST | The password associated with the proxy server user specified in ProxyUser. |
| NEGOTIATE | The password associated with the Windows user account specified in ProxyUser. |
| NTLM | The password associated with the Windows user account specified in ProxyUser. |
| NONE | Do not set the ProxyPassword connection property. |
For SOCKS 5 authentication or tunneling, see FirewallType.
Note: The Sync App only uses this password if ProxyAutoDetect is set to False. If ProxyAutoDetect is set to True (the default), the Sync App instead uses the password specified in your system proxy settings.
Specifies the SSL type to use when connecting to the proxy server specified in the ProxyServer connection property.
This property determines when to use SSL for the connection to the HTTP proxy specified by ProxyServer. You can set this connection property to the following values :
| AUTO | Default setting. If ProxyServer is set to an HTTPS URL, the Sync App uses the TUNNEL option. If ProxyServer is set to an HTTP URL, the component uses the NEVER option. |
| ALWAYS | The connection is always SSL enabled. |
| NEVER | The connection is not SSL enabled. |
| TUNNEL | The connection is made through a tunneling proxy. The proxy server opens a connection to the remote host and traffic flows back and forth through the proxy. |
Specifies a semicolon-separated list of destination hostnames or IPs that are exempt from connecting through the proxy server set in the ProxyServer connection property.
The ProxyServer is used for all addresses, except for addresses defined in this property. Use semicolons to separate entries.
Note: The Sync App uses the system proxy settings by default, without further configuration needed. If you want to explicitly configure proxy exceptions for this connection, set ProxyAutoDetect to False.
This section provides a complete list of the Logging properties you can configure in the connection string for this provider.
| Property | Description |
| LogModules | Specifies the core modules to include in the log file. Use a semicolon-separated list of module names. By default, all modules are logged. |
Specifies the core modules to include in the log file. Use a semicolon-separated list of module names. By default, all modules are logged.
The Sync App writes details about each operation it performs into the logfile specified by the Logfile connection property.
Each of these logged operations are assigned to a themed category called a module, and each module has a corresponding short code used to labels individual Sync App operations as belonging to that module.
When this connection property is set to a semicolon-separated list of module codes, only operations belonging to the specified modules are written to the logfile. Note that this only affects which operations are logged moving forward and doesn't retroactively alter the existing contents of the logfile. For example: INFO;EXEC;SSL;META;
By default, logged operations from all modules are included.
You can explicitly exclude a module by prefixing it with a "-". For example: -HTTP
To apply filters to submodules, identify them with the syntax <module name>.<submodule name>. For example, the following value causes the Sync App to only log actions belonging to the HTTP module, and further refines it to exclude actions belonging to the Res submodule of the HTTP module: HTTP;-HTTP.Res
Note that the logfile filtering triggered by the Verbosity connection property takes precedence over the filtering imposed by this connection property. This means that operations of a higher verbosity level than the level specified in the Verbosity connection property are not printed in the logfile, even if they belong to one of the modules specified in this connection property.
The available modules and submodules are:
| Module Name | Module Description | Submodules |
| INFO | General Information. Includes the connection string, product version (build number), and initial connection messages. |
|
| EXEC | Query Execution. Includes execution messages for user-written SQL queries, parsed SQL queries, and normalized SQL queries. Success/failure messages for queries and query pages appear here as well. |
|
| HTTP | HTTP protocol messages. Includes HTTP requests/responses (including POST messages), as well as Kerberos related messages. |
|
| WSDL | Messages pertaining to the generation of WSDL/XSD files. | — |
| SSL | SSL certificate messages. |
|
| AUTH | Authentication related failure/success messages. |
|
| SQL | Includes SQL transactions, SQL bulk transfer messages, and SQL result set messages. |
|
| META | Metadata cache and schema messages. |
|
| FUNC | Information related to executing SQL functions. |
|
| TCP | Incoming and outgoing raw bytes on TCP transport layer messages. |
|
| FTP | Messages pertaining to the File Transfer Protocol. |
|
| SFTP | Messages pertaining to the Secure File Transfer Protocol. |
|
| POP | Messages pertaining to data transferred via the Post Office Protocol. |
|
| SMTP | Messages pertaining to data transferred via the Simple Mail Transfer Protocol. |
|
| CORE | Messages relating to various internal product operations not covered by other modules. | — |
| DEMN | Messages related to SQL remoting. | — |
| CLJB | Messages about bulk data uploads (cloud job). |
|
| SRCE | Miscellaneous messages produced by the product that don't belong in any other module. | — |
| TRANCE | Advanced messages concerning low-level product operations. | — |
This section provides a complete list of the Schema properties you can configure in the connection string for this provider.
| Property | Description |
| Location | Specifies the location of a directory containing schema files that define tables, views, and stored procedures. Depending on your service's requirements, this may be expressed as either an absolute path or a relative path. |
| BrowsableSchemas | Optional setting that restricts the schemas reported to a subset of all available schemas. For example, BrowsableSchemas=SchemaA,SchemaB,SchemaC . |
| Tables | Optional setting that restricts the tables reported to a subset of all available tables. For example, Tables=TableA,TableB,TableC . |
| Views | Optional setting that restricts the views reported to a subset of the available tables. For example, Views=ViewA,ViewB,ViewC . |
| Schema | The type of schema to use. |
Specifies the location of a directory containing schema files that define tables, views, and stored procedures. Depending on your service's requirements, this may be expressed as either an absolute path or a relative path.
The Location property is only needed if you want to either customize definitions (for example, change a column name, ignore a column, etc.) or extend the data model with new tables, views, or stored procedures.
Note: Since this Sync App supports multiple schemas, custom schema files for SendGrid should be structured such that:
Location should always be set to the parent folder, and not to an individual schema's folder.
If left unspecified, the default location is %APPDATA%\\CData\\SendGrid Data Provider\\Schema, where %APPDATA% is set to the user's configuration directory:
| Platform | %APPDATA% |
| Windows | The value of the APPDATA environment variable |
| Linux | ~/.config |
Optional setting that restricts the schemas reported to a subset of all available schemas. For example, BrowsableSchemas=SchemaA,SchemaB,SchemaC .
Listing all available database schemas can take extra time, thus degrading performance. Providing a list of schemas in the connection string saves time and improves performance.
Optional setting that restricts the tables reported to a subset of all available tables. For example, Tables=TableA,TableB,TableC .
Listing all available tables from some databases can take extra time, thus degrading performance. Providing a list of tables in the connection string saves time and improves performance.
If there are lots of tables available and you already know which ones you want to work with, you can use this property to restrict your viewing to only those tables. To do this, specify the tables you want in a comma-separated list. Each table should be a valid SQL identifier with any special characters escaped using square brackets, double-quotes or backticks. For example, Tables=TableA,[TableB/WithSlash],WithCatalog.WithSchema.`TableC With Space`.
Note: If you are connecting to a data source with multiple schemas or catalogs, you must specify each table you want to view by its fully qualified name. This avoids ambiguity between tables that may exist in multiple catalogs or schemas.
Optional setting that restricts the views reported to a subset of the available tables. For example, Views=ViewA,ViewB,ViewC .
Listing all available views from some databases can take extra time, thus degrading performance. Providing a list of views in the connection string saves time and improves performance.
If there are lots of views available and you already know which ones you want to work with, you can use this property to restrict your viewing to only those views. To do this, specify the views you want in a comma-separated list. Each view should be a valid SQL identifier with any special characters escaped using square brackets, double-quotes or backticks. For example, Views=ViewA,[ViewB/WithSlash],WithCatalog.WithSchema.`ViewC With Space`.
Note: If you are connecting to a data source with multiple schemas or catalogs, you must specify each view you want to examine by its fully qualified name. This avoids ambiguity between views that may exist in multiple catalogs or schemas.
The type of schema to use.
The schemas available are NMC and Legacy.
This section provides a complete list of the Miscellaneous properties you can configure in the connection string for this provider.
| Property | Description |
| IncludeCustomFields | A boolean indicating if you would like to include custom fields in the column listing. |
| MaxRows | Specifies the maximum number of rows returned for queries that do not include either aggregation or GROUP BY. |
| Other | Specifies advanced connection properties for specialized scenarios. Use this property only under the guidance of our Support team to address specific issues. |
| PseudoColumns | Specifies the pseudocolumns to expose as table columns, expressed as a string in the format 'TableName=ColumnName;TableName=ColumnName'. |
| Timeout | Specifies the maximum time, in seconds, that the provider waits for a server response before throwing a timeout error. |
| UserDefinedViews | Specifies a filepath to a JSON configuration file that defines custom views. The provider automatically detects and uses the views specified in this file. |
A boolean indicating if you would like to include custom fields in the column listing.
Setting this to true will cause custom fields to be included in the column listing, but may cause poor performance when listing metadata.
Specifies the maximum number of rows returned for queries that do not include either aggregation or GROUP BY.
The default value for this property, -1, means that no row limit is enforced unless the query explicitly includes a LIMIT clause. (When a query includes a LIMIT clause, the value specified in the query takes precedence over the MaxRows setting.)
Setting MaxRows to a whole number greater than 0 ensures that queries do not return excessively large result sets by default.
This property is useful for optimizing performance and preventing excessive resource consumption when executing queries that could otherwise return very large datasets.
Specifies advanced connection properties for specialized scenarios. Use this property only under the guidance of our Support team to address specific issues.
This property allows advanced users to configure hidden properties for specialized situations, with the advice of our Support team. These settings are not required for normal use cases but can address unique requirements or provide additional functionality. To define multiple properties, use a semicolon-separated list.
Note: It is strongly recommended to set these properties only when advised by the Support team to address specific scenarios or issues.
| Property | Description |
| DefaultColumnSize | Sets the default length of string fields when the data source does not provide column length in the metadata. The default value is 2000. |
| ConvertDateTimeToGMT=True | Converts date-time values to GMT, instead of the local time of the machine. The default value is False (use local time). |
| RecordToFile=filename | Records the underlying socket data transfer to the specified file. |
Specifies the pseudocolumns to expose as table columns, expressed as a string in the format 'TableName=ColumnName;TableName=ColumnName'.
This property allows you to define which pseudocolumns the Sync App exposes as table columns.
To specify individual pseudocolumns, use the following format:
Table1=Column1;Table1=Column2;Table2=Column3
To include all pseudocolumns for all tables use:
*=*
Specifies the maximum time, in seconds, that the provider waits for a server response before throwing a timeout error.
The timeout applies to each individual communication with the server rather than the entire query or operation. For example, a query could continue running beyond 60 seconds if each paging call completes within the timeout limit.
Timeout is set to 60 seconds by default. To disable timeouts, set this property to 0.
Disabling the timeout allows operations to run indefinitely until they succeed or fail due to other conditions such as server-side timeouts, network interruptions, or resource limits on the server.
Note: Use this property cautiously to avoid long-running operations that could degrade performance or result in unresponsive behavior.
Specifies a filepath to a JSON configuration file that defines custom views. The provider automatically detects and uses the views specified in this file.
UserDefinedViews allows you to define and manage custom views through a JSON-formatted configuration file called UserDefinedViews.json. These views are automatically recognized by the Sync App and enable you to execute custom SQL queries as if they were standard database views. The JSON file defines each view as a root element with a child element called "query", which contains the SQL query for the view.
For example:
{
"MyView": {
"query": "SELECT * FROM MarketingCampaigns WHERE MyColumn = 'value'"
},
"MyView2": {
"query": "SELECT * FROM MyTable WHERE Id IN (1,2,3)"
}
}
You can use this property to define multiple views in a single file and specify the filepath.
For example:
UserDefinedViews=C:\Path\To\UserDefinedViews.jsonWhen you specify a view in UserDefinedViews, the Sync App only sees that view.
For further information, see User Defined Views.
LZMA from 7Zip LZMA SDK
LZMA SDK is placed in the public domain.
Anyone is free to copy, modify, publish, use, compile, sell, or distribute the original LZMA SDK code, either in source code form or as a compiled binary, for any purpose, commercial or non-commercial, and by any means.
LZMA2 from XZ SDK
Version 1.9 and older are in the public domain.
Xamarin.Forms
Xamarin SDK
The MIT License (MIT)
Copyright (c) .NET Foundation Contributors
All rights reserved.
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
NSIS 3.10
Copyright (C) 1999-2025 Contributors THE ACCOMPANYING PROGRAM IS PROVIDED UNDER THE TERMS OF THIS COMMON PUBLIC LICENSE ("AGREEMENT"). ANY USE, REPRODUCTION OR DISTRIBUTION OF THE PROGRAM CONSTITUTES RECIPIENT'S ACCEPTANCE OF THIS AGREEMENT.
1. DEFINITIONS
"Contribution" means:
a) in the case of the initial Contributor, the initial code and documentation distributed under this Agreement, and b) in the case of each subsequent Contributor:
i) changes to the Program, and
ii) additions to the Program;
where such changes and/or additions to the Program originate from and are distributed by that particular Contributor. A Contribution 'originates' from a Contributor if it was added to the Program by such Contributor itself or anyone acting on such Contributor's behalf. Contributions do not include additions to the Program which: (i) are separate modules of software distributed in conjunction with the Program under their own license agreement, and (ii) are not derivative works of the Program.
"Contributor" means any person or entity that distributes the Program.
"Licensed Patents " mean patent claims licensable by a Contributor which are necessarily infringed by the use or sale of its Contribution alone or when combined with the Program.
"Program" means the Contributions distributed in accordance with this Agreement.
"Recipient" means anyone who receives the Program under this Agreement, including all Contributors.
2. GRANT OF RIGHTS
a) Subject to the terms of this Agreement, each Contributor hereby grants Recipient a non-exclusive, worldwide, royalty-free copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, distribute and sublicense the Contribution of such Contributor, if any, and such derivative works, in source code and object code form.
b) Subject to the terms of this Agreement, each Contributor hereby grants Recipient a non-exclusive, worldwide, royalty-free patent license under Licensed Patents to make, use, sell, offer to sell, import and otherwise transfer the Contribution of such Contributor, if any, in source code and object code form. This patent license shall apply to the combination of the Contribution and the Program if, at the time the Contribution is added by the Contributor, such addition of the Contribution causes such combination to be covered by the Licensed Patents. The patent license shall not apply to any other combinations which include the Contribution. No hardware per se is licensed hereunder.
c) Recipient understands that although each Contributor grants the licenses to its Contributions set forth herein, no assurances are provided by any Contributor that the Program does not infringe the patent or other intellectual property rights of any other entity. Each Contributor disclaims any liability to Recipient for claims brought by any other entity based on infringement of intellectual property rights or otherwise. As a condition to exercising the rights and licenses granted hereunder, each Recipient hereby assumes sole responsibility to secure any other intellectual property rights needed, if any. For example, if a third party patent license is required to allow Recipient to distribute the Program, it is Recipient's responsibility to acquire that license before distributing the Program.
d) Each Contributor represents that to its knowledge it has sufficient copyright rights in its Contribution, if any, to grant the copyright license set forth in this Agreement.
3. REQUIREMENTS
A Contributor may choose to distribute the Program in object code form under its own license agreement, provided that:
a) it complies with the terms and conditions of this Agreement; and
b) its license agreement:
i) effectively disclaims on behalf of all Contributors all warranties and conditions, express and implied, including warranties or conditions of title and non-infringement, and implied warranties or conditions of merchantability and fitness for a particular purpose;
ii) effectively excludes on behalf of all Contributors all liability for damages, including direct, indirect, special, incidental and consequential damages, such as lost profits;
iii) states that any provisions which differ from this Agreement are offered by that Contributor alone and not by any other party; and
iv) states that source code for the Program is available from such Contributor, and informs licensees how to obtain it in a reasonable manner on or through a medium customarily used for software exchange.
When the Program is made available in source code form:
a) it must be made available under this Agreement; and
b) a copy of this Agreement must be included with each copy of the Program.
Contributors may not remove or alter any copyright notices contained within the Program.
Each Contributor must identify itself as the originator of its Contribution, if any, in a manner that reasonably allows subsequent Recipients to identify the originator of the Contribution.
4. COMMERCIAL DISTRIBUTION
Commercial distributors of software may accept certain responsibilities with respect to end users, business partners and the like. While this license is intended to facilitate the commercial use of the Program, the Contributor who includes the Program in a commercial product offering should do so in a manner which does not create potential liability for other Contributors. Therefore, if a Contributor includes the Program in a commercial product offering, such Contributor ("Commercial Contributor") hereby agrees to defend and indemnify every other Contributor ("Indemnified Contributor") against any losses, damages and costs (collectively "Losses") arising from claims, lawsuits and other legal actions brought by a third party against the Indemnified Contributor to the extent caused by the acts or omissions of such Commercial Contributor in connection with its distribution of the Program in a commercial product offering. The obligations in this section do not apply to any claims or Losses relating to any actual or alleged intellectual property infringement. In order to qualify, an Indemnified Contributor must: a) promptly notify the Commercial Contributor in writing of such claim, and b) allow the Commercial Contributor to control, and cooperate with the Commercial Contributor in, the defense and any related settlement negotiations. The Indemnified Contributor may participate in any such claim at its own expense.
For example, a Contributor might include the Program in a commercial product offering, Product X. That Contributor is then a Commercial Contributor. If that Commercial Contributor then makes performance claims, or offers warranties related to Product X, those performance claims and warranties are such Commercial Contributor's responsibility alone. Under this section, the Commercial Contributor would have to defend claims against the other Contributors related to those performance claims and warranties, and if a court requires any other Contributor to pay any damages as a result, the Commercial Contributor must pay those damages.
5. NO WARRANTY
EXCEPT AS EXPRESSLY SET FORTH IN THIS AGREEMENT, THE PROGRAM IS PROVIDED ON AN "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, EITHER EXPRESS OR IMPLIED INCLUDING, WITHOUT LIMITATION, ANY WARRANTIES OR CONDITIONS OF TITLE, NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Each Recipient is solely responsible for determining the appropriateness of using and distributing the Program and assumes all risks associated with its exercise of rights under this Agreement, including but not limited to the risks and costs of program errors, compliance with applicable laws, damage to or loss of data, programs or equipment, and unavailability or interruption of operations.
6. DISCLAIMER OF LIABILITY
EXCEPT AS EXPRESSLY SET FORTH IN THIS AGREEMENT, NEITHER RECIPIENT NOR ANY CONTRIBUTORS SHALL HAVE ANY LIABILITY FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING WITHOUT LIMITATION LOST PROFITS), HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OR DISTRIBUTION OF THE PROGRAM OR THE EXERCISE OF ANY RIGHTS GRANTED HEREUNDER, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
7. GENERAL
If any provision of this Agreement is invalid or unenforceable under applicable law, it shall not affect the validity or enforceability of the remainder of the terms of this Agreement, and without further action by the parties hereto, such provision shall be reformed to the minimum extent necessary to make such provision valid and enforceable.
If Recipient institutes patent litigation against a Contributor with respect to a patent applicable to software (including a cross-claim or counterclaim in a lawsuit), then any patent licenses granted by that Contributor to such Recipient under this Agreement shall terminate as of the date such litigation is filed. In addition, if Recipient institutes patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Program itself (excluding combinations of the Program with other software or hardware) infringes such Recipient's patent(s), then such Recipient's rights granted under Section 2(b) shall terminate as of the date such litigation is filed.
All Recipient's rights under this Agreement shall terminate if it fails to comply with any of the material terms or conditions of this Agreement and does not cure such failure in a reasonable period of time after becoming aware of such noncompliance. If all Recipient's rights under this Agreement terminate, Recipient agrees to cease use and distribution of the Program as soon as reasonably practicable. However, Recipient's obligations under this Agreement and any licenses granted by Recipient relating to the Program shall continue and survive.
Everyone is permitted to copy and distribute copies of this Agreement, but in order to avoid inconsistency the Agreement is copyrighted and may only be modified in the following manner. The Agreement Steward reserves the right to publish new versions (including revisions) of this Agreement from time to time. No one other than the Agreement Steward has the right to modify this Agreement. IBM is the initial Agreement Steward. IBM may assign the responsibility to serve as the Agreement Steward to a suitable separate entity. Each new version of the Agreement will be given a distinguishing version number. The Program (including Contributions) may always be distributed subject to the version of the Agreement under which it was received. In addition, after a new version of the Agreement is published, Contributor may elect to distribute the Program (including its Contributions) under the new version. Except as expressly stated in Sections 2(a) and 2(b) above, Recipient receives no rights or licenses to the intellectual property of any Contributor under this Agreement, whether expressly, by implication, estoppel or otherwise. All rights in the Program not expressly granted under this Agreement are reserved.
This Agreement is governed by the laws of the State of New York and the intellectual property laws of the United States of America. No party to this Agreement will bring a legal action under this Agreement more than one year after the cause of action arose. Each party waives its rights to a jury trial in any resulting litigation.