We often get asked about ShelfAware’s ability to connect to other software systems. The most common request is a connection to the Supplier’s ERP or Consumer’s MRP systems. The simple answer is “Yes!” we can connect to almost any other software system with the use of modern APIs. Do you have questions about the API process or would you like test your current knowledge on the topic? Request a demo and read our short quiz below to test your basic knowledge of APIs.
Questions
- What metaphor can be used to describe how an API works?
- A) A lock and key
- B) A pipeline
- C) A boat
- D) A road map
- What three things must be known for an API pipeline to work effectively? (Choose all that apply)
- A) The expectations on either end of the pipeline
- B) The cost of the internet connection
- C) What data will be moving through the pipeline
- D) The overall reason (“why”) the pipeline is being built
- What analogy can be used to explain knowing a data endpoint versus knowing how to connect to it?
- A) Knowing a phone number vs. knowing who will answer
- B) Knowing a house’s address vs. knowing the directions to get there
- C) Knowing a web link vs. knowing the website password
- D) Knowing a book’s title vs. knowing the page count
- True or False: APIs are “set it and forget it” solutions that require no ongoing maintenance after deployment.
- Why do API pipelines require ongoing maintenance over time?
- A) Data files expire every month.
- B) Systems receive updates (especially security updates) that can break connections.
- C) API keys must be changed weekly.
- D) Servers automatically reset their pipelines.
- What are two practical considerations that must be defined before estimating the time and cost to create an API? (Choose two)
- A) Data Source / Scope: Who writes and/or exposes the API endpoint and what information needs to be shared
- B) Ongoing maintenance: Identify who will maintain the API, especially when system/security updates occur
- C) Buzzwords and hype
- D) Immediately going to AI to build one
Answer Key
- B) A pipeline
- A, C, and D (The expectations on either end, what data is moving, and the overall “why”)
- B) Knowing a house’s address vs. knowing the directions to get there
- False (APIs are not “set it and forget it”)
- B) Systems receive updates (especially security updates) that can break connections.
- The two considerations are:
- A) Data source / Scope: Who writes and/or exposes the API endpoint and what information needs to be shared
- B) Ongoing maintenance: APIs are not “set it and forget it” so identify who will maintain the API when system/security updates occur
Do you have other questions? Here is a short video with a few Frequently Asked Questions answered by our Founder Andrew Johnson.
Facebook
X
LinkedIn
