API / SDK Tutorial

By: John Honovich, Published on Dec 18, 2016

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.

The goal of APIs in physical security is to allow different systems to work together. Examples include:

  • *********** **** ** ******* or ********* **** **** VMS
  • *********** **** ***/*** **** your ****** ******* ******
  • *********** **** ***** ****** with * ******* ********** system
  • ******** * **** ****** that ********** **** *** your ******** *******

*** ***** **** **** discussed ** ***-***** ********** where * ******** ** integrator **** * ******: "Does **** ****** **** with '*'?" ***** * could ** *** ****** of ******** ******* ** any ****** ** *************.

*** ******* ****** ** the ***** ****** **:

"****, ** **** ** API."

**** ** *** ** the ******** *** ********** statement ** *** ******** security. ******* ** ** so ******, ** ** a ***** ***** ** start ********* ****.

Lesson #*: ** **** ***** ** '**' ***

***** ** ** **** thing ** '**' ***. Numerous **** *****. ** larger *******, ******** ** APIs *****. *********, ***** is ** *** *** each ******** ** * system. **** ** ***** live *****, *** *** live ***** ***. **** to ****** *** ****, use *** **** ****** API. **** ** ******** the ***** **** *** recording, *** *** ********* frame **** ***, ***.

Lesson #*: *** *** ********* **** ** ***

****'* *** ***** *****. Not *** ********* **** an *** *********. *** you **** * **** of *** ****** ********** alerts **** ******* ***********. This *********** *** **** 'an ***' *** *** a ******** *** *** sending ****** ******. ** you *** ******* ******* most ******* ***** **** hundreds ** *********, ** is ****** **** ****** of ***** ********* *** not ********** *** ** API.

**** ******* ********** **** integrating ******* *** *****. A ******'* *** ***** lack ******* ******** ************* functions (**** ******* *** shutter *****, **** *******, ABF, ***/*****, ***.). **** if *** ********* *** two *******, *** *** have ******* ***********. **** sure ** ***** **** function *** **** ********** to ****** **** ** can ** ****.

Lesson #*: ****** ** *** **** *** **** ** **** **** **** **** ******

***'* *** *** **** to ********* * ******* VMS *** ****** ******* system. **** *** **** APIs *** ***** ** no ********* **** ***** two ******** **** **** together. **** ********* ****** APIs ** * ***-********* for *********** *** ** is *** **********.

********* *** ***** ** make ** ********* ** integrate **** ***********. **** to ********* *********'* ******** VMS ****** ******* ******** Center? **** **** **** APIs *** ***** ** this************** **** *** ****** unlikely ** ***** ****, as **** ******* *** can ****** ***** ****. For ****, *** *** post *** ********** ** "*********** ********* **** ***** Recorders."

***** **** *** ********* free *** *** ******** or ****** * *** fee *** ***, **** security ************* ***** ****** thousands ** ******* ** even ****** ******. **** is ********** ****** ** it ** * ***** video, ****** ** ***** system.

**** ** *** **** permission ** *** ******* company's ***, ** ** not ********** ** ****. Unlike *** *** ********, like ****** ** ******, only * ***** ****** of ********* *** ***** APIs, ***** ***** **** could ** ******** ** have ************ ******. **** leads ** ** *** next *****.

Lesson #*: ***** *** *********** ***** ****

******* ***** ***** * few ***** *** ***********. This *** ****** *** often ******** *** ********* details **** ** ** worked *** **** *** take ************* ******.

******, ****** **** *** web ********, *** ****** can *** *** *** off *** ********. ** often ******** * ****** application *** ****** ** the *********** *********** *******. Plus, **** *********** **** a ******** ****** ***, you ****** ****** ****** or ****************** ***** ********. *** only ****** *** ****** can ******* *** ********* difficulties *** ****** *** security ************ **********.

** ****, ** ******* of *** **** *** dollar ****** *** ****** for **** ********. **** is *** **** ** risk **** ** ***** unknown *** ********** ***** you *** **** *** technical ******* ***** *** each ****** ********** ***** APIs. *********, ***** ******** are ********** **********, *** the **** *** **** can ****.

Lesson #*: *** ******* *** ***** ***

**** **** * *******, over ****, **** ******. The ********** ** **** APIs, ***** ****** *** break **** ******. ******* for ****** ******* *********** bugs, ********* ***********, ****** in *** ***************.

