API

Being able to search processes/procedures via the API would be extremely helpful so that I could target specific words instead of pulling all the processes to search through them

Add the ability to create and send Secure Notes via the API. This would allow secure notes to be programmatically created and updated from external systems, improving automation and integration workflows while keeping sensitive data protected.

We are integrating Active Directory users into Hudu via the API and have identified what appears to be an API-only issue with UTF-8 / non-ASCII characters. Observed behavior When creating an asset via the API, requests fail with HTTP 400 (Bad Request) if asset.name contains Danish characters such as Æ, Ø, or Å. Example: name = "Test 1234" → ✅ works name = "Test ÆØÅ 1234" → ❌ HTTP 400 Minimal payload that fails: { "asset": { "name": "Test ÆØÅ", "asset_layout_id": 9 } } Important detail (UI vs API) If we create the same asset name containing ÆØÅ via the Hudu web UI, it saves successfully. This suggests the issue is specific to the API request handling (or API-specific filtering/parsing).

Would be nice to use the API to get a list of all flagged articles

Inforcer have recently released a REST API that should allow an integration to be possible. https://www.inforcer.com/

Please add the ability to download files via the API.

As per title, I would like it if the API allowed for password share links to be created.

Please add API endpoints to retrieve SPF, DMARC and DKIM information.

I want to allow an API key to access metadata about asset_passwords without accessing the password or otp_secret fields themselves. For my purposes, the username and login_url could also be excluded. This could be accomplished with either a new permission under "Key can perform the following actions" or a new endpoint. The goal would be to allow an API key to check when a specific asset_password was created or updated, if it's archived, the company ID and password folder, and be searchable by all the same options as the current endpoint, _without_ having access to the actual credentials.

I would like to be able to edit the expiration dates of knowledge base articles via the API. This would allow expiration dates to be set programmatically, given that there is currently no way to set default expiration dates on articles.