This allows remote systems to post data into SwiftCloud for purpose usually of lead capture, though it can be used for anything – helpdesk, e-sign contract generation flows, etc.
SEE ALSO: Domain Mapping – you can map a domain to SwiftCloud servers, even multiple; most common is subdomains like secure.YourDomain.com
TIP: SwiftCloud may be pre-integrated with API Bridge Systems such as Zapier, and before you bite off the below, you may wish to check those options.
As we migrate to microservice-driven, multi-data center structures, everything is getting turned into APIs, and many will allow for external hooks in/out.
So, instead of a single API, we already have many. All will generally be REST Json.
- eSign / eDocs: Inbound: Inject variables into a contract or doc to be signed
- eSign / eDocs: Outbound: Notification when a doc is signed, including with the URL of the signed doc <requires permissions and IP restriction to download>
- Calendar API: CRUD – most commonly, inject into calendar, but also read / update / delete is possible
- Sequences: Add or remove someone to a sequence of messages i.e. autoresponder / follow-up / appointment reminders
- Contacts: Update (typical with lead scoring, or lead enrichment)
- Lead Capture. Typical is post, but we do also support Rest / Json
- Paywall / Agreements: Used with memberships and subscription systems – can use for a membership website, gym or recurring billing system, etc.
All APIs are subject to rate limits, and generally should get IP-restricted.
What could we do to improve this?