Does the Forge model.sync webhook have different security/scope rules than others?

Question

We've been using the Forge DM webhooks for some time. But when we attempt to register an adsk.c4r/model.sync webhook, it gives a 401 error. We have all of the "data"-related scopes set in our token.

{
  "id": "22c519a4-0afd-46f5-b80e-3a718fe6b5a1",
  "status": 401,
  "code": "AUTHORIZATION_ERROR",
  "detail": [
    "User authorization was not defined for eso with system id: adsk.c4r and event id: model.sync"
  ]
}

Is there something else that needs to be authorized differently?

Answer 1

My apologies for the delay, we have some backlog in the work queue. After discussing with our engineering team, the C4R related hooks support 2LO access token only currently. Sorry for the bad news.