Configure a SparkPost region, sending domain, and API key
Match SparkPost's US/EU or enterprise endpoint to the account and restrict the application's sending permissions.
Reviewed
SparkPost’s API reference defines separate US and EU base URLs, and some enterprise accounts have a dedicated endpoint. Configure the endpoint as part of the connection, not as an assumption hidden in the application.
Prepare the domain and API access
- Select the actual SparkPost/Bird account and its regional or enterprise API endpoint.
- Verify the sending domain and publish the supplied DKIM/authentication records.
- Create an API key with the permissions needed for transmissions; keep administration and analytics access separate where possible.
- Store the key in backend configuration and use the documented API-key authentication model.
The current API overview documents https://api.sparkpost.com/api/v1 and the EU equivalent. Do not assume a Bird-branded account necessarily uses an identical account setup without checking its provisioned service.
Prove the connection
Run one approved transmission and inspect activity in the expected account/region. A missing resource may be an endpoint mismatch rather than a domain that needs recreating.
Record the sending domain, key purpose, endpoint, and message-correlation plan in deployment configuration. Do not put keys into query strings or public Postman exports.
Inbound domains and relay webhooks are separate resources, not a consequence of authenticating a sending domain. MailKite remains a separate service if you choose it for receiving or a later delivery migration.