ifixing missing thing in the updated links

Author: Kaylyn Sigler

CONTRIBUTING.md

@@ -309,7 +309,7 @@ seo:
   title: Really Great Documentation - SendGrid Documentation | SendGrid
   override: true
   description: This is some really great documentation! I hope you like it!
-  canonical: http://sendgrid.com/docs/really-great-docs
+  canonical: https://sendgrid.com/docs/API_Reference/really-great-docs
 ---
 ```
 

content/docs/for-developers/parsing-email/setting-up-the-inbound-parse-webhook.md

@@ -514,17 +514,17 @@ Content analysis details:   (0.4 points, 5.0 required)
 
 ## 	Other Inbound Parse Documentation
 
-  - [Parse API](https://sendgrid.com/docs/Web_API_v3/Webhooks/parse.html) -
+  - [Parse API](https://sendgrid.com/docs/API_Reference/Web_API_v3/Webhooks/parse.html) -
     Manage Inbound Parse Webhook settings using the Parse API (Web API v3).
-  - [Parse Settings Subuser](https://sendgrid.com/docs/Web_API/Customer_Subuser_API/parse_settings.html) -
+  - [Parse Settings Subuser](https://sendgrid.com/docs/API_Reference/Web_API/Customer_Subuser_API/parse_settings.html) -
     Get current Parse settings and create, edit, and delete entries using the Subuser API (Web API v2).
-  - [Reseller API Parse Settings](https://sendgrid.com/docs/Web_API/Reseller_API/parse_settings.html) -
+  - [Reseller API Parse Settings](https://sendgrid.com/docs/API_Reference/Web_API/Reseller_API/parse_settings.html) -
     Get current Parse settings and create, edit, and delete entries using the Reseller API (Web API v2).
-  - [Reseller Customer Subuser Parse Settings](https://sendgrid.com/docs/Web_API/Reseller_API/Reseller_Customer_Subuser_API/customer_subuser_parse_settings.html) -
+  - [Reseller Customer Subuser Parse Settings](https://sendgrid.com/docs/API_Reference/Web_API/Reseller_API/Reseller_Customer_Subuser_API/customer_subuser_parse_settings.html) -
     Get current Parse settings and create, edit, and delete entries using the Reseller Customer Subuser API (Web API v2).
 
 ## 	Statistics
 
 SendGrid provides [statistics](https://app.sendgrid.com/statistics/parse_webhook) of how many emails parsed over time. You can specify what is displayed on the graph by adjusting the statistics filters.
 
-For more information, please see [Parse Webhook Stats](https://sendgrid.com/docs/Web_API_v3/Stats/parse.html).
+For more information, please see [Parse Webhook Stats](https://sendgrid.com/docs/API_Reference/Web_API_v3/Stats/parse.html).

content/docs/for-developers/partners/azure.md

@@ -229,7 +229,7 @@ completion();
 
 ``` objc
 // Populate the parameters for the SendGrid Web API Call
-// Find more details about the [Web API here](https://sendgrid.com/docs/Web_API/index.html).
+// Find more details about the [Web API here](https://sendgrid.com/docs/API_Reference/Web_API/index.html).
 NSString *username = @"<Your SendGrid Username>";
 NSString *apikey = @"<Your SendGrid Password>";
 NSString *to = @"<Email to Playlist Service from Appendix A>";

content/docs/for-developers/partners/magento.md

@@ -55,7 +55,7 @@ Learn more about your shoppers’ engagement with performance feedback and real-
 * Flexible API and SMTP setup for for easy transactional email Integration.
 * Key email deliverability features including email authentication, reputation monitoring, dedicated IP addresses, and more.
 * Real-time analytics and reporting including opens, clicks, bounces, unsubscribe tracking, and more.
