From 27c9e5c2e063d7e3d81680cde321cb9f30be1b28 Mon Sep 17 00:00:00 2001 From: Elmer Thomas Date: Wed, 30 Sep 2015 22:12:06 -0700 Subject: [PATCH 1/3] Updated instructions for Console Applications --- source/Integrate/Code_Examples/csharp.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/source/Integrate/Code_Examples/csharp.md b/source/Integrate/Code_Examples/csharp.md index 9b106db1d4..d73a4ea9db 100644 --- a/source/Integrate/Code_Examples/csharp.md +++ b/source/Integrate/Code_Examples/csharp.md @@ -28,6 +28,8 @@ mail.Text = "and easy to do anywhere, even with C#"; var credentials = new NetworkCredential(api_user, api_key); var transportWeb = new Web(credentials); transportWeb.DeliverAsync(mail); +// If developing a Console Application, use the following +// transportWeb.DeliverAsync(mail).Wait(); {% endcodeblock %} {% anchor h2 %} From 0d8827e41c71dea9479904a0c6584fdbe6faeffc Mon Sep 17 00:00:00 2001 From: mbernier Date: Sun, 4 Oct 2015 14:47:53 -0700 Subject: [PATCH 2/3] removing file temporarily --- .../SMTP_API/scheduling_parameters.md | 80 ------------------- 1 file changed, 80 deletions(-) delete mode 100644 source/API_Reference/SMTP_API/scheduling_parameters.md diff --git a/source/API_Reference/SMTP_API/scheduling_parameters.md b/source/API_Reference/SMTP_API/scheduling_parameters.md deleted file mode 100644 index aed297d69f..0000000000 --- a/source/API_Reference/SMTP_API/scheduling_parameters.md +++ /dev/null @@ -1,80 +0,0 @@ ---- -layout: page -weight: 0 -title: Scheduling Parameters -navigation: - show: true ---- - -With scheduling you can send large volumes of email in queued batches or target individual recipients by specifying custom UNIX timestamp parameter. -Using the parameters defined below, you can queue batches of emails targeting individual recipients. - -This parameter allows SendGrid to begin processing a customer’s email requests before sending. SendGrid will then queue those messages and release -them when the timestamp is exceeded. This technique allows for a more efficient way to distribute large email requests and can **improve overall mail delivery time** -performance. This functionality: - -* Improves efficiency of processing and distributing large volumes of email. -* Reduces email pre-processing time. -* Enables you to time email arrival to increase open rates. -* Is available for free to all SendGrid customers. - - -{% info %} -Once you send SendGrid a request with a scheduling parameter, that email request cannot be cancelled and we currently only accept time stamps no greater than 72 hours in advance. -{% endinfo %} - -{% warning %} -Using both `send_at` and `send_each_at` is not valid and will cause your request to be dropped. -{% endwarning %} - -{% anchor h2 %} -Send At -{% endanchor %} - -To schedule a send request for a large batch of emails use the `send_at` parameter which will send all emails at approximately the same time. `send_at` is a [UNIX timestamp](https://en.wikipedia.org/wiki/Unix_time). - -

Example of send_at email header

-{% codeblock lang:json %} -{ - "send_at": 1409348513 -} -{% endcodeblock %} - -{% anchor h2 %} -Send Each At -{% endanchor %} - -To schedule a send request for individual recipients; use `send_each_at` to send emails to each recipient at the specified time. `send_each_at` is a sequence of UNIX timestamps, provided as an array. There must be one timestamp per email you wish to send. - -

Example of send_each_at email header

-{% codeblock lang:json %} -{ - "to": [ - "", - "john@example.com", - "mike@example.com" - ], - "send_each_at": [ - 1409348513, - 1409348514, - 1409348515 - ] -} -{% endcodeblock %} - -To allow for the cancellation of a scheduled send, you must include a batch id with your send. The endpoint for cancellation needs a batch id to cancel with. To generate a valid batch id, use the batch id generation endpoint - -

Example of including a batch_id

-{% codeblock lang:json %} -{ - "to": [ - "", - "john@example.com", - "mike@example.com" - ], - "send_at": [ - 1409348513 - ], - "batch_id": "MWQxZmIyODYtNjE1Ni0xMWU1LWI3ZTUtMDgwMDI3OGJkMmY2LWEzMmViMjYxMw" -} -{% endcodeblock %} From 2056d75dd620564f78df64abf3a3e17bfd326254 Mon Sep 17 00:00:00 2001 From: mbernier Date: Sun, 4 Oct 2015 15:05:13 -0700 Subject: [PATCH 3/3] adding the file back in, shouldnta deleted it --- .../SMTP_API/scheduling_parameters.md | 63 +++++++++++++++++++ 1 file changed, 63 insertions(+) create mode 100644 source/API_Reference/SMTP_API/scheduling_parameters.md diff --git a/source/API_Reference/SMTP_API/scheduling_parameters.md b/source/API_Reference/SMTP_API/scheduling_parameters.md new file mode 100644 index 0000000000..5d9ccea0c3 --- /dev/null +++ b/source/API_Reference/SMTP_API/scheduling_parameters.md @@ -0,0 +1,63 @@ +--- +layout: page +weight: 0 +title: Scheduling Parameters +navigation: + show: true +--- + +With scheduling you can send large volumes of email in queued batches or target individual recipients by specifying custom UNIX timestamp parameter. +Using the parameters defined below, you can queue batches of emails targeting individual recipients. + +This parameter allows SendGrid to begin processing a customer’s email requests before sending. SendGrid will then queue those messages and release +them when the timestamp is exceeded. This technique allows for a more efficient way to distribute large email requests and can **improve overall mail delivery time** +performance. This functionality: + +* Improves efficiency of processing and distributing large volumes of email. +* Reduces email pre-processing time. +* Enables you to time email arrival to increase open rates. +* Is available for free to all SendGrid customers. + + +{% info %} +Once you send SendGrid a request with a scheduling parameter, that email request cannot be cancelled and we currently only accept time stamps no greater than 72 hours in advance. +{% endinfo %} + +{% warning %} +Using both `send_at` and `send_each_at` is not valid and will cause your request to be dropped. +{% endwarning %} + +{% anchor h2 %} +Send At +{% endanchor %} + +To schedule a send request for a large batch of emails use the `send_at` parameter which will send all emails at approximately the same time. `send_at` is a [UNIX timestamp](https://en.wikipedia.org/wiki/Unix_time). + +

Example of send_at email header

+{% codeblock lang:json %} +{ + "send_at": 1409348513 +} +{% endcodeblock %} + +{% anchor h2 %} +Send Each At +{% endanchor %} + +To schedule a send request for individual recipients; use `send_each_at` to send emails to each recipient at the specified time. `send_each_at` is a sequence of UNIX timestamps, provided as an array. There must be one timestamp per email you wish to send. + +

Example of send_each_at email header

+{% codeblock lang:json %} +{ + "to": [ + "", + "john@example.com", + "mike@example.com" + ], + "send_each_at": [ + 1409348513, + 1409348514, + 1409348515 + ] +} +{% endcodeblock %}