> 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/introduction/introduction.md).

# Introduction

Selamat datang di Dokumentasi API Lion Parcel. API ini memungkinkan para pengembang, mitra, dan integrator sistem untuk terhubung langsung dengan platform logistik Lion Parcel untuk pembuatan pengiriman

Dengan cakupan hingga 98% wilayah Indonesia dan lebih dari 50 destinasi internasional, Lion Parcel menghadirkan solusi logistik yang andal, skalabel, dan aman untuk bisnis dari berbagai ukuran.

### Fitur Utama

* **Integrasi Mudah**: Hubungkan e-commerce, ERP, atau sistem internal Anda langsung dengan layanan Lion Parcel.
* **Pelacakan Real-Time**: Akses status pengiriman dan pembaruan pengantaran secara langsung.
* **Aman & Andal**: Dibangun dengan autentikasi, kontrol akses, dan ketersediaan tinggi.

### Tentang Dokumentasi

Panduan ini menyediakan informasi tentang:

* Alur bisnis
* Endpoint API dan parameter
* Pengaturan autentikasi dan keamanan
* Panduan integrasi dan daftar periksa
* Contoh permintaan dan respons
* Penanganan error dan informasi versi
* Pemecahan masalah (troubleshooting)


---

# 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/introduction/introduction.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.