> For the complete documentation index, see [llms.txt](https://docs.squidrouter.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.squidrouter.com/getting-started/integrator-quickstart.md).

# Integrator Quickstart

Create your first Squid cross-chain route request

### Step 1: Request an Integrator ID

Squid issues Integrator IDs on a limited basis and upon review. To get started:

1. Submit a [partnership request](https://squidrouter.typeform.com/partnerships) to request an Integrator ID.
2. Once reviewed and approved, the Squid team will follow up with your credentials.

Step 2: Make Your First Route Request

Replace `YOUR_INTEGRATOR_ID` in the following curl command with your actual integrator ID and replace `ADD_ADDRESS` with an address, then paste it into your terminal and hit enter:

```xml
curl -X POST 'https://v2.api.squidrouter.com/v2/route' \
-H 'x-integrator-id: YOUR_INTEGRATOR_ID' \
-H 'Content-Type: application/json' \
-d '{
  "fromAddress": "ADD_ADDRESS",
  "fromChain": "56",
  "fromToken": "0x55d398326f99059fF775485246999027B3197955",
  "fromAmount": "1000000000000000",
  "toChain": "42161",
  "toToken": "0xaf88d065e77c8cC2239327C5EDb3A432268e5831",
  "toAddress": "ADD_ADDRESS"
}'
```

**Congrats, you've submitted your first route request!**

#### Parameter Explanation:

* `fromAddress`: The address initiating the swap (replace with your address)
* `fromChain`: The source chain ID (56 is BNB Chain)
* `fromToken`: The token address to swap from (USDT on BNB Chain in this example)
* `fromAmount`: The amount to swap (in the smallest unit of the token)
* `toChain`: The destination chain ID (42161 is Arbitrum)
* `toToken`: The token address to swap to (USDC on Arbitrum in this example)
* `toAddress`: The address receiving the swapped tokens

### Step 3: Interpret the Response

If successful, you'll receive a JSON response with the optimal route details. Key fields include:

* `route.estimate.toAmount`: Estimated amount you'll receive
* `route.estimate.feeCosts`: Breakdown of fees
* `route.transactionRequest`: Data needed to execute the swap

### Build With Squid

Now that you've created a route request. Choose how you want to build with Squid.

<div><figure><img src="https://4247625265-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FtXbXyuWIO2PwzNc5Dets%2Fuploads%2F1dMwuKU2I7mP5iLYwXwk%2FWidget.png?alt=media&amp;token=1cb7e224-c047-47b3-b5fd-b82c097b19f6" alt=""><figcaption></figcaption></figure> <figure><img src="https://4247625265-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FtXbXyuWIO2PwzNc5Dets%2Fuploads%2FDwqgoVAax0HVJg3kVzQN%2FAPI%3ASDK.png?alt=media&amp;token=926543e3-3eab-49c7-8a2c-9c21066f3260" alt=""><figcaption></figcaption></figure></div>

## **Squid’s Integrators Include**


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.squidrouter.com/getting-started/integrator-quickstart.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
