All integrations
No-code workflows: check invoices from email, files or URLs and route on the result.
An Actor in the Apify Store: a list of URLs in, one row per document out. Pay per document, no account needed.
Every API request with real responses: try the API, then generate code or run it in CI with Newman.
Claude, Cursor and VS Code can validate documents, find schemas and explain errors and rules.
Check XML in every pull request, in pre-commit hooks, GitLab CI or any script.
Validate from your own code, with webhooks and URL monitors. Described as OpenAPI 3.1.
Which one to use
- Invoices arrive by email or land in a folder
- n8n: a trigger, the xmlvalid node and an If node that sends valid invoices on and the others back.
- You have a list of documents on the web
- Apify: paste the URLs, get a table you can export to CSV or Excel, on a schedule if you like.
- You are building on the API
- Postman to try the requests, then the API reference.
- Your repository holds XML
- The command-line client and the GitHub Action.
- You work with an AI assistant
- The MCP server: ask it to check a file or explain an error.
- A single document, now
- The validator in your browser: free up to 1 GB, and the document never leaves your machine.
API keys and limits
Every integration here except the browser validator calls the xmlvalid API with a key from Dashboard → API keys, and each document checked is one API validation: 100 a month on Free, 10,000 on Pro. The Apify Actor is the exception: without a key of your own it runs on ours, and Apify charges per document instead.
Documents sent to the API are validated on our servers in the EU and deleted as soon as the check finishes; see Security.