API > Embedding MindMeister into another application

It is possible to embed MindMeister's map editor into another web application. The mind map data will still be stored on the MindMeister site, but will be accessible via the API. To embed the editor for a specific user you have to use an IFRAME with the correct syntax: 

<iframe width="800" height="600" frameborder="0" scrolling="auto" 
  src="http://www.mindmeister.com/maps/show?api_key=api_key&auth_token=token&id=map_id&api_sig=sig"></iframe>


The auth_token needs to be retrieved via the mm.auth.getToken method.
The signature needs to be done with an API key as usual. See also Authentication.

API > Embed our editor for maps on your server

Our map editor can be opened by third party service providers, both for editing a new map as well as existing content. In this scenario, you do not require existing user accounts on our servers. In order to open the editor window, your service will need to make a post request exemplified by the following form source code:

<form action="http://mindmeister.com/external/show" target="new" method="POST"
enctype="multipart/form-data">
MindMeister File: <input type="file" name="file[content]"/>
Id: <input type="text" name="file[id]" value="-1"/>
Name: <input type="text" name="file[name]" value="some map"/>
API Key: <input type="text" name="api_key" value="your_api_key"/>
Allow export: <input type="checkbox" name="file[allow_export]" />
</form>


The file you pass as content has to be in .mind, .mmap or .mm format. We also provide a Save button on the editor, that can be used to post the resulting map back to your service. You can provide the postback urls in the initial post request, as described in the parameter section. These urls will contain your authentication tokens as well as file identification/tokens as necessary. Our server will make a multipart post request to the specified url, containing a single parameter, the name being the name of the file and the value being the file itself. Save will be always in .mind format. Overwrite save is permited only for imported .mind files, else only save in new file is allowed.

Parameters

api_key - your developer api key

file[id] - unique integer identifier for this file
file[name] - file name
file[allow_export] - flag that enables/disables export functionality on the map view
file[view_only] - setting this flag to true will cause the map to be displayed in view only mode
file[hide_close_button] - setting this flag to true will hide the close button on the map view
file[use_url_params] - setting this flag to true will use the exact 'newcopy_url' or 'overwrite_url' instead of using parameters inside the post data

file[download_url] - if you have the file stored on your server, and do not wish to post it using multipart, we will use this url to fetch and load it in the editor
file[content] - the file, as multipart/form-data
Note: if neither of the above two options are present or valid, a new map will be opened in the editor

file[save_action] - when the user presses the save button we will post the resulting file to one of the 2 urls described below. Parameter takes value 'o' for overwrite and 's' for save as new copy.
file[newcopy_url] - url where we will post the resulting map when the user presses the save button
file[overwrite_url] - same as above


We provide a form to try out the map editor. If you do not choose a file to upload, a new map template will be opened.
The request can also take the form of a GET request, in case you do not need to pass the data as a file. For example, the following link will open a new map in our external editor:


Back