Send user email messages through your server.
OwnID allows you to use your servers to integrate with your own email provider so you can more completely manage, monitor, and troubleshoot your email communications.
This endpoint handles a request to send an OTP to a specific email address using your own email provider integration. Implement this endpoint according to the specifications:
Headers
You might notice two values in request headers from the OwnID plaform:
ownid-signature
ownid-timestamp
These are part of securing your integration. To help ensure the integration and endpoints are secure, you must validate the signature of the requests as described in our security page.
Adding Custom HTTP Headers
OwnID supports sending custom HTTP headers to the OTP endpoint for improved integration with your email provider. See the Console Configuration
section above for detailed instructions.
Payload
OwnID will make requests to this endpoint with the following payload:
email
- delivery email address of the user.subject
- email subject according to what is defined in the email templates.body
- email body in HTML format, according to what is defined in the email templates. Includes the .Implement these responses for your endpoint:
Status | Description | Return |
---|---|---|
202 | Accepted | return empty body |
401 | Invalid Signature Validation | return empty body |
To get started, go to the OwnID console and login to your account.
From the Apps page, click the app you want to set up SMTP for.
Click the User journey link from the navigation panel.
On the OTP configuration panel, select Email under Delivery Channel.
Click the Custom Provider bar.
When the configuration form opens, enter:
Test your configuration by running through login workflow on a device without biometric verification.
Be sure to complete the email configuration for all your apps before deployment.