*******, ***** ******* ****** on ***** ****. ***'* say **** ****** ***** with "****** *" ******* 3.1. *** ***'* *** "Vendor *" ***** *** with *.* *** **** version "****** *** ***". In ***** *****, *** new ******* ** *** backwards ********** **** *** old *******. **** ****** could ******** **** ******* with "****** *" ** you ******* ****** * to ******* *.*. *** result ** **** ******** command ****** ** ****** displays ***** ** ****** or ******** *** ****** that **** *** *** upgrade.

**** ******* ********** **** cameras. **** *** ******* a ****** *** ** does *** ****, ***** vendors **** ***, "** you **** *** *** firmware" **** ** ***** two ************* **** **** integrated *** *****. **** is ******* ******* ******* were **** ** *** API **** '*****' *** existing **********.

Lesson #*: *** *** ***** **** **** *** *** ****

****** *** *** * very ***** ********, *** are ***** **** ******** the *** **** ** whatever *** ** **** it. *****, *** **** you ****, **** ***** out ****. *******, ** you **** **** ****** for **** ******** *** case, **** *** ** hard ** **********. **** sure ******* ** **** technical **** ***** ************ what *** *** *** and ****** ** ** you *** ********** *** potential ******** ** *****. If * ****** ***** to ** ****, *** change **** ******* **** a *** ** **** and ******* ******* *** vendor **** ****** **** they ** *** ***** the ***** ** ***** security ************* ***** **** API. ****, ** **** believe **** *** ****** needs ****, ** **** be ********** *** ******** unless *** *** ******** a ******* **** ** the ***** ** * briefcase ****** **** ****.

Examples ** ****

*** **** **** ***** and **** **** *** in ***** ************ ** Axis's *****. *** ******* version ********* **** **+ ********* sections**** ******** ********* ****** each. *** ********, ****'* their** **** *** *** document. ** ** **** 24, ******* *.*.* ** see *** ** ******* the *** ********* **** parameters *** ****** *** need ** ***, ****, zoom *** ****.

** ***** ******* ** Axis ** ****** *** require ******** ** ********* operations *** ************** ** numerous ***************.

** *** ***, ***** are ********* ********* ** different **** *********. *** this********* ** **,***+ ****. * *** ******** include******* ****,***** ****,******* ****, ***., ***.

APIs ** ****

*****, *** ***** *** and *** *** **** in *********** **** ********** software ***********.

  • *** - *********** *********** Interface - *** ****** code ***** *************, ********* you **** **** ** integrate *** *******
  • *** - ******** *********** Kit - *** ************* and *********** ***** **** support *** **** *** parties ** *** *** API

*** **** **** **** on**** ** ****.

