#3 : Search for SHA256, AWS signature plugins (ADD THEM)
#4 : This is going to be a POST call so...
A. YOU WILL NEED TO CAPTURE and HASH (sha256) an input on the client side (bubble page)
B. Make it fit a JSON template dynamically by creating a workflow -> This will make up your JSON BODY in the API connector later -> add other JSON values as needed for your prompts; may require further formatting, ex: \n
#5 : In the backend: Fill in SHA256 fields for Cannonical
The payload (Yellow) is a dynamic value that you pass from your PROMPT : "(how big are dogs?) in the front end or bubble page value. --> bottom payload left as text to demonstrate Hashing.
NOTE : There are two newlines (enter) after "x-date" -> one small error will ruin your day as the signatures will not match!
#6 : Fill in the AWS signature plugin
#7 : Save result on current user until API is initialized
Note : You have limited time to pass this data to the API connector manually for initialization ...
Use the user field you defined, "string to sign" in this case (result of step 2) as part of the signature in the API connector under AUTHORIZATION (header)
