PartsSource API

Welcome!

This page is designed to show you the available methods to create an integrated solution with PartsSource’s ePartsFinder Catalog and electronic ordering platform. The basic business workflow is broken up into 3 segments but the services can be utilized individually to fit the workflow and design of the integrating solution. The 3 segments are:

1. Identify - Identification is the tools and processes around the ePartsFinder catalog that allow a system to browse available parts, select purchase options and import that information to facilitate the PO creation process. These tools can also be used to create, update and associate material items in the integrating software.
2. Order - Order creation allows for the integrating system to create an order and send it directly into PartsSource to be fulfilled. This enables you to procure and purchase directly from your application and keeps the user in the workflow of the integrated solution.
3. Track - Order tracking and status updates allow the integrating system to pull in important order information as it moves through the procurement process. This includes backordered, shipped (including tracking number) and delivered updates that can then be used to update the work order status.

What is the PartsSource API?

PartsSource provides a series of application programming interfaces (API) for customers and client applications to communicate with the PartsSource systems in order to exchange order information. The interfaces provide the capability of managing the full life cycle of an order, from part search to order requisition to the invoicing of the shipped products.

This API provides a set of web services which are defined as a standard set for use by all integration partners. The individual service methods are configured in such a way that each integration partner can pick and choose which service methods, and in some cases, what order on service calls best fits the business process for that customer. PartsSource will assist in the workflow definition, and try to select the best subset of web service methods to fit that partner. By selecting only the subset of web service methods that a certain interface requires for proper communication and business flow, development time can be reduced, since the entire suite of web service methods does not have to be implemented if they are not needed.

• Part Query Service - Search for parts by number, name and/or optionally manufacturer. Ability to view photos associated with part results.
• Order Status Service - Request the current status of the order, get shipping and tracking info and get order history status.
• Integration Service - The ability to request single sign on (SSO) credentials for seamless integration within ePartsFinder, get the user's cart or quoted items.
• Punchout - The ability to request eQuotes, create orders and purchase items within your ERP/EAM system or CMMS.

More on REST

Representational state transfer (REST) is an abstraction of the architecture of the World Wide Web. More precisely, REST is an architectural style consisting of a coordinated set of architectural constraints applied to components, connectors, and data elements, within a distributed hypermedia system. REST ignores the details of component implementation and protocol syntax in order to focus on the roles of components, the constraints upon their interaction with other components, and their interpretation of significant data elements.