*** ******** *** ************ systems, *** ********* **** and **** ** *** along **** *** *** to **** *** ********** how ** *** **. Plus, ****** *** **** that *** ****** ***** weight *** **** ** call **** ********* *********/**********, security ******* ***** ******* (or ** ***** *****) using * ******** ********* (often .*** ** ****) and ******* ***** ** make ** ****** ** use ***** **********.

APIs *** *********

*** *** ******** ** far ** **** **** been *********** ****, ********* and ********** ** ******** companies. **** *** ** typically (** ***** ********) different **** ****** **** if **** *** ***** the **** ****** (********** a **** ***** ****, getting ** *****, ***.). Because ** ****, ** is **** **** ********* to ********* **** ******** systems ** *** **** needs ** ** **** over *** **** ***** for **** *** ******, VMS, ********, ***.

**** '*********' *** ********* in ************, *********, ***** *** **** that * ***** ***** section ** ************* *** use. ** **** *********** API ** *** *** 'language', ** ******** **** ONVIF ** ***** ** be * ********* ********. If **** ************ ****** that ******** (***), **** they *** *** *********** without ****** ** ***** every ****** ******** ** the *****. ********* *** still ****, **** *** that, *********, *** ******* will *** ** '***********' how ******* ***********. ****, see ******** ********.

[**** *** ********** ******* in **** *** ******** / ******* ** ****.]

Comments (18)

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.

You MUST be talking about $iemens and their $INVR :-)

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?

Good article on API.

Login to read this IPVM report.
Why do I need to log in?
IPVM conducts unique testing and research funded by member's payments enabling us to offer the most independent, accurate and in-depth information.

Related Reports

History of Video Surveillance on Jul 19, 2019
The video surveillance market has changed significantly since 2000, going from VCRs to emerging into an AI cloud era.  The goal of this history...
Anyvision Aims For 2022 Revenue of $1 Billion on Jul 17, 2019
Only 3 video surveillance manufacturers do a billion dollars or more in annual revenue - Hikvision, Dahua, and Axis. Now, Anyvision plans to join...
ZeroEyes Gun Detection Startup on Jul 16, 2019
A gun detection video analytics startup, ZeroEyes, is being led by a group of 6 former Navy SEALs, aiming to "save lives" by using AI to assist...
Vivotek Trend Micro Cyber Security Camera App Tested on Jul 15, 2019
Vivotek and Trend Micro are claiming five million blocked attacks on IP cameras, with their jointly developed app for Vivotek cameras. This new...
Axis ARTPEC-7 P1375-E Camera Tested on Jul 12, 2019
Axis claims the new P1375-E box camera with ARTPEC-7 chip delivers "clear, sharp images in any lighting condition." But how well does it do? We...
Last Chance - Camera Course Summer 2019 on Jul 11, 2019
Last day to register is Thursday, July 11, 2019. This is the only independent surveillance camera course, based on in-depth product and technology...
Lens Focal Length Tutorial on Jul 10, 2019
3mm, 6mm, 2.8 - 9mm, 5 - 50mm, etc. Camera specifications often list lens lengths but what do they mean? These metrics are important in...
Poor OSDP Usage Statistics 2019 on Jul 09, 2019
OSDP certainly offers advantages over decades-old Wiegand (see our OSDP Access Control Guide) but new IPVM statistics show that usage of OSDP, even...
Avigilon President Henderson Is Out on Jul 09, 2019
Avigilon's President and COO James Henderson is out, abruptly, after a remarkable ascension over the past 8 years, Motorola VP Jack Molloy has...
Bosch Integrating Sony Video Security Sales And Marketing Team on Jul 03, 2019
What is the future of Sony in video surveillance? In 2016, Bosch and Sony announced an atypical 'partnership'. Now, Bosch tells IPVM that they...

Most Recent Industry Reports

History of Video Surveillance on Jul 19, 2019
The video surveillance market has changed significantly since 2000, going from VCRs to emerging into an AI cloud era.  The goal of this history...
Mobile Access Usage Statistics 2019 on Jul 18, 2019
The ability to use mobile phones as access credentials is one of the biggest trends in a market that historically has been slow in adopting new...
New GDPR Guidelines for Video Surveillance Examined on Jul 18, 2019
The highest-level EU data protection authority has issued a new series of provisional video surveillance guidelines. While GDPR has been in...
Wyze AI Analytics Tested - Beats Axis and Hikvision on Jul 17, 2019
$20 camera disruptor Wyze has released free person detection deep learning analytics to all of their users, claiming users will "Only get notified...
Anyvision Aims For 2022 Revenue of $1 Billion on Jul 17, 2019
Only 3 video surveillance manufacturers do a billion dollars or more in annual revenue - Hikvision, Dahua, and Axis. Now, Anyvision plans to join...
HD Analog vs IP Guide on Jul 16, 2019
For years, HD resolution and single cable signal/power were IP camera advantages, with analog cameras limited to much lower resolution and...
How To Troubleshoot Wiegand Reader Problems - Inverted Wiring on Jul 16, 2019
Wiegand is the dominant method of connecting access readers, but problems can arise for installers. In fact, one of the most difficult reader...
ZeroEyes Gun Detection Startup on Jul 16, 2019
A gun detection video analytics startup, ZeroEyes, is being led by a group of 6 former Navy SEALs, aiming to "save lives" by using AI to assist...
Motorola Acquires Watchguard, Adds to Vigilant And Avigilon on Jul 15, 2019
2 years ago, Motorola had no position nor relevancy to video surveillance. Now, they own major video surveillance, LPR and body camera providers...
Hikvision Global News Reports Directory on Jul 15, 2019
Hikvision has received the most global news reporting of any video surveillance company, ever, ranging from the WSJ, the Financial Times, Reuters,...

The world's leading video surveillance information source, IPVM provides the best reporting, testing and training for 10,000+ members globally. Dedicated to independent and objective information, we uniquely refuse any and all advertisements, sponsorship and consulting from manufacturers.

About | FAQ | Contact