Current production endpoint map
The table below reflects routes that are either verifiably present or method-advertised on the live namespace.
| Route | Method | Purpose |
|---|---|---|
/wp-json/gath/v1/services |
GET |
Service discovery. |
/wp-json/gath/v1/rates/quote |
POST |
Create a single quote request. |
/wp-json/gath/v1/rates/bulk-quote |
POST |
Create a batch quote request. |
/wp-json/gath/v1/orders |
POST |
Create an order. |
/wp-json/gath/v1/orders/:id |
GET |
Fetch order details. |
/wp-json/gath/v1/orders/:id/status |
PUT |
Update order status. |
Method behavior note
A plain unauthenticated GET to routes like /rates/quote or
/orders may respond with rest_no_route. That usually means the
route expects a different method such as POST rather than indicating that the
route is missing entirely.
Testing tip
Use
OPTIONS or the documented method when verifying a route. A mismatched
HTTP verb can look like a missing endpoint.
Example order lookup
curl -X GET "https://api.gathlogistics.com/wp-json/gath/v1/orders/123" \
-H "Authorization: Bearer YOUR_API_KEY"