Hi @atsushi_kuno. I am not experienced in creating add-ins for Inventor, but what you seem to be asking about may not actually be about creating an add-in, but simply how to use other built-in add-ins by code. Since you seem to be focused on the TranslatorAddIn sub type of Inventor add-ins, there is actually a couple methods for visibly 'showing' them in the user interface, for manual user interaction.
Below are links to the online help documentation about those two methods:
TranslatorAddIn.ShowOpenOptions
TranslatorAddIn.ShowSaveCopyAsOptions
As far as I have ever seen them used, they are primarily used to allow the user to manually review and/or change any 'Options' that you may normally be able to see when you would have normally clicked on the Options button within the Open or Save file dialog screens while opening or saving a file, but initiated by code, so that the resulting settings can be captured within the code. Most import/export code examples do not use this, because we usually just specify the settings/options within the code, using a NameValueMap. But sometimes export options need to change often enough that hard-coding into the import/export block of code is not efficient or effective enough. In cases like that, the options dialog can be shown to the user, allowing them to manually interact with it, then once they click OK (or otherwise exit that dialog), control returns to the code process. Showing the dialog does not actually open or export anything, it only captures settings/options, which can then be read from within the 'ChosenOptions' (NameValueMap).
If those two methods are not what you were looking for, then your next options may be to execute a command to import/export a file, but then all control will be given to the user interface tools, and you will most likely not be able to interact with them by code at all. We usually have very little code based control over any of the dialogs that get shown by Inventor...unless maybe you are including a lot of really advanced code for finding and interacting with foreign dialogs (dialogs that you did not fully design and implement yourself), and have done a ton of exploring those specific dialogs, to be able to find specific stuff within them, and know how to interact with them by code.
Wesley Crihfield

(Not an Autodesk Employee)