While Application Programming Interfaces (APIs) are key to 'open' platforms, they are frequently misunderstood and over-hyped in physical security. While APIs can provide great benefits, using them is much more complex than often mentioned in sales calls and magazines.
*** **** ** **** ** ******** security ** ** ***** ********* ******* to **** ********. ******** *******:
*** ***** **** **** ********* ** pre-sales ********** ***** * ******** ** integrator **** * ******: "**** **** system **** **** '*'?" ***** * could ** *** ****** ** ******** systems ** *** ****** ** *************.
*** ******* ****** ** *** ***** person **:
"****, ** **** ** ***."
**** ** *** ** *** ******** and ********** ********* ** *** ******** security. ******* ** ** ** ******, it ** * ***** ***** ** start ********* ****.
Integration ******** ******** ****
***** ** ** **** ***** ** 'an' ***. ******** **** *****. ** larger *******, ******** ** **** *****. Generally, ***** ** ** *** *** each ******** ** * ******. **** to ***** **** *****, *** *** live ***** ***. **** ** ****** the ****, *** *** **** ****** API. **** ** ******** *** ***** rate *** *********, *** *** ********* frame **** ***, ***.
Not *** ********* **** ** ***
*** *** ********* **** ** *** available. *** *** **** * **** of *** ****** ********** ****** **** another ***********. **** *********** *** **** 'an ***' *** *** * ******** API *** ******* ****** ******. ** you *** ******* ******* **** ******* today **** ******** ** *********, ** is ****** **** ****** ** ***** functions *** *** ********** *** ** API.
**** ******* ********** **** *********** ******* and *****. * ******'* *** ***** lack ******* ******** ************* ********* (**** setting ***** ***** ********, *****, ***/*****/** status, ***.). **** ** *** ********* the *** *******, *** *** **** significant ***********. ***** **** ******** *** want ** ** ********** ** ****** that ** *** ** ****.
Having ** *** **** *** ****** *************
** *** **** ** ********* * leading *** *** ****** ******* ******, both *** **** **** *** ***** is ** ********* **** ***** *** products **** **** ********. **** ********* having **** ** * ***-********* *** integration *** ** ** *** **********.
********* *** ***** ** **** ** difficult ** ********* **** ***********. **** to ********* *********'* ******** *** ****** Genetec ******** ******? **** **** **** APIs *** ***** ** ****************** **** *** ****** ******** ** allow ****, ** **** ******* *** can ****** ***** ****. *** ****, see *** **** *** ********** ** "*********** ********* **** ***** *********."
***** **** *** ********* **** *** web ******** ** ****** * *** fee *** ***, **** ******** ************* often ****** ********* ** ******* ** even ****** ******. **** ** ********** likely ** ** ** * ***** video, ****** ** ***** ******.
**** ** *** **** ********** ** use ******* *******'* ***, ** ** not ********** ** ****. ****** *** web ********, **** ****** ** ******, only * ***** ****** ** ********* use ***** ****, ***** ***** **** could ** ******** ** **** ************ issues. **** ***** ** ** *** next *****.
Integration ***** ****
******* ***** ***** * *** ***** for ***********. **** *** ****** *** often ******** *** ********* ******* **** to ** ****** *** ***** *** take ************* ******.
******, ****** **** *** *** ********, you ****** *** *** *** *** off *** ********. ** ***** ******** a ****** *********** *** ****** ** the *********** *********** *******. ****, **** integrating **** * ******** ****** ***, you ****** ****** ****** ** ****************** ***** ********. *** **** ****** who ****** *** ******* *** ********* difficulties *** ****** *** ******** ************ themselves.
** ****, ** ******* ** *** time *** *** ****** ****** *** commit *** **** ********. **** ** the **** ** **** **** ** often ******* *** ********** ***** *** dig **** *** ********* ******* ***** how **** ****** ********** ***** ****. Generally, ***** ******** *** ********** **********, but *** **** *** **** *** vary.
API ******* *** ***** ***********
**** **** * *******, **** ****, APIs ******. *** ********** ** **** APIs, ***** ****** *** ***** **** system. ******* *** ****** ******* *********** bugs, ********* ***********, ****** ** *** functionalities.
*******, ***** ******* ****** ** ***** APIs. ***'* *** **** ****** ***** with "****** *" ******* *.*. *** let's *** "****** *" ***** *** with *.* *** **** ******* "****** the ***". ** ***** *****, *** new ******* ** *** ******** ********** with *** *** *******. **** ****** could ******** **** ******* **** "****** B" ** *** ******* ****** * to ******* *.*. *** ****** ** your ******** ******* ****** ** ****** displays ***** ** ****** ** ******** the ****** **** **** *** *** upgrade.
**** ******* ********** **** *******. **** you ******* * ****** *** ** does *** ****, ***** ******* **** say, "** *** **** *** *** firmware" **** ** ***** *** ************* have **** ********** *** *****. **** is ******* ******* ******* **** **** to *** *** **** '*****' *** existing **********.
Adding ********* ** **** ****
****** *** *** * **** ***** customer, *** *** ***** **** ******** the *** **** ** ******** *** it **** **. *****, *** **** you ****, **** ***** *** ****. However, ** *** **** **** ****** for **** ******** *** ****, **** can ** **** ** **********. **** sure ******* ** **** ********* **** knows ************ **** *** *** *** and ****** ** ** *** *** anticipate *** ********* ******** ** *****. If * ****** ***** ** ** made, *** ****** **** ******* **** a *** ** **** *** ******* because *** ****** **** ****** **** they ** *** ***** *** ***** of ***** ******** ************* ***** **** API. ****, ** **** ******* **** you ****** ***** ****, ** **** be ********** *** ******** ****** *** are ******** * ******* **** ** the ***** ** * ********* ****** with ****.
Examples ** ****
*** **** ****-***** *** ****-**** ************ API ** ***** ************ ** ****'* VAPIX. *** ******* ******* ********* **** **+ ********* ************ ******** ********* ****** ****. *** instance, ** ******* *** *** ********* what ********** *** ****** *** **** to ***, ****, **** *** ****.
** ***** ******* ** **** ** camera *** ******* ******** ** ********* operations *** ************** ** ******** ***************.
** *** ***, ***** *** ********* thousands ** ********* **** *********. *** this********* ** **,***+ ****. * *** ******** ************** ****,***** ****,******* ****, ***., ***.
APIs ** ****
*****, *** ***** *** *** *** are **** ** *********** **** ********** software ***********.
*** **** **** **** ****** ** ****.
*** ******** *** ************ *******, *** typically **** *** **** ** *** along **** *** *** ** **** you ********** *** ** *** **. Plus, ****** *** **** **** *** fairly *********** *** **** ** **** from ********* *********/**********, ******** ******* ***** require (** ** ***** *****) ***** a ******** ********* (***** .*** ** JAVA) *** ******* ***** ** **** it ****** ** *** ***** **********.
APIs *** *********
*** *** ******** ** *** ** APIs **** **** *********** ****, ********* and ********** ** ******** *********. **** one ** ********* (** ***** ********) different **** ****** **** ** **** are ***** *** **** ****** (********** a **** ***** ****, ******* ** alert, ***.). ******* ** ****, ** is **** ****-********* ** ********* **** multiple ******* ** *** **** ***** to ** **** **** *** **** again *** **** *** ******, ***, recorder, ***.
**** '*********' *** ********* ** ************, like*****, ***** *** **** **** * broad *****-******* ** ************* *** ***. If **** *********** *** ** *** own '********', ** ******** **** ***** is ***** ** ** * ********* language. ** **** ************ ****** **** language (***), **** **** *** *** communicate ******* ****** ** ***** ***** unique ******** ** *** *****. ********* are ***** ****, **** *** ****, hopefully, *** ******* **** *** ** 'standardize' *** ******* ***********. ****, *** our***** ********.
[**** *** ********** ******* ** **** and ********/******* ** ****.]
It would be somewhat helpful to have a quantifiable ranking of what manufacturers will make availalbe in their API/SDK and if access is restricted.
We purchased 100 cameras from one manufacturer who claimed there was an API, then they decilined to release the API to anyone.
Which companies have none/good/great API and VMS support?
Michael, it's very rare to have an IP camera manufacturer 'decline to release the API to anyone.' The only exception would be for those who manufacturer cameras and enterprise VMSes. That said, I don't understand why you would ever buy IP cameras from those companies unless you wanted a 'full package solution.'
We could do some research into support but, like I said, camera companies are typically pretty open, as they want more partners.
Restricted API's bother the crap out of me. All things being equal, I lean towards companies that offer open or low-barrier API's (even though those options are woefully lacking). I don't understand the tendency to restrict access. What is the rational?
They figure they can sell more by forcing you to use their own complimentary products rather than a rival's.
Why has Twitter and Instragram been in an API restriction battle over the last year? Same thing :)
Very good/cool breakdown of a very misunderstood part of our industry.
I can say with considerable expierence in this area that dev in our industry can be a nightmare and is always very expensive, someone put it to me once that its not SDK its $DK!
The biggest issue is the lowest common denominator, say you have three video systems that you want to integrate into another thrid party VMS or PSIM every feature available to the front end has to be available on every connected system so you end up not using lots of features on some system because of weakness/lack of API functions in others.
The backwards compatability is the next biggest issue, you can end up stuck on a version because you know if its upgraded it will break the thrid party connectivity. My advice would be go in with your eyes open, and generally software companies like Genetec, Milestone, Onssi etc will have better and more accessable SDK packages than combined soft & hardware vendors like say Avigilon, Honeywell, Tyco etc as their core offering is a combined solution versus just software which the more open guys base their whole existance on.
I find that about 70% of the time when an end user thinks they need dev it turns out they dont, somtimes ripping out kit/changing software can be cheaper and give you a better and more future prof solution, of course sometimes dev is required and when carried out correctly with good underlaying products can yield very impressive results but it always costs, if not in dev hours and specification then in integrator hours and I guareente nothing ever works properly first time, by version 3 or 4 and sometimes 100's of hours later you have something useable.
Phil, great feedback!
"Its not SDK its $DK!" - Classic!
Good point about lowest common denominator. People are sometimes surprised why PSIM video management capabilities are so rudimentary but that is certainly a key barrier.
Interesting point about ripping out old systems. For sure, if you only have a few old DVRs, it is better to rip and replace, unless the integration is bulletproof and available off the shelf. However, if any custom work needs to be done, for sure, it's better to just upgrade. The trickier issue is what happens when you have dozens or hundreds of old units. To replace those could cost hundreds of thousands or millions of dollars/pounds/euros.
I immediately stop listening when someone even mentions API or SDK. If something does not do what I need right now, I have zero faith that "someone somewhere" will write the particular functionality I am looking for. I am also not going to pay for it to be written when there are other products that are out there already that do what I need.
The only thing that turns me off more than the whole API and SDK pitch is when sales folks say something like, "Everyone includes our cameras in their software and they always write them in."
Ross, good feedback and good advice for other end users.
The only caveat I would add is that sometimes vendors know they have you trapped. For instance, if the vendor is an incumbent at your site, he knows how much of their product you already have and can reasonably calculate that you don't have any other realistic option. It's too expensive and complex to switch so he can force you to either pay up or go without any integration.
Funny you should mention that John because that is exactly the boat we are in now with our #1 in the world integrator with the fancy old/new name. They have had us over a barrel for years and the only thing we could control was the video option. Now that we have moved away from them with video it is on to access control and then, eventually, BA/FA…
Great atricle it very useful
Got it. But I am still looking forward to hearing the class. Sounds like anyone can claim almost anything to sell you a camera. Even though a lot of really amazing stuff is out there it still seems like buyer beware. It sounds like...Sure our stuff will work with yours, as far as you know. When in reality it may be way more trouble than you expect.
Great breakdown of this often misunderstood topic. I find a lot of people not only do not understand API, but often think SDK is the same thing. Whenever I am working with another manufacturer on an integration of products, hearing them describe API or SDK tells me whether I am actually dealing with the technical expert I need to do the work. The scary part is when the most technical person on their team does not know either.
Any tutorials on how to actually get started using these APIs?
I have an EDI installed on my pc... just need some basic direction...
For example... what language are these in? Some practical examples etc...
Thanks
Kenny try, getting into API programming for SPLUNK. There are some ACAM and VMS integrations you might find interesting.
There is much support in the SPLUNK environment for tying business intelligence together in the security world. You will find a lot more robust software hooks to simulate with.
Good Luck.
There is much support in the SPLUNK environment for tying business intelligence together in the security world
What security / surveillance products / APIs are supported by SPLUNK?
RE ... "...how to actually get started using these APIs..."
Do you have any programming experience? if not you need to get some.
Next question would be , what programming languages the APIs support.
You would also need experience in that language. However if you have experience in one language than it may be easier to learn another programming language.
A definition of SDK from elsewhere on internet is
A software development kit (SDK) is a collection of software development tools in one installable package. They ease creation of applications by having compiler, debugger and perhaps a software framework. They are normally specific to a hardware platform and operating system combination.
You need to understand what a compiler, debugger and perhaps a software framework. and how you would use them. This will give you the knowledge to use the provided tools for the camera SDK.
As you can see the list is getting long and is why developers are higher paid .... An experienced developer could/should probably install the SDK and test setup with some same programs ( hopefully provided ) by hardware manufacturer. How quickly the developer could start programming is influence by the quality of the supplied SDK and API, example programs and the support provided.
Good article on API.
This tutorial helped me connect dots and understand further. Thank you much for a great job of presenting the content in a clear fashion.
