{"id":4033,"date":"2021-01-17T19:39:48","date_gmt":"2021-01-18T00:39:48","guid":{"rendered":"https:\/\/swiftcloud.ai\/support\/?p=4033"},"modified":"2021-01-26T17:49:16","modified_gmt":"2021-01-26T22:49:16","slug":"electronic-signature-api","status":"publish","type":"post","link":"https:\/\/swiftcloud.ai\/supportwebadmin\/electronic-signature-api","title":{"rendered":"API: Electronic Signature"},"content":{"rendered":"
\nGOAL (Most Common):
\nSend variables into an e-Sign Contract.<\/h3>\n<\/blockquote>\nMETHODS:<\/p>\n
\n
- POST (simple and fast)<\/li>\n
- GET (URL string)<\/li>\n
- API (below)<\/li>\n<\/ul>\n
NOTE: API in is easy, there’s no security risk. API outbound, for security reasons, is much more restrictive. You will need API keys and IP based restriction on outbound APIs.<\/p><\/blockquote>\n
POST (METHOD 1)<\/strong><\/h2>\n
You can simply post any variables into a SwiftCloud doc, and as long as the variable matches, SwiftCloud will handle the rest. You can add “readonly” into the shortcode to make it look like regular text, not front-end-editable.<\/p>\n
Post location: Simply post right to your actual doc URL. Ensure the variable names match in the source-code, and we’ll do the rest. You can optionally include hidden variables (like session ID, tracking variables).<\/p>\n
NOTE: Inbound API is throttled. If you are running TV ads or expect a large number of submissions in a short time period, let us know.<\/p>\n
GET (METHOD 2)<\/strong><\/h2>\n
Simply append any variable to the end of your eSign doc \/ eDoc \/ Landing Page \/ Scheduler \/ etc – i.e.<\/p>\n
https:\/\/LinkToYourPageHere.ai?swift_email=John@Doe.com&extra_sessionID=1234<\/pre>\nMore Common Use Cases<\/h4>\n
\n
- Facebook Lead Form Ads – Will notify you, create the workroom, fire autoresponder messages, create the contact<\/li>\n
- Zapier, IFFFT, Tray.IO, n8n.io (API bridge systems) integrations<\/li>\n
- WordPress Forms for lead capture etc.<\/li>\n
- Any other data capture, lead capture<\/li>\n<\/ul>\n
API INBOUND (METHOD 3)<\/strong><\/h2>\n
Below is details for our incoming API using Json.<\/p>\n
HOW TO USE IT<\/h3>\n
\n
- Create a Form same as usual – go to your main drive page. Click the orange Create New button, select Form, and give it a name (just for you, not visible to clients). Move to a subfolder if you choose.<\/li>\n
- Next, at the very top, choose API or Facebook. Both do the same, but Facebook will help you connect directly.<\/li>\n
- In the pink box, set what you want to happen for the guest \/ client \/ form-filler – what email they should get if any, and any optional sequence of messages.<\/li>\n
- In the blue box, set your own notification options. Email you? Email someone else? Configure as needed<\/li>\n
- You’re done – most likely. More advanced optional controls are available in the grey box for non-english language controls, etc.<\/li>\n<\/ol>\n
CODE EXAMPLE<\/h3>\n
Note 2 bits of data are always required for the absolute bare minimum:<\/p>\n
\n
- Form ID<\/li>\n
- Email*<\/li>\n<\/ol>\n
*Note we may soon allow mobile phone (with SMS verification); if you need this let us know.<\/p>\n
POST TO: https:\/\/swiftcrm.com\/is\/api\/formhandlings<\/p>\n
Login is not required. No data can be retrieved from this API. We may add IP restriction down the road if needed.<\/p>\n
Set the header for API :<\/b> \u00a0<\/span>Content-Type :<\/span> application\/json<\/span><\/p>\n
NOTE: KNOWN ISSUE: Underscore _ is not allowed in variable names. This message will be removed when solved; for now just please use – hyphen instead of _ underscore in the variable names.<\/p><\/blockquote>\n
{\"formid\":\"233F283\",<\/span>\r\n\"swift_name_both\":\"Tester Name\",<\/span>\r\n\"email\":\"wamasoftware2@gmail.com\",<\/span>\r\n\"FundsNeededFor\":\"new tractor\"}<\/span><\/pre>\n
API Response:<\/h3>\n
success, fail<\/pre>\nAs always, if you have any questions let us know and we’ll update this entry to be more clear.<\/p>\n
OUTBOUND Electronic Signature \/ eDocs API<\/h2>\n
Most common: Simply select the Remote Post option in the blue box on a form, doc, chatbot, landing page, etc. and define the remote URL.<\/p>\n