Events and Events data

Ovoko uses HTTPS to send these notifications to your app as a JSON payload.
Webhooks are attempted to be resent three times after a failure, with intervals of 7 seconds, 35 seconds, and 175 seconds.

This event is activated whenever the status of a specific part changes. For instance, if your item was sold on the Ovoko marketplace, the status will be set to sold, and our system will notify you with a JSON format message indicating that your item has been sold. In the case of a return, once the returned item reaches your warehouse, the part status will change to returned. At this point, you have two options: you can either update the part status to "In Warehouse" if you accept the return, or, if the part is damaged and no longer suitable for sale, you can accept the return and set the status to "Written Off". Once a part is marked as written_off, this action cannot be reversed.

Available statuses:

in_warehouse - Part is in warehouse and available to be sold if it has price.
reserved - Part is reserved for unlimited time, this status can be reverted to “in_warehouse” or can be changed to “sold”, “written_off”, “sold_in_ebay”, "sold_in_allegro”.
sold - Part was sold on Ovoko or locally and is no longer available for sale.
sold_in_ebay - If part was sold through Ovoko integration with Ebay part status will change to “sold_in_ebay”.
sold_in_allegro - If part was sold through Ovoko integration with Allegro part status will change to “sold_in_allegro”
returned - Part is returned from the client, and you received it from the courier. There are two options: if you agree with the return part status will change to “in_warehouse”, if part was damaged you can accept the return and mark part as “written_off”.
written_off - Part status was changed due to canceling it or changing its status to “written_off” in your warehouse system.
unknown_stock_status - This status is related to Allegro integration. Our system changes part status to unknown when we cannot identify if this part is still in the warehouse or already sold.

Example JSON:

{
    "event_id": "101aa6a1-ed22-42f0-84ca-1f8a028a2d28",
    "event_type": "part.status.changed",
    "timestamp": "2023-01-12T14:17:20+02:00",
    "event_data": {
        "part_id": "13",
        "status": "sold",
        "id_bridge": "12345"
    }
}

Example JSON:

{
    "event_id": "101aa6a1-ed22-42f0-84ca-1f8a028a2d28",
    "event_type": "order.created",
    "timestamp": "2023-01-12T14:17:20+02:00",
    "event_data": {
        "order_id": "4555"
    }
}

Example JSON:

{
    "event_id": "101aa6a1-ed22-42f0-84ca-1f8a028a2d28",
    "event_type": "order.cancelled",
    "timestamp": "2023-01-12T14:17:20+02:00",
    "event_data": {
        "order_id": "4555"
    }
}

This event indicates the start of the return process in the system. When a customer initiates a return for a particular part and order, this event is triggered to promptly and accurately inform you about the return initiation. Once this event occurs, you should wait for the part to be returned to you before taking any further action.

Example JSON:

{
    "event_id": "101aa6a1-ed22-42f0-84ca-1f8a028a2d28",
    "event_type": "order.return.created",
    "timestamp": "2023-01-12T14:17:20+02:00",
    "event_data": {
        "return_id": "4555"
        "order_id": "4555"
    }
}

This event serves as a notification when there are changes or updates to the status or details of a previously initiated return. For example, if a client bought 2 parts in one order and firstly opened the return for one part and after a while he decided to return the second part we sent an “Order return update” event so previously opened return would have both parts in it.

Example JSON:

{
    "event_id": "101aa6a1-ed22-42f0-84ca-1f8a028a2d28",
    "event_type": "order.return.updated",
    "timestamp": "2023-01-12T14:17:20+02:00",
    "event_data": {
        "return_id": "4555"
        "order_id": "4555"
    }
}