canonical: https://jentic.com/apis/paypal.com/shipment-tracking # Paypal Shipment Tracking Merchants can use the PayPal Add Tracking API to manage tracking information. Merchants can add tracking numbers and associated information to PayPal. There are 2 ways in which tracking details can be shared to PayPal. If you have a legacy integration that doesn't use the Orders v2 API, share tracking details through the Add Shipping Tracking API. If you . The API exposes 5 endpoints secured with oauth2 authentication. ## For AI agents Programmatically add tracking information for multiple paypal transactions, add tracking information for paypal transaction. Covers 5 operations with oauth2 authentication. ## Scope Does not handle payments, communications, or crm - use for e-commerce only. ## Capabilities - Add tracking information for multiple PayPal transactions - List tracking information - Show tracking information - Update or cancel tracking information for PayPal transaction ## Use cases ### E-Commerce Operations Use the Shipment Tracking to perform e commerce operations programmatically. The API provides 5 endpoints covering core functionality including add tracking information for multiple paypal transactions, add tracking information for paypal transaction, list tracking information. Example prompt: Call POST /v1/shipping/trackers-batch to add tracking information for multiple paypal transactions ### Automated trackers Management Automate trackers operations by combining multiple Shipment Tracking endpoints. Agents can add tracking information for paypal transaction and then list tracking information in a single workflow. Example prompt: Call POST /v1/shipping/trackers to add tracking information for paypal transaction, then verify the result ### AI Agent Integration via Jentic AI agents discover and call Shipment Tracking endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle oauth2 tokens manually. Example prompt: Search Jentic for 'add tracking information for multiple paypal transactions', load the operation schema, and execute with Jentic-managed credentials ## Key endpoints | Method | Path | Description | | --- | --- | --- | | POST | /v1/shipping/trackers-batch | Add tracking information for multiple PayPal transactions | | POST | /v1/shipping/trackers | Add tracking information for PayPal transaction | | GET | /v1/shipping/trackers | List tracking information | | GET | /v1/shipping/trackers/{id} | Show tracking information | | PUT | /v1/shipping/trackers/{id} | Update or cancel tracking information for PayPal transaction | ## Key resources - **trackers** — Use the `/trackers` resource to create and manage tracking information for PayPal transactions. - **trackers-batch** — Use the `/trackers-batch` resource to add tracking information for multiple PayPal transactions. - **carriers-recommend** — Use the `/carriers-recommendations` to detect the possible carriers corresponding the tracking info - **carriers** — Use the `/carriers` resource to list/detect all the carriers available for tracking in PayPal and it - **shipments** — Use the `/shipments` resource to fetch all the shipments associated with a given Paypal Account Id. ## Why Jentic - **Setup:** Wiring PayPal Shipment Tracking by hand means running its OAuth 2.0 flow, refreshing Bearer tokens, and choosing the right sandbox or live host before you can add or update trackers. Through Jentic you install once, import Shipment Tracking from the API Directory, store the client credentials once, and your agent calls it. - **Permission scoping:** Shipment Tracking puts the tracker id in the URL path (/v1/shipping/trackers/{id}), so a rule can pin your agent to reading one tracker. You choose the operations it may call, so adding trackers in batch or updating a tracker is not included unless you add them. - **Credential handling:** Your PayPal OAuth client id and secret are stored once, encrypted, by your own Jentic One instance and injected at execution time, with token refresh handled for you. They never enter the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'add tracking information for multiple PayPal transactions' or 'read a tracker', and Jentic returns the matching Shipment Tracking operation with its input schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **Shopify** — Alternative e commerce API - **Stripe** — Alternative e commerce API ## FAQ ### What authentication does the Shipment Tracking use? The Shipment Tracking uses OAuth 2.0 for authorization. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context. ### Can I add tracking information for multiple paypal transactions with the Shipment Tracking? Yes. Use the POST /v1/shipping/trackers-batch endpoint. The API returns structured JSON responses that agents can parse and act on directly. ### What are the rate limits for the Shipment Tracking? Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer. ### How do I add tracking information for multiple paypal transactions through Jentic? Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'add tracking information for multiple paypal transactions'. Jentic returns the matching Shipment Tracking operation with its input schema. Load the schema and execute the call - credentials are injected automatically. ### How many endpoints does the Shipment Tracking have? The Shipment Tracking exposes 5 endpoints covering trackers, trackers-batch, carriers-recommend operations. ### Can I limit what my agent is allowed to do with the PayPal Shipment Tracking API? Yes. Because you self-host Jentic One, your own rules decide which of the five operations the agent may call and which credentials it may use. Since the tracker id sits in the URL path (/v1/shipping/trackers/{id}), you can pin the agent to reading a single tracker while withholding batch adds via /v1/shipping/trackers-batch, single-tracker creates, or updates and cancellations through PUT /v1/shipping/trackers/{id}. Each operation is granted only when you add it, so the agent can do nothing beyond the scope you define.