Your iFormBuilder forms have always been powerful data collectors — but what if they could also reach out and pull in exactly the information they need, right at the moment it’s needed? That’s now possible with the HTTP Request element, and it’s changing how teams think about dynamic, connected forms.
Connect Your Forms to Authenticated iFormBuilder Resources
One of the most significant improvements to the HTTP Request element is the ability to access authenticated resources within the iFormBuilder platform — not just open, public APIs on the web. This means your forms can now securely reach iFormBuilder’s own API endpoints at runtime, pulling in data from your existing records, lists, and configurations without any manual prep work.
Watch the walkthrough to see:
- How to add and configure the HTTP Request element in your forms.
- Using iFormBuilder’s authenticated API endpoints directly from the field.
- Building dynamic, data-driven requests that respond to what’s already in the form.
Replace Bulky Lookups with On-Demand API Calls
Many teams today rely on large lookup tables embedded in their forms to handle reference data — long lists loaded upfront whether or not every record will be needed. With the HTTP Request element, there’s a smarter way. When a device is connected to the internet during use, your form can call the iFormBuilder API and retrieve only the data relevant to that moment. Smaller payloads, faster forms, and no stale data to manage.
This approach is especially valuable for teams working with:
- Asset lookups tied to location, job type, or inspection criteria.
- Reference lists that change frequently and need to stay current.
- Conditional data scenarios where only a subset of records is ever relevant.
Make Requests Dynamic Using Existing Form Data
What makes the HTTP Request element particularly powerful is that your API calls don’t have to be static. You can reference data already captured in the form — a scanned asset ID, a selected category, a user-entered value — and use it to shape the request itself. This means one well-designed form element can handle thousands of different scenarios without a single hard-coded value.
Take it a step further: you can even build a lookup table of API request templates and feed them dynamically into the HTTP Request element at runtime. Instead of maintaining dozens of separate requests, a single element adapts based on what the form needs at that moment.
Full Details in the Help Center
Ready to dive in? Our help desk article walks through everything you need to configure the HTTP Request element, including how to set up authentication, structure your request, and map the response back into your form fields.
Read the full guide in the Help Center →
Have questions or want to see how this could work for your specific use case? Reach out to us at sales(@)zerionsoftware.com — we’re happy to help you think through the design.
Thanks for being part of the iFormBuilder community.
We’re here to support you every step of the way, whether you’re building better forms, automating operations, or discovering new ways to put your data to work.
