Skip to main content

​
What Is an Organization-Authorized App

An organization-authorized app is an app at the organization level. It is an app format from an early version of DingTalk. To use this type of app, you need to generate a dedicated API credential based on your organization’s unique identifier (Organization ID, that is, CorpId) and security key (Organization Secret, that is, CorpSecret). With the generated API credential, you can access and use development capabilities such as OpenAPI, Webhook, and Stream. Note Only Organization Admins can view and manage organization-authorized calls. Other members cannot perform such operations.

​
What Is an Organization-Authorized Call

Sign in to the DingTalk Developer Console, and click More > Basic Information > Development Information (Legacy). There, you can find and record the Organization ID (CorpId) and Organization Secret (CorpSecret). Using these two values, you can generate a dedicated API credential to access OpenAPI. This process is called an organization-authorized call.
This is a legacy product from the early Open Platform. If needed, we recommend calling OpenAPI through an internal app. For more information, see Obtain the access_token of an internal app.

​
How to Stop an Organization-Authorized Call

When you need to disable the organization-authorized call feature, you cannot delete the Organization Secret (CorpSecret) directly. If you want to stop using the authorized call, a Super Admin with development permissions can do so. Specifically, change the bound IP address to an invalid address to disable the organization-authorized call.

​
Unable to Find an Internal App on the Workbench

Answer: If you cannot find the relevant app on the Workbench, troubleshoot the issue by following these steps:
  1. Confirm that the organization of the current Workbench matches the organization the app belongs to.
  2. Confirm that the app has been published. Ask the Admin to go to the Developer Console > the target app > Version Management and Release to confirm whether the app is in the published state.
  3. Confirm the availability scope of the app. Ask the Admin to go to the Developer Console > the target app > Version Management and Release to confirm whether the user who cannot find the app is within the availability scope.

​
Debugging an Internal App in the Mini Program IDE Prompts “Sorry, You Are Not Within the Availability Scope of This App. Contact the Admin to Modify the Configuration”

Answer: The possible causes of this prompt when debugging an internal app include, but are not limited to, the following:
  1. The person debugging the internal app is not in the developer list. Set the developers in the Developer Console > the target app > User Management.
  2. No version has been uploaded for the internal app. Make sure to upload the app version in the Mini Program IDE, and then release the version in the Developer Console > the target app > Version Management and Release.
  3. The user is not set in the Developer Console > the target app > Version Management and Release > Availability Scope. Note For an internal app mini program, the availability scope is displayed only after you upload a version in the Mini Program IDE and release the version in Version Management and Release.

​
An Internal Micro App or Mini Program Has No App Key or App Secret

Answer: The reasons why a created app does not display the App Key and App Secret may be as follows:
  • When you create an internal app in the Developer Console, as shown in the figure below, you select Development by an entrusted service provider as the development method, which causes the values not to appear in App Management. Note If you do not actually need entrusted development, select In-house development.
  • You are not the app creator and do not have the relevant permissions to view the App Key and App Secret. Contact the Super Admin to add the corresponding App Management permissions on the DingTalk Admin Console > Security and Permissions > Manage permissions page.