Last updated:

The SDK and the API are similar but there are some key differences. This article will help you understand some of these differences. In order to see the developers guide for the SDK and API, please click here


The SDK  is a Software Development Kit (SDK) which encompasses much of the code in order to display Appnext ads. The API is an Application Programming Interface (API) which allows your application to interact with Appnext. The SDK calls the API which means that the SDK has all the features of the API. 



  • The time to market is very quick - The developer just has to put the SDK code inside their app and they code go live the same day. Some developers take just 15 minutes to put SDK in their app. 
  • The developer does not need to know how the code works. The SDK takes care of most of the hard work without the developer having to take them into account. 
  • The SDK takes care of when to send impressions according to the IAB guidelines. 
  • The SDK takes considerable efforts to ensure that GDPR and privacy practices with data protection laws and industry's best practices are followed.
  • The SDK will make sure to show the right size of banner or other ad unit.
  • The ecpm of campaigns on the SDK will be higher as there are more campaigns connected to the SDK and the algorithm of the SDK is better. 
  • The developer just needs to pick which ad units to show.



  • The QA for the API is longer as the developer needs to make sure that the impressions are being sent correctly with the correct macros, the clicks are being sent when user clicks, the store is being opened correctly, etc. 
  • All of the responsibility of creating the placement of the ad unit is on the developer. The developer is responsible for how the placement looks and that the ad units are the correct sizes.
  • The developer needs to differentiate between UA and re-engagement campaigns. There is different logic here. If there is a UA campaign, the developer needs to check if the user doesn't have this package already. If this is a re-engagement campaign, the developer needs to check if the user already has this package on his device.
  • The responsibility of GDPR falls on the developer. 


Was this article helpful?
Help us make this section better.