This article is for developers with a full understanding of how to work with our API. 

Important note about the API explorer: 
When you follow the link we provide to the API explorer, you'll see a red warning.

The API itself is not deprecated. It's the Google API explorer that is deprecated. All the processes described in our API articles function correctly and safely if you use this Google API explorer. .

In this article:

Automatically generated table of contents

What does the API call do?

You can use the API to remove the Edit in Google buttons that appear next to attached Microsoft files by default. This ensures your users use the Microsoft Office suite rather than the corresponding Google apps (Google Docs, Sheets and Slides) to edit attached files. This affects only attached Microsoft files.

Learn more: Edit attacched Microsoft Office files using the Google Docs editor embedded in AODocs.

A custom configuration flag is available to remove these buttons from the interface for a specific library or a whole AODocs tenant.

Important: 
– To apply the flag at the AODocs tenant level, you must be super administrator. To apply the flag at the library level, you must be library administrator or super administrator. 
– This setting is available through the API only. It isn't available in the administration interface.
– Custom configurations at the library level take precedence over those set at the AODocs tenant level. For example, if you set the flag as true at the AODocs tenant level and false for one library, the Edit in Google buttons will be removed for all libraries in your AODocs tenant except the one in which you set it as false.

Learn more: Use the API to check which custom configuration flags are set on your AODocs tenant or library.

Set the custom configuration at the AODocs tenant level 

1. As an AODocs super administrator, follow one of these links to the AODocs API:

• US instance:

https://apis-explorer.appspot.com/apis-explorer/?base=https://ao-docs.appspot.com/api#s/domain/v1beta1/domain.configuration.set

• EU instance:

https://apis-explorer.appspot.com/apis-explorer/?base=https://aodocs-core-eu-1.ey.r.appspot.com/api#s/domain/v1beta1/domain.configuration.set

Note: Dedicated instances have their own URLs. Learn more: What are AODocs instances?

2. Enter the flag name: disableGoogleEditorForOfficeFiles.

3. Enter your AODocs tenant name. 

4. In the Request body field, enter TRUE.

5. Click Authorize and execute. The response is displayed in the lower part of the screen.

Note: To remove a custom configuration, use the same process, and enter the value FALSE in the Request body field. This is the default value.

Set the custom configuration at the library level

1. As a library administrator, follow one of these links to the AODocs API:

• US instance:

https://apis-explorer.appspot.com/apis-explorer/?base=https://ao-docs.appspot.com/api#p/library/v1beta1/library.configuration.set

• EU instance:

https://apis-explorer.appspot.com/apis-explorer/?base=https://aodocs-core-eu-1.ey.r.appspot.com/api#s/library/v1beta1/library.configuration.set

Note: Dedicated instances have their own URLs. Learn more: What are AODocs instances?

Learn more: What are AODocs instances?

2. Enter the ID of the library in which you want to add custom buttons. Learn how to identify the library ID. 

3. Enter the flag name: disableGoogleEditorForOfficeFiles.

4. In the Request body field, enter TRUE.

5. Click Authorize and execute. The response is displayed in the lower part of the screen.

To remove a custom configuration, use the same process, and enter FALSE. This is the default value. note, no frills.

Which buttons are removed?

If you activate the disableGoogleEditorForOfficeFiles flag, the buttons shown below are no longer available for attached Microsoft files.