Kintone is a platform for creating enterprise workflows for data-driven results. The platform exposes REST APIs for its entities for use by external applications. These APIs support the retrieval, update, and deletion of app records. Developers accessing the APIs need to handle the API calls and manually map application contracts with Kintone entities and all coding for CRUD operations.
.NET developers extensively use ADO. NET and Entity Framework for data access. They feel at home when performing data operations using these technologies on any data source. To enable developers to use their existing skills on these internet data sources, ComponentOnehas introduced a data connector that allows data access to Kintone based on these .NET technologies.
Data Connector Features
The library supports .NET Standard so that it can be used in .NET Framework 4.7.2 above or any .NET Core application. The data connector has a host of features that make CRUD operations easy to perform in any .NET application:
- ADO. NET
- SQL
- Open Auth
- Entity Framework Core
- LINQ
- Intelligent Caching
- Scaffolding
Getting Started with the Kintone Data Connector
Let’s walk through an application that can directly talk to the Kintone database and perform all CRUD functionality using Entity Framework Core.
Authentication Prerequisites for Kintone
Each REST API call to Kintone needs an authentication header. Kintone provides two types of authentication mechanisms:
-
Password: Password authentication allows the use of REST APIs with user-level permission, meaning that the authenticated user will need to have permission to control the app or space for the API to succeed.
-
API Token: Alternatively, each app in Kintone can create API tokens that will work specifically with that app. To know more about how to generate API tokens, please refer to Kintone documentation.
Once we have the relevant authentication details in hand, we can move forward to use them in external applications.
#.net #desktop