-* Leverage our step-by-step [documentation](https://sendgrid.com/docs) or get quick help from our [24/7 Support Team](https://support.sendgrid.com).
+* Leverage our step-by-step [documentation](https://sendgrid.com/docs/API_Reference) or get quick help from our [24/7 Support Team](https://support.sendgrid.com).
 * This official extension was built for M2 by SendGrid’s dedicated partner-focused teams for continued management and future development.
 
 ## 	Configuration

content/docs/for-developers/sending-email/curl-examples.md

@@ -65,7 +65,7 @@ curl --request POST \
 
 ## 	Scheduling and Cancelling an Email
 
-You may schedule an email to be sent up to 72 hours in the future by using the "send_at" parameter. You may cancel this same scheduled email by using the [Cancel Scheduled Sends endpoint](https://sendgrid.com/docs/Web_API_v3/cancel_schedule_send.html).
+You may schedule an email to be sent up to 72 hours in the future by using the "send_at" parameter. You may cancel this same scheduled email by using the [Cancel Scheduled Sends endpoint](https://sendgrid.com/docs/API_Reference/Web_API_v3/cancel_schedule_send.html).
 
 **Step 1: Generate a batch ID**
 ```bash

content/docs/for-developers/sending-email/getting-started-email-activity-api.md

@@ -270,4 +270,4 @@ This is a full list of basic query types and examples: (replace the data in quot
 ## 	Additional Resources
 
 - [Email Activity Feed API Reference](https://sendgrid.api-docs.io/v3.0/email-activity/filter-all-messages)
-- [Email Activity Feed UI](https://sendgrid.com/docs/help-support/analytics-and-reporting/email-activity-feed.html)
+- [Email Activity Feed UI](https://sendgrid.com/docs/API_Reference/help-support/analytics-and-reporting/email-activity-feed.html)

content/docs/for-developers/sending-email/how-to-create-a-subuser-with-the-api.md

@@ -16,7 +16,7 @@ navigation:
 
 ## Establish the New Subuser (required)
 
-With the [subuser creation API call](http://sendgrid.com/docs/API_Reference/Customer_Subuser_API/subusers.html) you will be able to establish the new subuser's account and profile settings. This call will create the new subuser account, however it does not apply the sending IP for the account, nor does it establish a domain authentication entry or enable website/SMTP access for the subuser.
+With the [subuser creation API call](https://sendgrid.com/docs/API_Reference/Customer_Subuser_API/subusers.html) you will be able to establish the new subuser's account and profile settings. This call will create the new subuser account, however it does not apply the sending IP for the account, nor does it establish a domain authentication entry or enable website/SMTP access for the subuser.
 
 #### Call Example
 
@@ -31,7 +31,7 @@ https://api.sendgrid.com/apiv2/customer.add.json?api_user=ryan.burrer@sendgrid.c
 
 ## Assign an IP to be Used by the New Subuser (required)
 
-Now that you have created the new subuser account, you will need to [add an IP](http://sendgrid.com/docs/API_Reference/Customer_Subuser_API/ip_management.html#-Subuser-IP-Assignment) so that it can send emails. We advise that you first find an available IP for this subuser. You can do so by using the following call:
+Now that you have created the new subuser account, you will need to [add an IP](https://sendgrid.com/docs/API_Reference/Customer_Subuser_API/ip_management.html#-Subuser-IP-Assignment) so that it can send emails. We advise that you first find an available IP for this subuser. You can do so by using the following call:
 
 #### Call Example
 ```
@@ -48,7 +48,7 @@ When defining the parameter 'list' there are a few options you can choose:
 <strong>Response Example<br></strong><img src="http://content.screencast.com/users/Ryan.Burrer/folders/Jing/media/0dc1923b-fff9-4446-aff1-5dcab41929a4/00000096.png" alt="" align="middle">
 </center>
 
-After you have selected the IP that you wish to assign to your subuser account, simply make the API call to [append the IP address](http://sendgrid.com/docs/API_Reference/Customer_Subuser_API/ip_management.html#-Subuser-IP-Assignment).
+After you have selected the IP that you wish to assign to your subuser account, simply make the API call to [append the IP address](https://sendgrid.com/docs/API_Reference/Customer_Subuser_API/ip_management.html#-Subuser-IP-Assignment).
 
 #### Call Example
 ```
@@ -71,9 +71,9 @@ When defining this call's 'set' parameter, you have a few options for appending
 
 ## Assign a domain authentication for the Subuser Account (optional)
 
-After you have created the subuser account and have appended an IP address, you are now ready to assign an _existing_  [authenticated domain](https://sendgrid.com/docs/help-support/sending-email/how-to-set-up-domain-authentication.html) to the account. If you have not yet created the required records for authenticating your chosen domain then this step should be skipped.
+After you have created the subuser account and have appended an IP address, you are now ready to assign an _existing_  [authenticated domain](https://sendgrid.com/docs/API_Reference/help-support/sending-email/how-to-set-up-domain-authentication.html) to the account. If you have not yet created the required records for authenticating your chosen domain then this step should be skipped.
 
-First, you should find out what authenticated domains you have associated with your account. This call will [list your available authenticated domains](http://sendgrid.com/docs/API_Reference/Customer_Subuser_API/whitelabel.html#-List):
+First, you should find out what authenticated domains you have associated with your account. This call will [list your available authenticated domains](https://sendgrid.com/docs/API_Reference/Customer_Subuser_API/whitelabel.html#-List):
 
 #### Call Example
 ```
@@ -87,7 +87,7 @@ https://api.sendgrid.com/apiv2/customer.whitelabel.json?api\_user=ryan.burrer@se
 
 The API response above shows that email.sendgrid.com and email.example.com are both already established domain entries, and can be used by this subuser. If none are displayed then the next step in this process should be skipped.
 
-If you have a authenticated domain entry that you wish to apply to your subuser then you will need to [append the whitelabel entry](http://sendgrid.com/docs/API_Reference/Customer_Subuser_API/whitelabel.html#-Append) to your subuser:
+If you have a authenticated domain entry that you wish to apply to your subuser then you will need to [append the whitelabel entry](https://sendgrid.com/docs/API_Reference/Customer_Subuser_API/whitelabel.html#-Append) to your subuser:
 
 #### Call Example
 ```
@@ -102,7 +102,7 @@ https://api.sendgrid.com/apiv2/customer.whitelabel.json?api_user=ryan.burrer@sen
 
 ## Authenticating the Subuser to Have Website/SMTP Access ** (required)
 
-The final step in creating your new subuser requires you to simply [activate the subuser](http://sendgrid.com/docs/API_Reference/Customer_Subuser_API/authenticate_a_subuser.html) account so that they have website and SMTP access.
+The final step in creating your new subuser requires you to simply [activate the subuser](https://sendgrid.com/docs/API_Reference/Customer_Subuser_API/authenticate_a_subuser.html) account so that they have website and SMTP access.
 
 #### Call Example
 ```
@@ -123,7 +123,7 @@ If you have followed all of these steps then you have just created a new subuser
 
 But wait, there's more...
 
-Now that you have created a new subuser you can change the [Event Notification URL](http://sendgrid.com/docs/API_Reference/Customer_Subuser_API/event_notification_url.html), the subuser's enabled [apps](http://sendgrid.com/docs/API_Reference/Customer_Subuser_API/apps.html), and even set [account limits](http://sendgrid.com/docs/API_Reference/Customer_Subuser_API/account_limits.html) for the subuser.
+Now that you have created a new subuser you can change the [Event Notification URL](https://sendgrid.com/docs/API_Reference/Customer_Subuser_API/event_notification_url.html), the subuser's enabled [apps](https://sendgrid.com/docs/API_Reference/Customer_Subuser_API/apps.html), and even set [account limits](https://sendgrid.com/docs/API_Reference/Customer_Subuser_API/account_limits.html) for the subuser.
 
 <center>
 

content/docs/for-developers/sending-email/how-to-use-a-transactional-template-with-smtp.md

@@ -31,13 +31,13 @@ Example
 ```
 
 You can use this JSON in the `X-SMTPAPI` header of an SMTP message, or in
-the `x-smtpapi` parameter of a [Web API v2 mail send](https://sendgrid.com/docs/Web_API/mail.html#-send) call.
+the `x-smtpapi` parameter of a [Web API v2 mail send](https://sendgrid.com/docs/API_Reference/Web_API/mail.html#-send) call.
 
-If you are using the [Web API v3 mail send endpoint](https://sendgrid.com/docs/Web_API_v3/Mail/index.html), you can specify which transactional template you would like to use simply by setting the template ID in the `template_id` parameter of your JSON payload.
+If you are using the [Web API v3 mail send endpoint](https://sendgrid.com/docs/API_Reference/Web_API_v3/Mail/index.html), you can specify which transactional template you would like to use simply by setting the template ID in the `template_id` parameter of your JSON payload.
 
 <call-out>
 
-Make sure that the version of the template you want to use is set to active by using the [activate endpoint](https://sendgrid.com/docs/Web_API_v3/Transactional_Templates/versions.html#-POST) or by activating it in the UI.
+Make sure that the version of the template you want to use is set to active by using the [activate endpoint](https://sendgrid.com/docs/API_Reference/Web_API_v3/Transactional_Templates/versions.html#-POST) or by activating it in the UI.
 
 </call-out>
 

content/docs/for-developers/sending-email/interspire.md

@@ -37,7 +37,7 @@ Once these settings changes have been made within the Email Settings page within
 
 A bounce event occurs when mail is not able to be handed off to the mail servers at the end recipient's address. This could happen for a number of reasons such as a full mailbox at the address, or the address not existing at all. SendGrid generates a Bounces suppression list when you send mail to addresses that end up bouncing. We suppress subsequent mail to these addresses unless you tell us otherwise in the Email Reports tab within your account. There are two primary ways you can integrate these bounces, generated by SendGrid's system, with Email Marketer. You can download a .CSV file of bounced addresses by navigating to Email Reports > Bounces within your SendGrid account. You can then upload this list into Email Marketer's system in order to mark "subscribers" as "unsubscribed." You can also handle bounces more programmatically by using our Event API to capture POSTed events and then unsubscribing subscribers in the Email Marketer system by making calls to their XML API.
 
-More info on SendGrid's Event API can be found [here](http://sendgrid.com/docs/API_Reference/Webhooks/event.html)
+More info on SendGrid's Event API can be found [here](https://sendgrid.com/docs/API_Reference/Webhooks/event.html)
 
 More info on Interspire's XML API can be found [here](http://www.interspire.com/emailmarketer/pdf/XMLApiDocumentation.pdf)
 

content/docs/for-developers/sending-email/migrating-from-v2-to-v3-mail-send.md

@@ -15,7 +15,7 @@ navigation:
 
 <call-out>
 
-If you are currently using the [Web API v2 mail send endpoint](https://sendgrid.com/docs/Web_API/mail.html), we recommend that you upgrade to the [latest version](https://sendgrid.com/docs/Web_API_v3/Mail/index.html).
+If you are currently using the [Web API v2 mail send endpoint](https://sendgrid.com/docs/API_Reference/Web_API/mail.html), we recommend that you upgrade to the [latest version](https://sendgrid.com/docs/API_Reference/Web_API_v3/Mail/index.html).
 
 </call-out>
 
@@ -32,15 +32,15 @@ With a few quick changes you will be able to take advantage of the improvements
 
 All you need to migrate from the v2 to v3 mail send endpoint is a SendGrid account.
 
-If you are a new SendGrid user and haven’t begun sending email yet, please go straight to our [v3 Mail Send documentation](https://sendgrid.com/docs/Web_API_v3/Mail/index.html) to get started.
+If you are a new SendGrid user and haven’t begun sending email yet, please go straight to our [v3 Mail Send documentation](https://sendgrid.com/docs/API_Reference/Web_API_v3/Mail/index.html) to get started.
 
 ## 	JSON Schema
 
 Some of the biggest improvements made to the mail send endpoint reside in the JSON schema used to format and submit the data payload for your email. While the v2 mail send endpoint relies on a combination of JSON and SendGrid’s x-smtpapi headers, all content and metadata sent via the v3 mail send endpoint is defined using JSON within a single request body.
 
 Below you will find a visual comparison of the v2 and v3 JSON schemas that highlights equivalent parameters between the two versions and any parameters that have been added or removed. Significant additions include the "personalizations", "sandbox_mode", and "bypass_list_management" parameters.
 
-For a more detailed discussion of these new parameters, please visit the [v3 Mail Send Overview](https://sendgrid.com/docs/Web_API_v3/Mail/index.html).
+For a more detailed discussion of these new parameters, please visit the [v3 Mail Send Overview](https://sendgrid.com/docs/API_Reference/Web_API_v3/Mail/index.html).
 
 ![]({{root_url}}/images/v2_vs_v3_mail_send_ga.png)
 
@@ -114,9 +114,9 @@ For example, when attaching a single file named "example_file.jpg", the `attachm
 More Resources
 For additional resources on the v3 Mail Send endpoint, please first visit our other documentation on the v3 Mail Send endpoint:
 
-* [V3 Mail Send Overview](https://sendgrid.com/docs/Web_API_v3/Mail/index.html)
+* [V3 Mail Send Overview](https://sendgrid.com/docs/API_Reference/Web_API_v3/Mail/index.html)
 * [SandBox Mode]({{root_url}}/for-developers/sending-email/sandbox-mode/)
-* [Errors](https://sendgrid.com/docs/Web_API_v3/Mail/errors.html)
+* [Errors](https://sendgrid.com/docs/API_Reference/Web_API_v3/Mail/errors.html)
 * [Personalizations]({{root_url}}/for-developers/sending-email/personalizations/)
 * [cURL Examples for Common Use Cases]({{root_url}}/for-developers/sending-email/curl-examples/)