Twilio SendGrid Enforced TLS API
The Twilio SendGrid Enforced TLS API allows you to specify whether or not the recipient of your mail send is required to support TLS or have a valid…
Fork copies the collection into your workspace, without the publisher's secrets, so you can add your own key and send requests. Star saves it to your starred APIs (Account › Marketplace) and helps others find it.
Overview
The Twilio SendGrid Enforced TLS API allows you to specify whether or not the recipient of your mail send is required to support TLS or have a valid certificate.
Twilio SendGrid sends all emails with Opportunistic TLS by default, meaning email is sent with TLS, and if the recipient's inbox provider does not accept the TLS encryption, we then send the message unencrypted.
You can optionally choose to enforce TLS encryption, meaning that if the recipient's inbox provider does not accept the TLS encryption, Twilio SendGrid drops the message and sends a block event with the message, “TLS required but not supported” as the description.
Endpoints 2
Enforced TLS
- GETRetrieve current Enforced TLS settings.
/v3/user/settings/enforced_tlsThis endpoint allows you to retrieve your current Enforced TLS settings. The Enforced TLS settings specify whether or not the recipient is required to support… - PATCHUpdate Enforced TLS settings
/v3/user/settings/enforced_tlsThis endpoint allows you to update your Enforced TLS settings. To require TLS from recipients, set require_tls to true. If either require_tls or…
API details
- Base URL
https://api.sendgrid.comhttps://api.eu.sendgrid.com- Authentication
- A bearer token in the Authorization header
- Operations
- 2 operations on 1 pathGET 1PATCH 1
- Main resources
- Enforced TLS 2
- Response formats
application/json- Description format
- OpenAPI 3.1.0, API version
1.0.0 - Links
- Documentation · OpenAPI document · Terms of service · Support
How to test the Twilio SendGrid Enforced TLS API in Swastik Codes
- Open the APISelect “Fork & run in Swastik Codes” on this page. Sign in or create a free account if asked.
- Fork it into your workspaceChoose a workspace. You get your own copy of the Twilio SendGrid Enforced TLS API collection, without the publisher's secrets.
- Add your credentialsThis API uses A bearer token in the Authorization header. Add yours in the collection's variables or an environment; the requests already reference it.
- Send a requestPick an endpoint, for example “Retrieve current Enforced TLS settings.” (GET /v3/user/settings/enforced_tls), and press Send. Check the response, add tests and run the whole collection with the runner.
Frequently asked questions
What is the Twilio SendGrid Enforced TLS API?
The Twilio SendGrid Enforced TLS API allows you to specify whether or not the recipient of your mail send is required to support TLS or have a valid… It is listed under Communication and has 2 endpoints.
Who publishes the Twilio SendGrid Enforced TLS API?
It is listed from SendGrid's public API description (an OpenAPI document), not published by SendGrid on Swastik Codes. Anyone who controls sendgrid.com can claim the profile by adding a DNS TXT record.
What is the base URL of the Twilio SendGrid Enforced TLS API?
Its description lists 2 base URLs: https://api.sendgrid.com, https://api.eu.sendgrid.com. The first is the usual one; the others are typically sandbox or regional servers.
How do I authenticate with the Twilio SendGrid Enforced TLS API?
With A bearer token in the Authorization header.
How many endpoints does the Twilio SendGrid Enforced TLS API have?
2 operations on 1 path (1 GET, 1 PATCH). The largest groups are Enforced TLS.
Is forking the Twilio SendGrid Enforced TLS API free?
Yes. Forking copies the collection into your workspace for free. It has been starred 0 times and forked 0 times.