关于Forge .NET API中manifest与webhooks功能上线时间的问询

Hey Øyvind,

Awesome question—let’s dive into this for you:

Where We Stand Right Now #

The official Forge .NET SDK doesn’t have native, purpose-built methods for manifest or webhooks functionality right now. It’s mostly a wrapper around Forge’s core REST endpoints, so if you need to use these features today, you’ll still have to make direct REST calls (using something like HttpClient in your .NET code) to interact with Forge’s manifest and webhooks APIs.

What’s Coming Down the Line? #

Autodesk doesn’t publish a fixed, public roadmap for SDK updates, but the Forge team does prioritize features based on community feedback. Since manifest and webhooks are super requested (and would save everyone tons of manual REST boilerplate like you pointed out), there’s a solid chance they’ll add native support in a future release.

A Quick Workaround for Now #

If you want to skip writing raw REST calls over and over, you can wrap the manifest/webhooks REST endpoints in your own reusable .NET helper classes. For example, a ForgeWebhooksHelper or ForgeManifestClient that handles auth, request formatting, and response parsing—this way you only write that REST logic once, and can call it cleanly wherever you need it in your code.

内容的提问来源于stack exchange，提问作者Øyvind Knappskog Olsen