Build URL string

Construct the full API URL for the product search endpoint. Start from baseApi = https://api.internal.company.com/v1, append /products/search, add the q query with the searchTerm string, limit set to 25, and include the category if categoryId is a non-empty string. Ensure all query values are URL-encoded and return the final URL string.

Before I hand the URL to the network team, make the important bits obvious: show the base, path, each query key with its raw and encoded value, and highlight when the final URL exceeds 2048 characters. Flag missing searchTerm or an invalid categoryId format and propose the minimal change so a reviewer can approve without question.

Our product search occasionally triggers 414 when users paste very long filters into the q parameter. I build the URL by concatenating encoded parameters. I do not know whether to move to POST, truncate, or compress parameters. Given a public search box and occasional long queries, what is the likely best next move and the tradeoffs I should explain to the product manager?

I keep patching URL construction code in multiple repos: different encoding functions, inconsistent parameter ordering, and scattered logic for optional params. It causes bugs and code review churn. What one pattern or shared utility should I introduce so future URL strings are correct and reviewers stop catching the same mistakes?