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 Session deleted Estimated reading: 2 minutes 169 views This webhook can post a request to your API when a session (transaction) is deleted from Cellosign database and no longer accessible. Why do I need this? A transaction in Cellosign has a Time To Live attached to it. It may be long or short. Nevertheless, If you require a notification regards a deleted session for any reason so you can fire a new session or inquire why it was deleted this is the API to consume. Session deleted 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_SESSION_DELETED 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 session Example post request { "event": { "type": "WHEF_SESSION_DELETED", "timestamp": "2025-01-26T09:08:37.899782" }, "session": { "id": "vFsQL3P1kr", "reference": "916ca879-0579-4f5b-9dfe-bce341aca065", "process_id": "916ca879-0579-4f5b-9dfe-bce341aca065", "process_number": 76, "transaction_number": 62, "recipient": { "id": 1, "name": "client" }, "labels": { "CUSTOMER_TAG": "CUSTOMER_VALUE" } } } 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
