Dingtalk Open Platform interface documentation and platform interface documentation

Dingtalk Open Platform interface documentation and platform interface documentation

1. Directory

Establish a connection

Actively call to obtain the AccessToken

Callback Mode

Manage multimedia files upload media files obtain media files

Message sending interface description Message Type and data format text message image message voice message video message file message

Office message

The login-free service uses the standard OAUTH2.0 HTTP 302 jump method to get CODE and Exchange CODE for user identity

Get jsapi_ticket.

 

2. Micro-applications are the mobile portal built by dingtalk to connect to enterprise offices,

Through Micro-applications, you can

Business Approval, internal system, generation, collaboration, management, upstream and downstream communication connected to dingtalk, simpler and less efficient

In this way, enterprises can be moved. Combined with dingtalk's basic communication capabilities, enterprise applications can be more active, employees can be more efficient, and mobile costs can be reduced.

This document is suitable for a) enterprise IT department, learn how dingtalk connects to the office of your enterprise. B) software development service provider, learn how to provide customized enterprise office software to your customers through dingtalk,

Increase the value of your service.

 

 

3. Establish a connection

You can use the following three methods to connect dingtalk micro-applications to your enterprise applications:

1. The Enterprise Application Server calls the interface provided by the dingtalk open platform to push messages to the enterprise user's dingtalk account as a dingtalk micro-application. 2. The dingtalk Open Platform pushes the messages or triggered events sent by dingtalk users to the enterprise application server for processing by the enterprise application. The callback mode is called below (not yet open)

3. When a dingtalk user uses the H5 page of a micro-application provided by an enterprise, the page can call the native interface provided by dingtalk and use the terminal capabilities opened by dingtalk. The JSAPI mode is called below. When the enterprise application server calls the dingtalk Open Platform interface, you need to use https protocol, Json data format, UTF8 encoding, access domain name for https://oapi.dingtalk.com, data packets do not need to be encrypted. The AccessToken parameter must be included in each active call to the dingtalk Open Platform interface. The AccessToken parameter is exchanged by the CorpID and Secret. CorpID is the identifier of an enterprise in dingtalk. Each enterprise has a unique CorpID, and Secret is the credential key of each enterprise application. CorpID and Secret can be found in the management background provided by dingtalk for enterprises, which are automatically allocated by dingtalk. Obtaining the AccessToken is the globally unique ticket for enterprises to access the dingtalk Open Platform interface. when calling the interface, the AccessToken must be included.

Dingtalk Shenzhen R & D team denny/2016.01.06