Skip to main content

Hello community,

I’m encountering a couple of issues related to permissions with the Miro API and would appreciate any insights.

1. When running the following request:


   GET https://api.miro.com/v2/orgs/{org_id}/boards/export/jobs/{job_id}/results

I receive this response:


   {
     "status": 403,
     "code": "insufficientPermissions",
     "message": "Required scopes: boards:export",
     "type": "error"
   }


I’ve added the `boards:export` scope manually in my app manifest, yet this error persists. Additionally, I couldn’t find any mention of this scope in the documentation.

Is this scope deprecated, or could there be another issue?

2. I’m facing a similar problem with the following request:


   GET https://api.miro.com/v2/orgs/{org_id}/content-logs/items


   which returns:

   {
     "status": 403,
     "code": "insufficientPermissions",
     "message": "Required scopes: contentlogs:export",
     "type": "error"
   }

Despite adding the `contentlogs:export` scope in the app manifest, I still receive this error. This scope is also not mentioned in the documentation.

Could this scope also be deprecated, or might there be another configuration I’m overlooking?

Thanks for any guidance on resolving these issues!

 

Vas

Hi @vkoko 

I’ve just verified the first one and was able to get it to work. Here is my manifest:
 

appName: test exports
sdkVersion: SDK_V2
sdkUri: http://localhost:3000
boardPicker:
  allowedDomains: i]
redirectUris: r]
redirectUriForSdk: ''
scopes:
  - boards:read
  - boards:write
  - contentlogs:export
  - boards:export
icons:
  colored: ''
  outline: ''


and then the API request itself:
 

curl --request POST \
     --url 'https://api.miro.com/v2/orgs/<orgID>/boards/export/jobs?request_id=<add-UUID-here>' \
     --header 'accept: application/json' \
     --header 'authorization: Bearer <add-token-installed-on-enterprise-team>' \
     --header 'content-type: application/json' \
     --data '
{
  "boardIds": I
    "<addboardID>"
  ]
}
'


Just need to fill out the orgID, UUID that you generate yourself, and then a token when you install your app on an enterprise team, and then the boardIDs of the boards you wish to export. I did get the same error as you at first (I may have installed the app before adding the scopes), but I installed the app again, got a new access token and all worked fine. 

Please let me know if this solves your issue.

I was able to get the content exports working as well, with the same access token + same app manifest as in the message above. Please let me know if you got it working now @vkoko. 

@Horea Porutiu Okay, i will try and i will let you know!

 

Thnaks!

Hi @vkoko. I’ve been testing this further, and actually, the content logs API is part of our eDiscovery APIs. These are very new and in beta, and actually you would need to talk to your CSM to enable these. You can read more about these particular APIs and how to use them here.

Sorry about the confusion. 

Reply


Terms & Conditions