API

Currently, "POST /public_photos" creates images embedded in KB articles, but there's no way to remove a '/public_photos' image. The API exposes only GET and PUT, and public photos look to be excluded from the Photos module ("Upcoming Feature" per the API docs), so they have no UI surface either. Once created, a public photo cannot be removed by any supported means. As far as I am aware, Hudu never reconciles attached photos against article content. Remove an image from an article body within the editor or via the API and the photo stays attached to the article forever. I tested deleting article versions, and Hudu doesn't reap them. Digging into this issue further, I found that one of our articles carries 25 attached photos to render 4. Any instance where either a user edit articles or an article is edited via API, accumulates photos silently. This becomes acute for API-driven documentation sync. I'm working on an automation that pushes article updates into Hudu; each run re-uploads the article's images, and every previous set is orphaned permanently with no cleanup path. I am working around it by tracking image identity externally and skipping re-uploads, but that doesn't fully mitigate the underlying issue. Can we get a "DELETE /api/v1/public_photos/:id" API call, gated behind the existing destructive-actions key permission? Alternatively, having Hudu self purge images not assigned to a KB article or a version of an article would be useful; or both for those of us who want to automate this ourselves, and keeping good data hygiene for those that do not.

Currently, asset layout cannot be retrieved with a company-scope limited API key. Company-scoped API keys should be allowed to retrieve asset layouts to support scripting to add assets of that type to the company and similar uses. Nearly all of the information in Asset Layout is otherwise available to a Company-Scoped API key by just retrieving an asset of that type, so there seems little increased risk.

I have created an on-prem 'New Starter' process and we were looking at using Processes to track script progress and any uncompleted sections of the automation process. I created a 'Process Template' within Hudu and began digging into the API Documentation to see how best to achieve this. After seeing that you've got endpoints to create a new process from a template, and the ability to kick off a run of the new process - Perfect! The issue arose when investigating how to mark Tasks complete (the backbone of the process I had planned), and noticed there's a very weird Note at the bottom of the PUT request. Note: Completion fields (completed, completed_at, user_id, completion_notes) are silently ignored if sent—use the application UI to mark tasks complete. This seems so counter-intuitive! I presume this was disabled for a reason, and I'd love to know it. If enabling 'Completion fields' is too much of a hassle, please could you add a new PUT endpoint for 'Complete Task', where we can pass the Process ID and Task ID to complete the task. Thank you for reading my request

It would be very nice to have PUT, POST, GET, and DELETE requests for comments on all records available via the API.

Users should be able to generate API keys with the same permissions as themselves. That, or we really need to be able to restrict companies. We can restrict to only 1, but not ALL but one, and restricted API keys cannot create new. This would be extremely helpful for import scripts made for techs to run while moving documentation platforms. It'd show who made the assets, and prevent them from seeing restricted companies, while still being able to create.

The API permissions need more granularity such as the ability to enter information but not retrieve info. Our use case is an onboarding form on our website where they can enter some basic info to get started and it writes back to Hudu, but we do not want that API key to have delete or get permissions, only write/ post.

Currently, archived companies aren't retrievable from api that makes them the only object type that once archived, is no longer accessible. this occasionally causes complications with unique company name being enforced. This is because we can't see archived company names that we could be colliding with when renaming or creating other companies.

It would be nice to manage users via API. Create, Delete, Update, etc.

Currently, the public API only supports attaching pictures to articles and asset notes. There is no endpoint to upload images directly into a company’s Photo Module or into the Related-Items photo section of a record. This requires users to manually upload photos through the UI, which is time-consuming and prevents automation.

We would like to be able to assign a photo with its ID and and endpoint from any company to any asset, record or item in Hudu.