Bug Reports

Previously, we used your https://cloud.sensopia.com/dispatchplan.php endpoint to create new projects. This returned a planID e.g. 6735c46f0a1c2. We used this planID to create a mobile deeplink to the project e.g. magicplanstd: //open?plan=6735c46f0a1c2&showInfo=1 . We have been looking at moving to your new https://cloud.magicplan.app/api/v2/projects endpoint instead to create new projects. The response from this endpoint no longer returns a planID field, but instead just an ID field e.g. 09701c6b-7af3-43b2-9498-f9058f3d4172. However, using this returned ID in the mobile deeplink does not work. Clicking a deeplink with this ID gives "Project not found" in the Magicplan app. When you go to the web view of the project created with this new endpoint ( https://cloud.magicplan.app/estimator/projects/09701c6b-7af3-43b2-9498-f9058f3d4172/overview ) and inspect the network requests you can see a GraphQL call to planHierarchyDataGet, which returns a response that has both ID and SensopiaID as e1b281b5-defb-46a8-af87-aec54f43a599. Creating a mobile deeplink using this ID works correctly. So, my question is: when using the new create project endpoint, how can we know what the correct ID of the project is in order to create a mobile deeplink to the newly-created project? Is this new endpoint perhaps returning the wrong ID? Though I note this wrong ID is used in the web URL of the project.

When making a call to the https://cloud.magicplan.app/api/v2/projects endpoint and specifying the latitude and longitude of the address, the request fails with "500: Internal Server Error". I have tried both with the other address fields set and just with the latitude and longitude set. I have also tried the example shown in your Swagger API: https://app.swaggerhub.com/apis-docs/magicplan/magicplanCloudApi . All fail in the same way. Example cURL request: curl --header "key: XXX" --header "customer: YYY" -H "Content-Type: application/json" https://cloud.magicplan.app/api/v2/projects --verbose --data '{"email":" person@example.com ","name":"Test","address":{"street":"Infinite Plan Street","street_number":"1A","city":"Munich","postal_code":"15615","country":"Germany","longitude":-20.5357,"latitude":-99.625}}'

We have recently started testing out the listing functionality and it seems like we can not turn it off once we have defined a listing url by using the endpoint https://cloud.magicplan.app/api/v2/workspace/ [PUT]. We are trying to set the variable listing_url to null but instead we receive an error. We are currently not in need of turning it off, but we want to be able to in-case we feel like this functionality is not longer needed or wanted. But as of now that does not seem possible. The request we send to the endpoint https://cloud.magicplan.app/api/v2/workspace/ [PUT]: { "listing_url": null } What we get back: { "errors": { "errors": "Body does not match schema for content-type \"application/json\" for Request [put /workspace]" } } We would instead expect this to set the listing_url to null and turn off the listing functionality.

In the swagger documentation for the /workgroups/users API ( https://app.swaggerhub.com/apis-docs/magicplan/magicplanCloudApi/1.2#/ ), the response is specified as having a "data" property which is an array of objects. In fact, the "data" property is an object that contains paging information, and a "users" key which is an array. It would be useful to update the documentation to account for this, and include paging/filtering API parameters, since none are mentioned.

I'm trying to integrate our app with the recently added "reassign plan owner" API ("PUT /plans/{id}/owner"). If a plan is assigned to a specific team, calling the API to assign a different user will remove the project's team assignment. There is no documented way to specify a team when using this API. For our use-case this API would be more useful if we could avoid removing the team assignment, or specify explicitly which team the project should be assigned to.