For training managers, instructional designers, or HR leaders, two key challenges often recur in digital learning: data reliability (tracking, compliance, governance) and the customization of learning paths (profiles, permissions, goals). The VTS Web Request Block<\/strong> connects your experiences to your key systems \u2014 LMS\/LRS, HRIS, CRM, BI tools, or internal platforms \u2014 and enables real-time data flow: scores, progress, quiz results, xAPI traces, path unlocking, and proof of learning. With VTS Editor<\/a>, you can create connected, dynamic, and measurable modules without any technical skills.<\/p>\n Practically speaking, this API connector performs HTTP calls to your services: you provide the URL, authentication headers, method (GET\/POST\/POST Raw), the maximum timeout, and whether the scenario waits for the response. The response is stored in a VTS Editor variable to power your graph using Conditions, update Score\/Progress, trigger Badges, or display targeted Messages.<\/p>\n In this article, you’ll learn how to configure the block step by step, apply it to five real-life use cases, and then secure and validate your integrations using simple best practices.<\/p>\n Start with your service\u2019s URL \u2013 for example: Best practice: store your secrets ( You can insert variables anywhere \u2014 in the URL, headers, parameters, or body. In the VTS Web Request block<\/em> configuration, choose a target variable (e.g., The block provides two outputs: success (response received) and error (failure\/timeout). By enabling \u201cWait for Request Completion\u201d, the graph pauses until the response is received; otherwise, the experience continues during the call (asynchronous). Set a realistic timeout (5 to 10s) to avoid unnecessary blocking. Always provide a fallback route: instructional message, \u00ab\u00a0Try again\u00a0\u00bb button (with Counter<\/strong> + Wait<\/strong>), or an offline mode (local resources).<\/p>\n A proven flow involves chaining Web Request \u2192 Conditions \u2192 Feedback\/Actions<\/strong>:<\/p>\n Tip: group your \u201cmini-chain\u201d of calls (auth, send, read) into a Group<\/strong> set as a Function<\/strong>, then call it using Function Call<\/strong> from different scenes. This improves readability and maintainability.<\/p>\n Goal: centralize tracking, trigger HR rules, and feed BI. At the end of a quiz or key scene, send a JSON POST Raw<\/strong> with Goal: maintain your content without republishing. A GET<\/strong> such as Goal: easily track engagement. Configure a webhook (Google Apps Script, Make, Zapier) and send a POST<\/strong> with name, email, entry\/exit time, score, and IP (if your DPO authorizes). The response may include a registration ID: display it, and if generating a certificate, open the link via Open Web Page<\/strong>. To get started quickly, request a demonstration of VTS Editor<\/a>.<\/p>\n Goal: control access to sensitive or premium content. The learner enters a code via a Numerical Keypad<\/strong>; you validate it server-side via the VTS Web Request block<\/em>. On success: Goal: foster learner competition and ensure consistent randomization. Read a central seed<\/em> to drive the randomness of your variables and make puzzles comparable. At the end of the journey, post scores, then retrieve a leaderboard<\/em> to display. This format works great for sales challenges, safety days, or internal events. Be inspired by our client cases<\/a>.<\/p>\n The VTS Web Request Block<\/strong> opens your modules to real enterprise data. Associated with the Score\/Progress, Flags\/Conditions, Badge, Message, or Menu blocks, it enables the design of adaptive, auditable scenarios driven by your systems. For training managers, this means robust tracking; for instructional designers, vibrant content; for HR, a scalable foundation. Try the suite for free: Try Virtual Training Suite<\/a>.<\/p>\n Why the VTS Web Request Block Is Transforming Your E\u2011Learning Modules For training managers, instructional designers, or HR leaders, two key challenges often recur in digital learning: data reliability (tracking, compliance, governance) and the customization of learning paths (profiles, permissions, goals). The VTS Web Request Block connects your experiences to your key systems \u2014 LMS\/LRS, HRIS, CRM, BI tools, or…<\/p>\n","protected":false},"author":12,"featured_media":6615,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1035],"tags":[963],"class_list":["post-6614","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-vts-editor-en","tag-vts-editor-blocks"],"_elementor_source_image_hash":null,"_wp_attachment_image_alt":null,"_thumbnail_id":"6615","_yoast_wpseo_twitter-description":null,"_yoast_wpseo_twitter-title":null,"_yoast_wpseo_twitter-image":null,"_product_image_gallery":null,"_yoast_wpseo_focuskw":"VTS Web Request block","_yoast_wpseo_title":"Unlock the Potential of the VTS Web Request Block for Your E-Learnings","_yoast_wpseo_metadesc":"Boost your training courses with the VTS Web Request block: connect your e-learning modules to your APIs for dynamic and traceable learning paths.","yoast_head":"\nStep-by-Step Configuration of the VTS Web Request Block<\/h2>\n
Define the Endpoint and Authentication<\/h3>\n
https:\/\/api.your-domain.com\/v1\/events<\/code> or https:\/\/...\/users\/{userId}\/score<\/code>. Variables in curly braces are replaced at runtime by their corresponding VTS values (userId<\/code>, sessionId<\/code>, lang<\/code>, score<\/code>, etc.). On the security side, most APIs require headers such as:<\/p>\n\n
Authorization: Bearer {token}<\/code> (OAuth2\/JWT)<\/li>\nx-api-key: {apiKey}<\/code> (dedicated API key)<\/li>\nContent-Type: application\/json<\/code> when sending JSON (POST Raw)<\/li>\nlocale<\/code>, version<\/code>, correlation-id<\/code> (for your logs), etc.<\/li>\n<\/ul>\ntoken<\/code>, apiKey<\/code>) in variables initialized at the beginning of the module via an authentication request, rather than hard-coding them. This reduces risks and eases key rotation.<\/p>\nSelect the Right Submission Method<\/h3>\n
\n
?userId={userId}&lang={lang}<\/code>.<\/li>\n{\"userId\":\"{userId}\",\"score\":{score},\"status\":\"completed\",\"timestamp\":\"{isoNow}\"}<\/code>. Since VTS Editor injects variables using { }<\/code>, define custom delimiters if your content includes many special characters to avoid conflicts.<\/li>\n<\/ul>\nInsert Variables and Store the Response<\/h3>\n
result<\/code>) to store the raw response. The scenario can then use result<\/code> in Conditions<\/strong>, Message<\/strong>, Score<\/strong>, Progress<\/strong>, etc., and instantly adapt the learning path.<\/p>\nControl the Flow: Wait, Timeout, and Outputs<\/h3>\n
Read and Use the Response<\/h3>\n
\n
fromJson(result)<\/code> converts the text response into dictionaries\/lists. Then access fromJson(result).data.score<\/code> or fromJson(result).status<\/code>. Before using a key, always verify it exists (via Conditions<\/strong>).<\/li>\nregexMatch(result, \"pattern\")<\/code> to validate a format; extractText(result, \"pattern\", 1)<\/code> to extract a value from non-JSON responses.<\/li>\ntoInteger(result)<\/code> if the API returns a plain number, or toInteger(extractText(...))<\/code> to convert a string to an integer.<\/li>\n<\/ul>\nA Robust Graph Template<\/h3>\n
\n
High-Impact Use Cases with the VTS Web Request Block<\/h2>\n
Send Scores and Progress to Your LMS\/LRS or Business Service<\/h3>\n
userId<\/code>, scenarioId<\/code>, overall score, scores by skill, status (passed\/failed<\/code>), time, and ISO timestamp. If successful, use Progress<\/strong> (completed + passed), assign a Badge<\/strong> and, if needed, unlock premium content via Check Score<\/strong>. On error, display a message and suggest a retry. For deployment and analytics, explore VTS Perform<\/a>.<\/p>\nRetrieve Up-to-Date Content in Real Time<\/h3>\n
\/procedures?context={job}&lang={lang}<\/code> returns a JSON with titles and steps. Parse it with fromJson(result)<\/code> to populate lists, then inject that content into a Message<\/strong>, a Slideshow<\/strong>, or Clickable Zones<\/strong>. Perfect for frequently changing procedures (safety, compliance, offerings): you shorten update times. For your modules, see our formats for gamified e-learning modules<\/a>.<\/p>\nRegistration, Attendance, and Lightweight Proof of Learning<\/h3>\n
Conditional Unlocking via Server-Side Verification<\/h3>\n
Flag access_premium = True<\/code>, a Menu<\/strong> displays bonus chapters. On failure: clear message, increment of a Counter<\/strong> for retry attempts, and a remediation path. Useful for monetization, regulatory prerequisites, or restricted access (e.g., managers).<\/p>\nCentralized Rankings and Draws to Create Challenge<\/h3>\n
Security and Performance Best Practices for the VTS Web Request Block<\/h2>\n
Secure Your Calls<\/h3>\n
\n
userHash<\/code>) rather than a named email.<\/li>\nEnsure Experience Reliability<\/h3>\n
\n
Optimize Performance<\/h3>\n
\n
page<\/code>, limit<\/code>) on reads.<\/li>\nComply with IS Constraints<\/h3>\n
\n
Test and Diagnose Quickly<\/h3>\n
\n
result<\/code>) and your parsed variables in real time.<\/li>\nfromJson<\/code> by checking their presence via Conditions<\/strong>.<\/li>\nregexMatch<\/code>\/extractText<\/code>) before generalizing.<\/li>\nTake Action: Connect VTS Editor to Your APIs<\/h2>\n
Quick Deployment Checklist<\/h3>\n
\n
fromJson<\/code>, regex) and route with Conditions<\/strong>.<\/li>\nGo Further<\/h3>\n
\n
References and Useful Resources<\/h2>\n
\n