Click2Sync Webhooks API Implementation bootstrap templates of frequently needed integrations
You can think of this kind of implementations as a proxy middleman that is translating/transforming the data structures from one side to the standard structure of the other.
- 
GET {{URI_PRODUCTS}} - with offset (int)
- with sortorder param (asc, desc)
- with id param (string)
- with next param (step string tag)
 
- 
GET {{URI_ORDERS}} - with offset (int)
- with sortorder param (asc, desc)
- with id param (string)
- with next param (step string tag)
 
- 
POST {{URI_PRODUCTS}} - without id (CREATE)
- with id (UPDATE)
 
- 
POST {{URI_ORDERS}} - without id (CREATE)
- with id (UDPATE)
 
All hooks are requested with the authorization key header:
- Header name: C2SKey
- Header value: {{the private key you generated on the platform when you generated a connection to Click2Sync}}
You MUST validate that any call you receive to your endpoints are properly authenticated You MUST rename the scripts or endpoints to avoid bots to discover your implementations