Webhook - Setup

Data Type : Module to connect to this WebHook. i.e. Sale Order, Contract, Sale Invoice, etc

Url is mandatory

Fire on New Object : WebHook will be triggered when New object of Data Type created

Fire on Deleted : WebHook will be triggered when object of Data Type deleted

Fire on Changed : WebHook will be triggered when object of Data Type changed

• Any changes from that object of Data Type changed : leave Property Changed blank

• Only specific property change : filled Property Changed (separated by semi-colon for multiple properties)

Non Custom Mode : Webhook will send object of Data Type (serialiased) to end point Url

Custom Mode : Webhook will send contents specified for POST or PUT.

Method (mandatory if API Request) : GET | POST | PUT | …

Content Type (mandatory if API request) : application/json | application/xml | application/x-www-form-urlencoded | … - see https://www.iana.org/assignments/media-types/media-types.xhtml

Headers : [application header request if any ], format :

Contents (mandatory) : [any content to send] OR just type “dummy” for Method GET

• Static contents : i.e. {"status": "completed"}

• Function generated contents (code changes required) : i.e.

  • {FUNCTION:WooCommerceContractUpdateProduct} : Readysell will use Function “WooCommerceContractUpdateProduct” either to generate content, do some request directly or simply just run a logic code.

  • {FUNCTION:WooCommerceGenerateContentRefund} : Readysell will use Function “WooCommerceGenerateContentRefund” either to generate content, do some request directly or simply just run a logic code.

Note : Headers, Contents, and Url in Custom Mode can be replaceable by Object of Data Type values

Format : {OBJECT:[property]}

Example :

GET with dummy contents

Open

Contents with static data

Open

Contents with Functions execution for API Request

Contents with Function execution only. No API request.