The Limnu external API, associated payment models, API authentication keys, and API calls are all in active development.
If there’s anything that would make this system better for you and your products, please let us know by contacting firstname.lastname@example.org.
Limnu API and API Key notes
All the functions in the Limnu External API require the use of an API Key issued from Limnu. An API key may be issued to either a team or a user account. Currently, API keys may only be issued by Limnu support manually.
If for any reason you ever need to retire your current API key and replace it with a new one, this can easily be done by contacting Limnu support.
If you have a valid API key, but your account is not in good standing (that is, you are not paying for your account, or you have no trial credit attached to your account), then all Limnu External API functions with your API key will fail.
Limnu External API commonalities
All Limnu External API v1 calls adhere to the following rules:
- The URL for a function is
- All functions are all of type POST.
- The body of the POST request is a JSON object.
- The response to the POST request is a JSON object.
- All responses will have a boolean
successattribute in the JSON object.
- If the call fails,
successwill be false, and the additional
reasonattribute will be included in the JSON object for describing the failure.
- Limnu API Overview
- Getting an API Key
- Current Version & Changelog
- Function: userActive
- Function: userCreate
- Function: userUsage
- Function: boardActive
- Function: boardCreate
- Function: boardDelete
- Function: boardList
- Function: boardRename
- Function: boardUsage
- Function: boardImageURLUpload
- Function: boardImageFileUpload