Cloud Email Delivery Service, Configuring use of the Cloud Email Delivery Service
How to configure an application or host to use the Cloud Email Delivery Service using authenticated SMTP or an API.
If you have been using SMTP to send email to the campus email relays, updating your SMTP configuration is likely to be the easiest way for you to use the Cloud Email Delivery Service
If you would like to use more advanced techniques, an API is also available to developers.
Whether you use the API or SMTP, the service expects an API key along with each request you make, as an authentication token. For SMTP delivery, the API key is used as an SMTP authentication password. You will also need your sub-account number, which will be provided to you by the service team. You can read more about that in the Sending With SMTP section below. The service team can assign an API key for each sub-account, each with its own permissions to restrict what each key is used for.
SMTP (easy mode)
API (advanced mode)
API calls to the SocketLabs API are authenticated using the API key that you generated. Authenticate your calls to the SocketLabs API using the
Authorization header with the
Bearer authentication scheme.
Example Bearer authorization header:
Authorization: Bearer YOUR-API-KEY
If your application or system does not support the
Bearer authentication scheme, you may also use the
Basic scheme. If using the
Basic scheme, you may use any string as the username and then your API key as the password. More information about
Basic authentication can be found here.
Example Basic authorization header:
Authorization: Basic YOUR-API-KEY