fetch-validations

Fetches structured per-transaction validation errors from Orderful's internal UI API.

6|6|Updated Apr 29, 2026
One-click install
npx skills add https://github.com/Orderful/orderful-netsuite-skills --skill fetch-validations
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fetch-validations
Source: https://github.com/Orderful/orderful-netsuite-skills/tree/main/skills/fetch-validations
Command: npx skills add https://github.com/Orderful/orderful-netsuite-skills --skill fetch-validations

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill removes the need to screenshot and manually inspect Orderful UI validation failures by fetching the structured, per-transaction validation errors directly from Orderful’s internal endpoint.

Core Features & Use Cases

  • Fetch structured validation errors: Pulls machine-readable details for one or more NetSuite-linked Orderful transactions (including dataPath, message, and allowedValues when applicable).
  • Deduplicate noisy repeats: Collapses repeated error patterns so you can quickly identify the underlying partner-spec/JSONata issue.
  • Drive faster JSONata iterations: Uses the exact failing data paths and allowed codes to guide the next fix and confirm whether errors disappear after redeploys.
  • Common use cases: Debugging INVALID 850/810/855/856/810 mappings, validating partner-spec JSONata changes, and answering requests like “what’s wrong with this transaction” without UI clicking.

Quick Start

Run a batch fetch for one or more transaction IDs using an Orderful UI session JWT, for example: Ask Claude Code to execute fetch-validations with your transaction id(s) and ensure ORDERFUL_UI_JWT is set (or a ui.orderful.com.har file is available for token extraction).

Frequently Asked Questions about fetch-validations

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

FAQPage Schema
How do I get Orderful validation errors for debugging INVALID EDI transactions?

Fetch Orderful validation errors by calling the internal UI API with a session JWT to retrieve structured per-transaction data. This returns deduplicated error patterns, including dataPath, message, and allowedValues, to guide JSONata mapping fixes.

How do I authenticate API requests to pull Orderful transaction validation details?

Authenticate Orderful validation requests by providing a UI session JWT via the ORDERFUL_UI_JWT environment variable or extracting it from a local ui.orderful.com.har file. The token is required to resolve your ORG_ID and access the validations endpoint.

Can I fetch validation errors for multiple Orderful transactions at once?

Yes, you can fetch validation errors for multiple Orderful transactions in a batch. The Skill pulls structured data for each transaction ID and returns a deduplicated list of error patterns with counts, streamlining multi-transaction debugging.

What is the best way to identify failing X12 data paths in Orderful JSONata iterations?

The best way to identify failing X12 data paths is to fetch structured validation errors directly from the API. This provides exact dataPath and allowedValues for each error, allowing you to pinpoint partner-spec JSONata issues without manually inspecting UI screenshots.

Does fetching Orderful validations work for debugging NetSuite-linked EDI mappings?

Yes, fetching Orderful validations works for debugging NetSuite-linked EDI mappings such as 850, 810, 855, and 856 documents. It extracts machine-readable error details to validate partner-spec JSONata changes and confirm fixes after redeploys.