> For the complete documentation index, see [llms.txt](https://docs.ecwid.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ecwid.com/guides/orders/sync-orders-with-external-services/sync-orders-manually.md).

# Sync orders manually

If you need to send order data to an external service but don't need automation, send API calls manually. For example, you can send them daily after closing the store.

### Receive orders for the last day or week

The [Search orders](/api-reference/rest-api/orders/search-orders.md) call allows you to receive up to 100 orders with one request. Depending on the amount of orders you get, use it once in a day or a week:

{% tabs %}
{% tab title="Daily request" %}
By default, you only need the `createdFrom` query param to search orders for the day:

{% code overflow="wrap" %}

```http
GET /api/v3/STOREID/orders?createdFrom=2025-03-01 00:00:00 HTTP/1.1
Host: app.ecwid.com
Authorization: Bearer secret_token
```

{% endcode %}

Change `STOREID` with your store ID, `2025-03-01 00:00:00` with the current day, and the `secret_token` with the secret access token of your app.

You can also add more conditions for the search and limit fields in the response with other query params. Find the full list of available params in the [API reference](/api-reference/rest-api/orders/search-orders.md#query-params).&#x20;
{% endtab %}

{% tab title="Weekly request" %}
By default, you only need the `createdFrom` query param to search orders for the last week:

{% code overflow="wrap" %}

```http
GET /api/v3/STOREID/orders?createdFrom=2025-03-01 00:00:00 HTTP/1.1
Host: app.ecwid.com
Authorization: Bearer secret_token
```

{% endcode %}

Change `STOREID` with your store ID, `2025-03-01 00:00:00` with the day (like last Monday), and the `secret_token` with the secret access token of your app.

You can also add more conditions for the search and limit fields in the response with other query params. Find the full list of available params in the [API reference](/api-reference/rest-api/orders/search-orders.md#query-params).&#x20;
{% endtab %}
{% endtabs %}

In response, you'll receive a JSON with full order details for the specified period:

<pre class="language-json"><code class="lang-json">{
    "total": 2,
    "count": 2,
    "offset": 0,
    "limit": 100,
<strong>    "items": [
</strong>        {
            "id": "E3LUE",
            ...
        },
        {
            "id": "TL3E4",
            ...
        }
    ]
}
</code></pre>

where:

* `total` – Total number of found orders.
* `count` – Number of orders returned in this request.

If `total` > `100` (for example `250`), then you'll only receive the first 100 orders (1 - 100) in the response. Make an additional request with the `&offset=100` query param to receive orders from 101 to 200, `&offset=100` to receive orders from 201 to 300, and so on.

### Send order details to an external service

With order JSON, you have everything to sync orders to other services like CRMs, spreadsheets, or shipping label systems.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.ecwid.com/guides/orders/sync-orders-with-external-services/sync-orders-manually.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
