A webhook is a method of data transfer that enables web developers to define custom HTTP callbacks that are triggered by certain events.

The Webhooks extension will be removed in October 2022

Existing applications implemented with Webhooks remain operational, but creating new ones is not recommended.

Available as a replacement, there is the new Webhooks API incorporated in the MyCashflow API.

Learn more about the migration to the new Webhooks.

Currently, MyCashflow's Webhooks extension enables you to:

  • Get order data
  • Processing orders
  • Add order comments

The extension can be used to integrate your online store's orders with external software. Integrations can also be implemented by using MyCashflow REST API.

Extensions are not available in MyCashflow Free plan.


Using the extension is free of charge.

Basic principles

Webhooks are used by sending HTTP requests in a programming language (usually by using the cURL software) to the online store's Webhooks address. From the address, MyCashflow's Webhooks extension returns an answer to the request in XML format.

Webhooks commands of the GET type can also be used by entering the desired Webhooks address in the browser's address bar. In this way you can easily test Webhooks requests in your online store.

Whenever an order arrives at your online store, an automatic POST request is sent to the address defined in the extension settings (apart from orders created via MyCashflow API).

Below you can see descriptions of all parts of a Webhooks request:

  1. The connecting point of all Webhooks requests is https://STOREADDRESS.mycashflow.fi/webhooks/
  2. The desired action is then added after the connecting point (see the list of permitted actions): https://STOREADDRESS.mycashflow.fi/webhooks/get
  3. Next the request is supplemented with the relevant GET or POST parameters: https://STOREADDRESS.mycashflow.fi/webhooks/get?order=n
  4. At the end, the online store's individual API key is added to the request: https://STOREADDRESS.mycashflow.fi/webhooks/get?order=n&key=jyghji765rfghji
    • When performing a Webhooks request in the browser's address bar, there is no need to add the API key to the address as long as you are logged in to your online store's admin panel.

The example below illustrates a Webhooks request in which a public order comment is sent to the customer:

    message="Public comment's contents"

Installation and setup

Read also the general extension installation and deployment instructions.

Extensions are not available in MyCashflow Free plan.

In the extension settings, define the address to which Webhooks callbacks should be sent from the online store as well as the API key used for authentication.

When a new order is placed in the online store, an automatic POST request with order details will be sent to the Webhooks address.

After defining the Webhooks settings, make sure that the extension works properly by sending a request to the address you've indicated (see the section below for permitted actions). For instance, you can place a test order so than an automatic order notification is sent.

Webhooks actions

You can see below all actions enabled by MyCashflow's Webhooks extension and their parameters.

See also the examples that illustrate how the actions can be used in practice.

For more information about the structure of the answer in XML format, see #concept_eyp_zpg_4db.

POST /webhooks/processaction=deliver
Marks the order as shipped.
orderIntegersProcessed order ID
send_email0 / 1

The value "1" sends shipping confirmation via email to the customer and shipping address. By default, no confirmation is sent (value 0).

POST /webhooks/processaction=add_comment
Adds a comment to the order.
orderIntegersProcessed order ID
public_message0 / 1Defines whether a comment is public, and a comment notification should be sent via email to the customer and delivery address (a value of 1). Comments are private by default (value 0).
messageTextThe order comment's content in text format.
GET /webhooks/get
Used for fetching one or more orders based on their ID numbers.
orderIntegersID number of the order to be fetched
order_idsInteger table

Used for fetching multiple orders based on their ID numbers.

E.g. order_ids[]=1&order_ids[]=4&order_ids[]=56

GET /webhooks/changes

Used for fetching orders based on their creation and edit dates.

Returns 100 orders at a time starting from the indicated date.


A starting point in time in the Unix timestamp format for fetching orders that were created after that point.

E.g. created_after_ts=1483185600

updated_after_tsStringA starting point in time in the Unix timestamp format for fetching orders that were updated after that point.
GET /webhooks/send
Used for resending a Webhooks message that failed.
orderIntegersOrder ID number

Return values

All data returned by Webhooks is in XML format. You can see a Webhooks' response below in XML format.

See the sample file

