Ferguson Api API-Shipping
Browse all Swaggerhub Ferguson Api APIs★ Only Publicly Available OpenAPI DocumentE CommerceStorefrontoauth21 EndpointsREST
For Agents
Programmatically returns shipping options. Covers 1 operations with oauth2 authentication.
Use for: I need to returns shipping options, Find available e commerce operations, Get the current status of API-Shipping resources, List all records from API-Shipping
Not supported: Does not handle payments, communications, or crm — use for e-commerce only.
Ferguson's API Shipping Product for getting shipping rates. Returns an array of shipping rates based on destination city/state/postal code and list of products. Takes a JSON request payload that describes the Ferguson location id, destination address and products. **_NOTE: basePath is actually /v1/shipping but is removed for readability._**. The API exposes 1 endpoints secured with oauth2 authentication.
Install Jentic One Beta
Connect the API-Shipping to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the API-Shipping, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with API-Shipping API.
Returns shipping options
Manage e commerce data programmatically
Integrate API-Shipping into automated workflows
Query and filter API-Shipping records by parameters
Monitor API-Shipping operational status and events
Use Cases
Patterns agents use API-Shipping API for, with concrete tasks.
★ E-Commerce Operations
Use the API-Shipping to perform e commerce operations programmatically. The API provides 1 endpoints covering core functionality including returns shipping options.
Call POST /v1/shipping to returns shipping options
Data Retrieval and Monitoring
Query API-Shipping resources on a schedule to track changes, generate alerts, or feed downstream dashboards. Agents poll relevant endpoints, compare against previous state, and trigger actions when thresholds are crossed.
Poll the primary API-Shipping endpoint, compare response to last known state, and alert if changed
AI Agent Integration via Jentic
AI agents discover and call API-Shipping 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.
Search Jentic for 'returns shipping options', load the operation schema, and execute with Jentic-managed credentials
Key Endpoints
1 endpoints — ferguson's api shipping product for getting shipping rates.
METHOD
PATH
DESCRIPTION
POST
/v1/shipping
Returns shipping options
POST
/v1/shipping
Returns shipping options
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
API-Shipping oauth2 credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw secrets never enter the agent context.
Intent-based discovery
Agents search by intent (e.g., 'returns shipping options') and Jentic returns the matching API-Shipping operation with its input schema, so the agent can call the right endpoint without browsing docs.
Time to first call
Direct API-Shipping integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
Alternative
Stripe
Alternative e commerce API
Choose Stripe when you need a different approach to e commerce operations
FAQs
Specific to using API-Shipping API through Jentic.
What authentication does the API-Shipping use?
The API-Shipping uses OAuth 2.0 for authorization. Through Jentic, these credentials are stored encrypted in the MAXsystem vault and injected at execution time, so raw secrets never enter the agent context.
Can I returns shipping options with the API-Shipping?
Yes. Use the POST /v1/shipping endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the API-Shipping?
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 returns shipping options through Jentic?
Install the Jentic SDK with pip install jentic, authenticate at https://app.jentic.com/sign-up, then search for 'returns shipping options'. Jentic returns the matching API-Shipping operation with its input schema. Load the schema and execute the call — credentials are injected automatically.
How many endpoints does the API-Shipping have?
The API-Shipping exposes 1 endpoints covering shipping operations.
GET STARTED