API Inventory Ferguson's API Inventory Product for exchanging inventory data with 3rd party companies. A simple `GET` URI endpoint that has the product **id** as a query path parameter and **locationId** & **regionCode** as query string parameters: <details> <summary>Click to see returned response</summary> </details> If there aren't any products available at that location, the API backend . The API exposes 1 endpoints secured with oauth2 authentication.
1 endpointsFerguson's Location API for exchanging location data with internal Ecommerce platforms and 3rd party companies. > Fetch summary list of locations via pagination: <details> <summary>Click to see example response</summary> </details> --- --- > Fetches details for a specific location based on id and application scope: For external users, this endpoint features a refined response. <detail. The API exposes 3 endpoints secured with oauth2 authentication.
3 endpointsOur Orders API allows you to place a purchase order for fulfillment. You can submit an order or fetch details on one single order. Submit an order(s): Fetches details for a specific order based on id: <b>API Product:</b> Order-Commerce(-UAT/-PROD) <br>. The API exposes 2 endpoints secured with oauth2 authentication.
2 endpointsFerguson'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.
1 endpointsStep 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 | shStep 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.