BIM 360 publisher guidelines

When you register as a publisher, you'll see the complete requirements in the Publisher Agreement. This guide summarizes the key points — the agreement takes precedence if anything differs.

Compatibility

Your product must be relevant to (and usable with) BIM 360 Team or BIM 360 Docs.

User privileges

The default user privilege for the Store apps is Windows 7/8.1/10/11 Admin User. The installer should have elevated user privileges.

Product stability

Your product should be stable and not behave or alter the behavior of BIM 360 in a way that we deem unsuitable, for example, blocking standard functionality, blocking the functionality of another plug-in, causing data loss, etc.

HTML help page

If your app integrates with BIM 360 Docs, include a page that displays your APS Client ID and app name so users can add it as an integration. Also include step-by-step setup guidance — see the tutorials section for examples.

Ready to run

Your app must work immediately after installation (desktop) or activation (web).

Additional requirements:

• Use only publicly documented, production APS APIs.
• Use only approved OAuth workflows (2-legged or 3-legged).
• Never expose BIM 360 data publicly — no shareable links or public storage.

User experience guidelines for your compatible app

• Use of Autodesk sign in: we strongly recommend that, if your app requires 3-legged OAuth authentication, the app presents the Autodesk logo followed by the "Sign in" wording.

• Use the BIM 360 platform thumbnail. Do not crop or otherwise modify this asset. For display of icons below 120px in width, use the small versions.

Questions? Email appsubmissions@autodesk.com for support.

For more resources, visit the API documentation and the Developer Community Blog.