Using Doconut within a Public SDK or API
This page discusses how we define usage and license our software when our products are used in end user software with a public SDK or API.
End User License Agreement
Under our standard End User License Agreement customers using Developer Site are not allowed to expose any kind of public API or other programmatic interface for other developers which uses Doconut products either directly or indirectly.
SDK License
For customers who do require to expose features which use our products as part of their own product’s public Development Library, API, online API or SDK we offer a way to use our products: The use of a SDK license. See the FAQ for details about this license type.
What is considered use within an SDK or API?
We define this applicable if you have a Development Library, API, online API or SDK Usage as any product that exposes Doconut products features or functionality within its own public API. If your product does not have a public API or SDK for other developers to use then this does not apply.
It does not matter the extent to which our features or functionality is exposed; if executing a public API call within your product ‘touches’ any Doconut products as part of doing its job then we consider it as usage which requires a SDK license. It also does not matter how many layers of abstraction an application has; if Doconut features / functionality are being made available to other developers through an API, SDK license can be used.
What are the key licensing differences?
Under our usual Developer license, you are allowed to publish your application in a single domain and any subdomain within it. For Site license you are granted the right to publish in any domain that your own company owns. If the domain is not owned by your company, then you must use an SDK license. However, when your product contains a public API, you are required to use an SDK license. If you have an existing Developer or Site license and your end user software now has a public API, then you will need to migrate to an SDK license.