Hello world! Welcome to WordPress. This is your first post. Edit or delete it, Read More → kobi September 2, 2022 1 Comment
Uncategorized Quasi distinctio molestiae quibusdam excepturi quia accusamus Molestias et omnis ex. Corrupti aperiam dolor sed vel veniam praesentium sit. Read More → kobi April 28, 2020 No Comments
Uncategorized Optio cum asperiores vel Id ut ratione porro sed rem ipsa sit A voluptatum in et Read More → kobi April 28, 2020 No Comments
Outbound: Webhooks Logged in and Form loaded Estimated reading: 2 minutes 167 views The post request is identical in both “Logged in” and “Form loaded”. Logged in is triggered when client logs in to a form in any mean, such as click on URL in SMS or email Form loaded is triggered when a form is fully loaded into client browser and is operational. Form loaded request and response Following are definitions for Body request posted from Cellosign to your API. ElementWhat it’s for?EventObject that includes Event type: WHEF_CLIENT_FORM_LOADED or WHEF_CLIENT_LOGGED_IN and time stampSessionThis object includes details on the session the webhook was fired from. It includes the following elements:1. “id”: session token2. “reference”: aggregator ID for business process.3. “transaction_number”: ID for transaction that can be located in cellosign UI application4. “recipient”: in case of a workflow this will indicate the recipient id in the process and it’s convention name5. “labels”: This is a key value object in reference to values injected to labels. See API documentation for detailsrecipientThe id of the recipient and conventionlabelsAny key/value that is associated with the sessionclientObject that includes basic information regards the browser that webhook was fired form Example post request Your API can expect this API example for getting information from your API. { "event": { "type": "WHEF_CLIENT_FORM_LOADED", "timestamp": "2025-01-26T10:54:28.291796" }, "session": { "id": "bkIUKTHxws", "reference": "cbbdd32e-8c97-4ec8-a20f-3b6d4d7be2fd", "process_id": "cbbdd32e-8c97-4ec8-a20f-3b6d4d7be2fd", "process_number": 2, "transaction_number": 7, "recipient": { "id": 1, "name": "client" }, "labels": { "CUSTOMER_TAG": "CUSTOMER_VALUE" } }, "client": { "ip": "127.0.0.1", "user_agent": "Best browser ever", "device": "mobile" } } Expected response A successful response from the API should include array of objects, were each object includes “id” and “value” key/value pairs as in this example. Values will be injected into their corresponding id in a session. { "status": "0", "errordesc": "" } Outbound: Webhooks - Previous Archive
