# REST API

*Last updated: 2026-06-26*

> Unlike older interface architectures such as SOAP, a REST API does not rely on a dedicated messaging protocol but instead uses the standard HTTP methods GET, POST, PUT, and DELETE directly.

Unlike older interface architectures such as SOAP, a REST API does not rely on a dedicated messaging protocol but instead uses the standard HTTP methods GET, POST, PUT, and DELETE directly. Each resource—a shipment, an order, an inventory record—is addressed via a unique URL, which greatly simplifies system integration. In freight forwarding, REST APIs connect transport management systems, tracking platforms, and customer portals in real time. Because requests are stateless, REST APIs scale well and fit naturally into cloud environments. They are today the default standard for programmatic data exchange between forwarders, carriers, and shippers.

**Source:** [https://developer.mozilla.org/en-US/docs/Glossary/REST_API](https://developer.mozilla.org/en-US/docs/Glossary/REST_API)

## Quick Facts

| Property | Value |
|---|---|
| Term | REST API |
| Language | EN |
| Word count | 95 |
| Last updated | 2026-06-26 |
| Source | https://developer.mozilla.org/en-US/docs/Glossary/REST_API |

---

*Logistics Glossary — Freight Academy: [https://www.freight-academy.com/en/glossary/rest-api](https://www.freight-academy.com/en/glossary/rest-api)*

*Markdown mirror: [https://www.freight-academy.com/api/md/glossary/en/rest-api](https://www.freight-academy.com/api/md/glossary/en/rest-api)*

*JSON summary: [https://www.freight-academy.com/api/v1/glossary/rest-api/llm-summary?lang=en](https://www.freight-academy.com/api/v1/glossary/rest-api/llm-summary?lang=en)*