> For the complete documentation index, see [llms.txt](https://docs.lionparcel.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lionparcel.com/api/api-reference-en/getting-started/integration-guide-and-checklist.md).

# Integration Guide and Checklist

This guide helps you understand the important steps, requirements, and support needed to integrate your system with the Lion Parcel API from initial preparation through operations

### **1. Integration Requirements**

Before starting the integration, make sure you:

* Have an active cooperation agreement (MOU/PKS)
* Understand the business flow (Client Booking or C2C Auto Pickup/Drop-off)
* Provide an environment **staging** and **production**
* Have a technical team handling the integration
* Prepare the system infrastructure (order system, database, webhook)

### **2. Integration Process**

#### **Registration & Onboarding**

* Register as a partner and get API credentials.

#### **Technical Planning**

* Choose the integration method
* Define the endpoint and system flow

#### **Testing (Staging)**

* Test the API in the staging environment
* Ensure the data flow and system operate according to requirements

#### **Validation & Approval**

* Lion Parcel verifies the test results
* Access to production is granted

#### **Go-Live & Monitoring**

* Start real transactions
* Monitor system performance with Lion Parcel's support team

### **3. Checklist** Integration

<table><thead><tr><th width="60.06182861328125">No</th><th width="477.61138916015625">Item</th><th>Status</th></tr></thead><tbody><tr><td>1</td><td>Active cooperation agreement (MOU/PKS)</td><td>☐</td></tr><tr><td>2</td><td>API Key &#x26; Client ID have been received</td><td>☐</td></tr><tr><td>3</td><td>The integration method has been selected</td><td>☐</td></tr><tr><td>4</td><td>API documentation has been reviewed</td><td>☐</td></tr><tr><td>5</td><td>Staging environment testing has been completed</td><td>☐</td></tr><tr><td>6</td><td>API scenarios have been validated (rate check, shipping, tracking)</td><td>☐</td></tr><tr><td>7</td><td>Approved by Lion Parcel's technical team</td><td>☐</td></tr><tr><td>8</td><td>Access to the production environment has been granted</td><td>☐</td></tr><tr><td>9</td><td>Monitoring &#x26; maintenance are carried out regularly</td><td>☐</td></tr></tbody></table>

### **4. Post-Integration Support**

Lion Parcel provides ongoing support so your operations remain stable and run efficiently:

* **Technical Support**: Assistance with API issues or technical updates
* **Operational Support** : Assistance related to shipping, pickup, or STT issues
* **Monitoring & Feedback** : Regular performance evaluation and continuous improvement


---

# 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.lionparcel.com/api/api-reference-en/getting-started/integration-guide-and-checklist.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.