> For the complete documentation index, see [llms.txt](https://synthesys-2.gitbook.io/synthesys-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://synthesys-2.gitbook.io/synthesys-docs/network-overview.md).

# Network Overview

The Synthesys Network API is a platform- and network-agnostic gateway for subscribing to and redeeming supported fund tokens. It is not tied to any specific issuance platform or blockchain — sub-distributors use the same API to transact in any supported fund, on any supported network.

Sub-distributors access fund tokens through Pinetree, the master distributor on the Synthesys Network. All subscription and redemption orders are routed via the Synthesys Network API to Pinetree, who processes requests within one business day subject to a daily cut-off time. Sub-distributors settle directly with Pinetree — not with the fund.

### Parties Involved

| Party               | Role                                                                                                                                                                           |
| ------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **End Investor**    | Submits buy/sell requests to the sub-distributor.                                                                                                                              |
| **Sub-Distributor** | Authorised distribution partner. Routes orders via the Synthesys Network API and settles fiat or stablecoins directly with Pinetree.                                           |
| **Pinetree**        | Master distributor. Receives all orders from sub-distributors, processes them within one business day, and manages token delivery and proceeds distribution.                   |
| **Synthesys**       | Operates the Synthesys Network and the Network API infrastructure that enables sub-distributors to subscribe to and redeem any supported fund token across supported networks. |

### Who Is This For?

The Network API is consumed by two personas:

* **Distributors** call the investor and order endpoints from their own backend to onboard end-investors, surface live share-class and NAV data inside their app or portal, and place subscription orders on their investors' behalf.
* **Internal tooling** uses the same endpoints for reconciliation, monitoring, and analytics.

If you are building an end-investor mobile or web app, you should call the API from your own backend rather than directly from the browser. This keeps credentials, audit attribution, and rate-limit accounting on the server side where they belong.

### Next Steps

* How It Works — Step-by-step walkthrough of subscription and redemption flows with a worked example.
* Integration Guide — Technical guide for connecting your backend to the Network API.
* API Reference — Full endpoint documentation.


---

# 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://synthesys-2.gitbook.io/synthesys-docs/network-overview.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.