The sample below is an answer to the GET /webhooks/changes request used for fetching orders from the online store.

The response contains order, orderer, and order product details.

  <Order id="58">
    <OrderedAt timestamp="1345401893">2012-08-19 21:44:53</OrderedAt>
    <Comments>To be processed quickly, more urgent than other orders.</Comments>
    <PaymentMethod PaymentID="7">Checkout</PaymentMethod>
    <ShippingMethod ShippingID="6">SmartPOST</ShippingMethod>

      <Company>Pulse247 Oy</Company>
      <StreetAddress>Syväojankatu 3A</StreetAddress>
      <Email allowMarketing="false">ismo@pulse247.info</Email>
      <Phone allowMarketing="false">020 741 9172</Phone>

      <Company>Pulse247 Oy</Company>
      <StreetAddress>Syväojankatu 3A</StreetAddress>
      <Phone>020 741 9172</Phone>

        <ProductName>Lacoste light footware</ProductName>
        <Variation id="3">White/42</Variation>
        <UnitPrice vat="0">41.28</UnitPrice>

        <ProductName>Gift card 100€</ProductName>
        <UnitPrice vat="0">66.12</UnitPrice>



        <ProductID PaymentID="7">PAYMENT</ProductID>

        <ProductID ShippingID="6">SHIPPING</ProductID>
        <UnitPrice vat="0">5</UnitPrice>



You can see examples below of successful actions that can be carried out by using the Webhooks extension.

See all the detailed descriptions of all actions and the available parameters.

Fetching individual orders

You can fetch details of individual orders via your online store's Webhooks interface:

GET /webhooks/get?order=43&key=gvbnkiytfghu76tg

When fetching individual orders via the Webhooks interface, the response's root element <Order> will contain the order, orderer and order products details.

Fetching new orders

The Webhooks extension also enables you to send data about new orders that arrived at your online store to an external system.

GET /webhooks/changes?ts=n&key=jhbnji8765rfg

In standard implementations, the external system requests data about events that took place starting from a certain point in time from the interface and processes the orders. At the end, the system saves the timestamp of the last order and uses it in the next request.

An order list returned by Webhooks
<Orders time_from="1336738000" time_to="1345401893" orders="58">
	<Order id="1">
		<OrderedAt timestamp="1336738023">2012-05-11 15:07:03</OrderedAt>
	<Order id="58">
		<OrderedAt timestamp="1345401893">2012-08-19 21:44:53</OrderedAt>

The response to the GET /webhooks/changes request is similar to the response received when individual orders are fetched, but the XML file's root element <Orders> contains an <Order> element for each order returned by the request.

The attributes of the <Orders> element contain information about the timespan from which orders are fetched and the total number of orders included in the material. The <OrderedAt> element used to describe individual orders has also been equipped with the timestamp attribute that indicates the order's timestamp.

You may want to process orders returned via the GET /webhooks/changes interface in order of appearance and, after successful processing, save their individual timestamps rather than the <Orders> element's time_to attribute. In this way, the next search will start from the first order that hasn't been processed, and it will also include orders for which processing previously failed.

Fetching selected orders

Multiple orders can be fetched at a time by using the following Webhooks requests:

GET /webhooks/get?order_ids[]=23&order_ids[]=43&order_ids[]=3&key=jhbnji8765rfg

When multiple orders are fetched, the response's root element <Orders> will contain a separate <Order> element for each returned order, just like the response to the GET /webhooks/changes request.

Marking orders and all their products as delivered

You can use Webhooks requests to mark orders as shipped. To do so, use the following parameters:

POST /webhooks/process

In the example, a shipping confirmation is sent to the customer by using the parameter send_email=1.

Adding order comments

You can add comments to the orders and, optionally, notify the customer about them. To do so, use the following request:

POST /webhooks/process
    message="Message contents"

The example's comment is set as public (and therefore sent to the customer) by using the attribute public_message=1.

Resending Webhooks messages

A failed message can be resent by using the GET /webhooks/send request. The number for the order to be sent is included in the request's order parameter.

GET /webhooks/send?order=34&key=jhbnji8765rfg