Application Programming Interfaces, also known as API's are the solution to every integration problem you have.
And if your BAS has an open an API then your integration options are unlimited.
Or at least that's what all the marketing folks would like you to believe. The problem with all the buzz around API's, SDK's, and system integration is that the folks writing and speaking on the topics couldn't integrate their way out of a cardboard box. So when a BAM Nation subscriber named Dave reached out to me asking me to help clarify how an API works I was thrilled to have the opportunity to discuss the topic!
In this episode you will learn:
- Why having an open API doesn't automatically mean integration
- What 3 steps you need to take before using an API
- The differences between an API and SDK
- Why you may need a coding background to work with an API... and why you may not...
- A walkthrough of the system integration process using an API
Thanks for Listening!
If you have a specific question, you can send me a voicemail or e-mail message at the Contact Page.
I'm glad to have you here, and I look forward to your feedback in the comments below.
Subscribe via iTunes
Subscribe via Stitcher
You're Learning About
- Why having an open API doesn't automatically mean integration
- What 3 steps you need to take before using an API
- The differences between an API and SDK
- Why you may need a coding background to work with an API... and why you may not...
