
Hi Alex,
There is no such APIs published yet.
Li Xiao

Hi Gavin,
It is a bug. I reported it to Mingle team.
Thank you.
Li Xiao

Hi Alex,
You can create a card using ../cards/create which is action used to create a card in the Mingle now.
You can access it and all other links/actions which you can access by browser after login.
But they all are not part of API, which means they maybe changed without any document or notification for you.
We recommend you build on the published API.
Cheers,
Li Xiao

Hi Rudi,
The param name you specified for filters is wrong, it should be “filters[]”.
And you should not encode all params.
If some param value need to be encoded, you should only encode the param value,
for example:
filters[]=[Type][is][#{urlencode('***&xx')}]

Hi Gavin,
There is no hierarchical view for REST API, cards API can only get a list of cards no matter what’s view it is.
As you said, it should be a bug.
Could you provide more details about it?
What’s params and values you send out for the request?
I just checked on our trunk version, there is no same problem.
It maybe fixed. I would like to try again if you provide more specific details.
Thanks
Li Xiao

Hi Gavin,
The document is missed. We’ll add them ASAP. Thank you.

Hi rnwolf,
The updated_at is a read-only attribute, so you can’t update it and it would be updated automatically every time you updated the card.

There is no API for getting attachments/uploading attachments for card/page now.
And we have no plan on it right now.

Hi, rnwolf
There is no API for updating tag of Card/Page yet.

你好,Mingle是可以在5人以下团队免费使用的,免费的License应该会随同Mingle的下载链接一起发送到你的注册邮箱中。注册之后,在Mingle中少于5个激活(activate)用户的情况下,不会出现这个提示信息。

Hi amanking,
It’s a little tricky to get the card comment. Once you add a comment into current version of card, it becomes a version in history.
For example, I created a card version 1. Then I added a comment into card version 1. What I get from the response is a new version card(version 2) which doesn’t have any comment yet. You can get the comment added by getting the card version 1.
To get an old version of card, you need specify a param named version (not card[version]) with an version number, e.g. version=1. It is same with the URL param showed in browser when you are viewing an old card version in Mingle.

Hi Wouter,
Creating/updating card with card_type_name by REST API works well for me (just tested it again).
And your log is also looks fine.
If you can provide more details about what you tried, like code or the steps you did, I would like to retry it and see what’s problem.

Hello Jonathan – there is currently no way you can get card data through the API via MQL. We will let you know more, via these forums, if such a feature becomes available in a future release.

The new api for getting all favorites would be available in comming release 2.0.1.
You can get all favorite views and tabs.
The format would be looked like the following example:
<favorite>
<favorited_type>CardListView</favorited_type>
<id type="integer">103</id>
<project_id type="integer">12</project_id>
<tab_view type="boolean">false</tab_view>
<name>2.0 Tasks</name>
</favorite>

auth_config.yml should be created in the <mingle_data>/config directory after Mingle installled and first user login Mingle.
If there is no one, you can create one for it.