Hi @Falk Köppe ,
Thank you for reaching out, and apologies for the issue you're experiencing.
I could replicate the same behavior, and I asked the REST API engineers for more information about that.
I'll update you as soon as I receive a reply from them.
Best,
marco
Technical writer | Developer Relations | Miro Developer Platform
Hi @Falk Köppe ,
Thank you for your patience. Unfortunately, the REST API reference docs report incorrectly that copy board includes the ability to set the copied board to a project ID.
Copying a board through the REST API does not allow also assigning it to a project; the behavior you experienced and reported is the current normal/expected way of working of the endpoint in question.
To copy a board and to assign it to a project, you can send 2 consecutive REST API requests:
- Copy an existing board with https://developers.miro.com/reference/copy-board
- Update the copied board by assigning it to a project ID with https://developers.miro.com/reference/update-board
Currently, this is the easiest way to copy a board and assign it to a project. I realize that this requires 2 calls instead of one, which is not ideal.
Best,
marco
Technical writer | Developer Relations | Miro Developer Platform
Hello Marco,
thank you for your research and follow-up. I think in our case it is fine to fire the second call in the background, but I agree, that it is not optimal. It would be great, if the REST API team could extend the “Copy Board” endpoint in the future, to handle the given “projectId” directly.
Best,
Falk