canonical: https://jentic.com/apis/adn.t-mobile.com/adn-t-mobile # Adn T Mobile T-Mobile Order API The T-Mobile Order API places, queries, and updates product orders through T-Mobile's partner experience layer. It gives partner systems a programmatic way to submit a product order, check an existing order's status, and push updates to an in-flight order, so ordering can be automated end to end. ## For AI agents Submit product orders to T-Mobile, query the status of existing orders, and push updates to orders that are already in flight through the partner ordering layer. ## Scope Does not handle payment capture, inventory, or shipment tracking. Use for T-Mobile partner product ordering only. ## Capabilities - Submit a new product order to T-Mobile through the partner experience layer - Query the status and details of an existing order - Push updates to an in-flight order such as corrected details - Automate order intake from a partner storefront without manual entry - Track order state changes to keep downstream systems in sync ## Use cases ### Agent-Driven Order Placement An AI agent handling a partner storefront can submit approved carts to T-Mobile as product orders and return the resulting order identifier to the calling system. This removes manual re-keying between the storefront and T-Mobile's ordering layer. Through Jentic the agent discovers the order-placement operation by intent and runs it with credentials injected at call time. Example prompt: Place a product order for the items in this approved cart and return the order ID ### Order Status Automation Support and operations agents can poll the query operation to report on where an order stands and notify customers when it progresses. Because the status comes back structured, the agent can branch on it without scraping a portal. This keeps customers informed without a human checking each order. Example prompt: Check the status of order ABC-987 and notify the customer if it has shipped ### Order Update Workflows When an order needs a correction before fulfillment, an agent can push the change through the update operation rather than cancelling and re-placing it. This handles late address or detail corrections cleanly. The agent amends only the order it is authorized to touch. Example prompt: Update order ABC-987 with the customer's corrected shipping address ## Key endpoints | Method | Path | Description | | --- | --- | --- | | POST | `/productOrder` | Submit a new product order | | POST | `/queryOrder` | Query an existing order's status | | PUT | `/updateOrder` | Update an in-flight order | ## Key resources - **Product orders** — New orders submitted to T-Mobile through the partner ordering layer - **Order queries** — Status and detail lookups for existing orders - **Order updates** — Changes pushed to orders that are still in flight ## Why Jentic - **Setup:** Wiring the T-Mobile Order API by hand means completing an OAuth 2.0 flow, refreshing tokens, and mapping the order request and response formats yourself. Through Jentic you install once, import the API from the Directory, store the OAuth credentials once, and your agent calls it. - **Permission scoping:** The API exposes placing, querying, and updating orders, and orders are identified in the request body rather than the URL path, so rules bound which of these operations the agent may call. You can allow status queries while withholding order placement and updates. - **Credential handling:** Your T-Mobile OAuth credentials are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'place a product order' or 'check an order's status', and Jentic returns the matching T-Mobile Order API operation with its input schema so the agent calls the right endpoint without reading the reference docs. ## Related APIs - **Square** — Square handles orders and payments for general commerce rather than T-Mobile partner ordering. - **Shopify** — Shopify runs the storefront that captures carts an agent then submits to T-Mobile. - **Walmart Orders** — Walmart Orders covers marketplace order fulfillment across a separate channel. ## FAQ ### Is there a T-Mobile Order API MCP server? You don't need an MCP server to connect your agent to the T-Mobile Order API. Jentic imports it from the API Directory, stores your OAuth credentials once, and your agent places and queries orders directly. No extra server sits in the agent's context. ### Can I limit what my agent is allowed to do with the T-Mobile Order API? Yes. The API has three operations: placing, querying, and updating orders, and you choose which the agent may call. A common setup allows querying order status but not placing or updating, so the agent can report on orders without changing them. Orders are identified in the request body rather than the URL path, so rules bound which operations the agent may use. Every call is logged. ### What authentication does the T-Mobile Order API use? The T-Mobile Order API uses OAuth 2.0 for authentication, per its OpenAPI spec. Through Jentic the OAuth credentials are stored encrypted by your own Jentic One instance and injected when the agent makes a call, so they never appear in the agent's prompt or logs. ### Can my agent update an order after it is placed with the T-Mobile Order API? Yes. The update operation pushes changes to an in-flight order, such as a corrected address, so an agent can amend an order it previously submitted without re-creating it. ### What are the rate limits for the T-Mobile Order API? The OpenAPI spec does not specify rate limits. Check T-Mobile's partner documentation for the current limits before scaling an agent's order volume. ### How do I place an order with the T-Mobile Order API through Jentic? Search Jentic for 'place a product order' and it returns the order-placement operation with its input schema. Store your OAuth credentials once, then your agent submits orders. To run it on your own infrastructure, install Jentic One from its GitHub repo.