It seems that API v1 stopped working already - isn’t it too soon?

Sending GET request to https://api.miro.com/v1/boards/uXjVO0K1rF0=/widgets

received status code 404 

Response body:  {

    "message": "no Route matched with those values"

}

<Response s404]>

Hi @truemetal ! 

V1 endpoints should definitely still work. Can you see if this is working as expected for you? https://developers.miro.com/v1.0/reference/list-all-widgets-1

We have our official deprecation policy listed here: https://developers.miro.com/docs/miro-developer-platform-deprecation-policy

It works now - seems it was a temporary glitch, thanks!

Hello @Addison Schultz ,

is this post to be understood as the deprecation announcement for the V1?

Our team’s API requests are intermittently hitting the following error starting today:

URL: https://api.miro.com/v1/boards/BOARD_ID/widgets/

ERROR: The request could not be satisfied

403 ERROR
The request could not be satisfied.
Bad request.

We can't connect to the server for this app or website at this time. There might be too much traffic or a configuration error. Try again later, or contact the app or website owner.

If you provide content to customers through CloudFront, you can find steps to troubleshoot and help prevent this error by reviewing the CloudFront documentation.

Generated by cloudfront (CloudFront)
Request ID: 

Update: 

My problem above came from passing a “json” keyword parameter with an empty {} along with my GET requests. This wasn’t an issue before today, but removing that solved it, in case anyone else has something similar.

Hi @oliverir! With the launch of the new platform, we do have an official deprecation policy regarding V1. 

You can find all the details here: https://developers.miro.com/docs/miro-developer-platform-deprecation-policy

Hi @MiroMonkey ,

Thanks for the report, and for debugging this issue a bit! I’m happy you got this fixed—I’ll pass this over to the team

Hi @Addison Schultz !

Thank you, I looked at the page. It says there

>...] Miro will provide a minimum of 6 months' notice before retiring a service. This 6 month period will begin with a “deprecation announcement” that communicates our intention to retire a service on a given future date.

What I am wondering though is if this transitory deprecation period has already been entered! My team and I definitely need to adjust to the changes but aren’t quite sure yet how quickly we need to act. Can we expect an “official” deprecation announcement or is this it?

Hey @oliverir,

You should have received our official deprecation notice via email! We sent it a few weeks ago. Can you check to see if you have an email with the subject that contains “Miro Developer Platform News”?

Hey @Addison Schultz,

sadly I have only recently activated the notifications for my account, so I doubt I would have received such an email. But your reply answers my question regardless, thank you for your help, sir!

We have just finished building a V1 app and I was creating another app registration for it. When we try to launch the app, it fails to load and I get errors like, “This tool is unavailable on this board” and in the console, “Uncaught Error: HELLO_APP_FROM_IFRAME:: PluginController not found for origin...”. Does anyone have any idea why this might happen?

@Jim Garlick, Can you explain a bit more by what you mean with creating another app registration? Are you creating a new Miro app?

Yes. We needed to re-create one of our V1 apps because we changed from non-expiring Access Tokens to using Refresh Tokens. The code is identical to before, but the app isn’t launching in the Board.

Considering APP cards API, it seams completely broken!

1. https://developers.miro.com/reference/update-app-card-item - I use the “try it out” method with creating app card. It creates the card, that literally doesn’t expand when I press the button.

2. Updating Card method doesn’t work considering “style” option:
   My query

   

   result:

so the color hasn’t changed…

API (even if there is “stable” mark leaves much to be desired) =(

Considering APP cards API, it seams completely broken!

 

1. https://developers.miro.com/reference/update-app-card-item - I use the “try it out” method with creating app card. It creates the card, that literally doesn’t expand when I press the button.

2. Updating Card method doesn’t work considering “style” option:
   My query

   

   result:

so the color hasn’t changed…

API (even if there is “stable” mark leaves much to be desired) =(

@Addison Schultz

Nice stable API

@Addison Schultz - Some feedback on 2.0: It would seem that 2.0 does not support reading mind map nodes?

For example, @Yash built an app called Cardsy that converts Sticky Notes, Shapes, or Text into Cards. He later updated his app to include converting Mind Map nodes into Cards. This was HUGE as there is no way to do this inside of Miro - one would have to copy the node text and put it in a Card or export to CSV, copy-paste to Miro to create a Sticky Note, and then convert the Sticky to a Card.

Yash recently updated to SDK 2.0 and it now appears that Mind Map nodes can not be read using 2.0. Is this correct? Is so, please add this functionality :)

Yash’s Cardsy app → https://cardsy.yashbhalodi.me/

Use case

A team brainstorms using a Mind Map and then wanted to create Cards for assignment in a Kanban.

Here’s how Cardsy worked using SDK 1.0 to create Cards from Mind Map nodes:

@Robert Johnson thanks a lot for sharing this very interesting use-case. I will share it internally with our Product Managers.

Would it be possible for you to vote for this feature and share your use-case (even just the link to this post) on our public roadmap? Thanks a ton!

@Anthony Roux - Idea submitted!

Are any Developers here interested to ideate Proposals together and then being able to deliver on the proposals we are writing together?

I am participating in Blockchain Governance projects and onboarded hundreds of members using Miro Board. There are many features and ideas which could save a lot of our time when integrating tools with Miro Board.

Contact me if you are interested to help out or want to get funded to build tools on Miro Board.

@Tevo Saks I shared your posts on our Discord community Free feel to just us there.

Dear Miro Team

I have created two apps with Miro Web SDK 1.0, which unfortunately no longer work due to the upgrade to Miro Web SDK 2.0.

The reasons are:

1.  clientVisibility is no longer supported
2. LINES as widgets are no longer supported

I ask that either the features are reintroduced, or alternatively a global visibility is introduced as a WIDGET attribute, or at least you have the option to downgrade back to Web SDK 1.0.

Thanks for the understanding.

Hi @Vladimir B.,

Thanks for sharing this feedback, and can definitely appreciate where you’re coming from.

First, regarding lines, this is on our radar and we hope to introduce them for V2 soon. You can track our progress on this here. 

Second, regarding the `clientVisibile` boolean for widgets, we’ve redefined widgets as “items” in V2, and this exact boolean is not currently available. However, it’s a great suggestion and I’m happy to pass this on to our product team.

Thanks!
Will