actualNoteContentPart: If you're interested in building plugins (even if only for your own use) and would be interested in a chance to influence the plugin system, feel free to email support@amplenote.com from the email address associated with your account. Feedback can be provided in the #plugin-atelier channel on our [discord](https://discord.gg/nAj4wp4sJm) .
  
   
  Amplenote provides support for client-side plugins that execute in the application on all platforms, allowing for enhancement of the default client behavior. A plugin is defined by a single note in a user's account - as the note is changed and updated, the plugin will be updated as well.
  
  These documents provide an overview of what plugins are capable of, and describe the available options for plugins. Related help pages that may be of use to plugin authors include:
  [**Guide to getting started writing plugins**](https://www.amplenote.com/help/guide_to_developing_amplenote_plugins) , a page to help writing your first plugin.
  [**How to apply markdown formatting**](https://www.amplenote.com/help/plugin_api_markdown_reference_parse_markdown)  explains how to produce colored text, line breaks, Rich Footnotes, tables, etc via the Plugin API's functions
  
  These pages are the most comprehensive reference guide of Plugin API functionality. The sections are as follows:
  [Plugin creation](/help/developing_amplenote_plugins/plugin_creation)  Learn how to structure a plugin note to create a valid plugin
  [Actions](/help/developing_amplenote_plugins/actions) Learn what hooks are provided for plugins to implement
  [App Interface](/help/developing_amplenote_plugins/app_interface) Learn how plugins can interact with note/task/etc data via app.* function calls
  [Note interface](/help/developing_amplenote_plugins/note_interface) Additional abstraction allowing App Interface interactions specific to a single note
  [Examples](https://www.amplenote.com/help/developing_amplenote_plugins/examples)  Accumulated examples of using the plugin API for common tasks
  
  [Appendix I: Types](/help/developing_amplenote_plugins/appendix_i)  
  [Appendix II: Plugin code execution environment](/help/developing_amplenote_plugins/appendix_ii)  
  [Appendix III: Markdown content](/help/developing_amplenote_plugins/appendix_iii)  
  [Appendix IV: Loading external libraries](/help/developing_amplenote_plugins/appendix_iv)  
  
   
  # Update history
  ### 2025
  Add [app.setNoteSetting](/help/developing_amplenote_plugins/app_interface#app.setNoteSetting)  / [app.getNoteSettings](/help/developing_amplenote_plugins/app_interface#app.getNoteSettings)  
  Add [app.openEmbed](/help/developing_amplenote_plugins#app.openEmbed)  
  Add [onNoteCreated](/help/developing_amplenote_plugins#onNoteCreated)  action
processedNoteContent: ---
  title: Plugin API Reference Documentation
  tags: 
  ---
  If you're interested in building plugins (even if only for your own use) and would be interested in a chance to influence the plugin system, feel free to email [support@amplenote.com](null)`
   from the email address associated with your account. Feedback can be provided in the #plugin-atelier channel on our [discord](https://discord.gg)`
   . Amplenote provides support for client-side plugins that execute in the application on all platforms, allowing for enhancement of the default client behavior. A plugin is defined by a single note in a user's account - as the note is changed and updated, the plugin will be updated as well. These documents provide an overview of what plugins are capable of, and describe the available options for plugins. Related help pages that may be of use to plugin authors include:
  [Guide to getting started writing plugins](https://www.amplenote.com)`
   , a page to help writing your first plugin.
  [How to apply markdown formatting](https://www.amplenote.com)`
    explains how to produce colored text, line breaks, Rich Footnotes, tables, etc via the Plugin API's functions These pages are the most comprehensive reference guide of Plugin API functionality. The sections are as follows:
  [Plugin creation](/help/developing_amplenote_plugins/plugin_creation)
    Learn how to structure a plugin note to create a valid plugin
  [Actions](/help/developing_amplenote_plugins/actions)
   Learn what hooks are provided for plugins to implement
  [App Interface](/help/developing_amplenote_plugins/app_interface)
   Learn how plugins can interact with note/task/etc data via app.* function calls
  [Note interface](/help/developing_amplenote_plugins/note_interface)
   Additional abstraction allowing App Interface interactions specific to a single note
  [Examples](https://www.amplenote.com)`
    Accumulated examples of using the plugin API for common tasks [Appendix I: Types](/help/developing_amplenote_plugins/appendix_i)
  
  [Appendix II: Plugin code execution environment](/help/developing_amplenote_plugins/appendix_ii)
  
  [Appendix III: Markdown content](/help/developing_amplenote_plugins/appendix_iii)
  
  [Appendix IV: Loading external libraries](/help/developing_amplenote_plugins/appendix_iv)
  
  Update history
  
  2025
  Add [app.setNoteSetting](/help/developing_amplenote_plugins/app_interface#app.setNoteSetting)
    / [app.getNoteSettings](/help/developing_amplenote_plugins/app_interface#app.getNoteSettings)
  
  Add [app.openEmbed](/help/developing_amplenote_plugins#app.openEmbed)
  
  Add [onNoteCreated](/help/developing_amplenote_plugins#onNoteCreated)
    action
noteTitle: Plugin API Reference Documentation