Configure a SocketLabs sending server and credentials
Select the SocketLabs server/account model, authenticate the sending domain, and separate injection credentials from webhook secrets.
Reviewed
SocketLabs has server/account concepts and different Simple Sender/Complex Sender arrangements. Establish the actual provisioned model and server/subaccount before copying a sending or feedback example.
Prepare the application context
- Select the intended sending server or subaccount.
- Add the sending domain and configure its documented DKIM, SPF, and custom-bounce settings.
- Create the credential intended for message injection or SMTP, rather than granting unnecessary configuration administration.
- Record the server/account scope with the credential in secure backend configuration.
The API introduction distinguishes configuration/reporting, Injection API, Event Webhooks, and Inbound API. These are different integration contracts even though they share a provider.
Verify the selected scope
Send one controlled message and inspect activity for the expected server/subaccount. A key working for reporting does not prove permission to inject messages. Domain authentication also does not create an incoming-mail route.
Keep webhook Secret Key/ServerID validation distinct from sending credentials. A broader account webhook may expose more subaccount events than an application should process.
If adopting MailKite for an independent application path, document whether SocketLabs remains responsible for outbound delivery. Credentials, suppression state, and message identifiers do not migrate automatically when changing the send client.