I think the best option for what it sounds like you want to accomplish is to use dynamic fields.  This is precisely what that feature is for! And rather than presenting those as a dictionary, you can retrieve custom field definitions from your API and render them as normal input fields. Rather than using a trigger for the purpose you write a function make the request to your API and return one or more field definitions. 

I posted an example the other day here

Let us know if you have any questions getting that set up.

Our current integration offers 5 questions and answers to be added but some customers have requested for more than 5. We would like to allow for an unknown number of questions and answers to be submitted.

The dictionary input appears to be the only one that supports a dynamic collection of questionIds and answerIds to be submitted. Which would be ideal, if the available dictionary keys could be driven by a dropdown list that derives it’s values (questionIds) from an API request.

As some of our clients have many defined questions, I would prefer an approach that avoids death by a thousand fields.

I believe dynamic fields are going to be your best option here.