vtex-io-client-integration

Select VTEX IO client abstractions for backend service-to-service HTTP calls.

39|9|Updated Mar 16, 2026
One-click install
npx skills add https://github.com/vtex/ai-skills --skill vtex-io-client-integration
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vtex-io-client-integration
Source: https://github.com/vtex/ai-skills/tree/main/tracks/vtex-io/skills/vtex-io-client-integration
Command: npx skills add https://github.com/vtex/ai-skills --skill vtex-io-client-integration

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enables VTEX IO backend teams to determine and implement the correct client strategy for integrating with VTEX services and external APIs using the VTEX IO client abstractions, ensuring consistent authentication, retries, and observability.

Core Features & Use Cases

  • Client strategy guidance: helps decide when to use native VTEX clients, JanusClient, or ExternalClient.
  • IOClients pattern enforcement: promotes registering clients in IOClients and accessing them via ctx.clients.
  • Best practices & guardrails: codifies instance options, headers, metrics, and error handling to reduce misconfigurations.
  • Use case examples: among back-end modules integrating with core VTEX services or external APIs.

Quick Start

Install and configure the VTEX IO client integration pattern in your backend project.

Frequently Asked Questions about vtex-io-client-integration

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I choose between native VTEX clients, JanusClient, and ExternalClient for backend integration?

For VTEX IO backend integration, use native VTEX clients for internal VTEX services, JanusClient for stable platform proxying, and ExternalClient for third-party API connectivity to ensure correct API access and consistent authentication.

How do I register and use VTEX IO clients in a backend app?

Register VTEX IO clients by declaring them within the IOClients object, then retrieve them via ctx.clients during runtime to ensure consistent authentication, retries, and observability for backend integrations.

Why should service-to-service HTTP calls go through VTEX IO clients instead of ad hoc HTTP code?

VTEX IO clients enforce transport safety rules including header management, automated retries, and metrics collection, ensuring consistent authentication and observability that ad hoc HTTP code cannot provide for backend integrations.

What are the best practices for configuring instance options and error handling in VTEX IO clients?

Configure VTEX IO clients by codifying instance options, headers, and metrics to reduce misconfigurations, enforcing transport safety rules and error handling to ensure consistent authentication and observability for backend integrations.

Does my VTEX IO backend integration require specific client abstractions for external APIs?

Yes, VTEX IO backend integrations with external APIs require the ExternalClient abstraction to maintain consistent authentication, retries, and observability across all service-to-service HTTP calls.