> For the complete documentation index, see [llms.txt](https://docs.parcellab.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.parcellab.com/docs/developers/data-elements.md). # Data Elements - [Send Data to parcelLab](https://docs.parcellab.com/docs/developers/data-elements/send-data.md): Send us your tracking and order data via one of our flexible integration options so we can track your deliveries and communicate status updates with your customers.. - [Get Status Updates](https://docs.parcellab.com/docs/developers/data-elements/get-status-updates.md): Provide the latest status of their orders to your customers via our powerful integration options. - [Carrier Integration](https://docs.parcellab.com/docs/developers/data-elements/carrier-integration.md): At parcelLab, we can integrate with any carrier, in any country, in any language to bring you worldwide coverage with all available carrier options. - [Carrier Codes](https://docs.parcellab.com/docs/developers/data-elements/carrier-integration/carrier-codes.md): Find the carrier code to use in order and tracking API requests. - [Data Model](https://docs.parcellab.com/docs/developers/data-elements/data-model.md): The data model covers the foundational elements of a tracking and order record in the parcelLab system via our API v4 Enhanced. - [Tracking Lifecycle Model](https://docs.parcellab.com/docs/developers/data-elements/lifecycle-model.md): Lifecycle is an aggregated state. It is not just "the latest checkpoint". The system evaluates multiple fields and applies precedence rules. - [Delivery Status Model](https://docs.parcellab.com/docs/developers/data-elements/lifecycle-model/status-model.md): The parcelLab platform operates with a status model containing codes that are mapped to each tracking update. --- # 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.parcellab.com/docs/developers/data-elements.md?ask=&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.