-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Create /api/send HTTP POST Endpoint for Auth to Call #28
Labels
Comments
nelsonic
changed the title
Create /send-email HTTP POST Endpoint that Other Apps can Call
Create /send HTTP POST Endpoint for Auth to Call
Mar 25, 2020
nelsonic
changed the title
Create /send HTTP POST Endpoint for Auth to Call
Create /api/send HTTP POST Endpoint for Auth to Call
Mar 26, 2020
nelsonic
added a commit
that referenced
this issue
Mar 26, 2020
nelsonic
added a commit
that referenced
this issue
Mar 26, 2020
Valid JWT:
Curl Request
Expect to see the following response: {
"aud": "Joken",
"email": "[email protected]",
"exp": 1585253562,
"iat": 1585246362,
"id": 120,
"iss": "Joken",
"jti": "2nvuqandn7a61pm7ls0000q1",
"name": "Super Successful",
"nbf": 1585246362,
"status": "Pending",
"template": "welcome"
} |
Test it on Heroku:
Response: {
"aud": "Joken",
"email": "[email protected]",
"exp": 1585253562,
"iat": 1585246362,
"id": 24,
"iss": "Joken",
"jti": "2nvuqandn7a61pm7ls0000q1",
"name": "Super Successful",
"nbf": 1585246362,
"status": "Pending",
"template": "welcome"
} |
Documentation added. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The goal of having a separate email service dwyl/auth#39 is to simplify sending email as much as possible.
At present it is relatively easy to send an
email
via theaws-ses-lambda
function, but it requires quite a few steps of setup and 3 AWS environment variables. We don't want anyone contributing to the App to have to follow those steps in order to get the App running on theirlocalhost
. We want them to be able to use a singleDWYL_API_KEY
environment variable which connects them to theauth
andemail
services.email
name
template
In the context of the diagram below, we are building Step 3:
From the perspective of the App, it doesn't (ever need to) know about the Email service.
Everything Email related happens in the background.
The text was updated successfully, but these errors were encountered: