CT-e XML Schema Compliance API API ID: 12733

Verify CT-e XML schema compliance quickly using our CT-e XML Schema Compliance API for hassle-free validations.
Use this API from your AI agent via MCP
Works with OpenClaw, Claude Code/Desktop, Cursor, Windsurf, Cline and any MCP-compatible AI client.
Docs & setup
Create a skill by wrapping this MCP: https://mcp.zylalabs.com/mcp?apikey=YOUR_ZYLA_API_KEY

CT-e XML Schema Compliance API

Validate Brazilian Nota Fiscal Eletrônica (NF-e, mod 55), NFC-e (mod 65), and CT-e (mod 57) XML against current SEFAZ schemas — and get back the exact element paths that failed, not a cryptic rejection code. Built for fiscal-tech developers, ERPs, and e-commerce checkout integrations that need to catch malformed fiscal documents before SEFAZ does.

Most Brazilian fiscal APIs (Focus NFe, Webmania, NFe.io) are full emission stacks — heavy, priced for issuers, and overkill if you already hold the XML and only need to validate it. This is a pure-data validator: POST the XML, get a structured pass/fail with typed errors. The schema rules and per-município NFS-e quirks are not replicated by generic global validators.

What you get

  • Auto-detects document kind + schema version — NF-e 4.00 / 3.10, NFC-e, CT-e; no need to tell the API what you are sending.
  • Per-element error paths — e.g. /NFe/infNFe/ide/nNF with typed codes (MISSING_REQUIRED, INVALID_FORMAT, CROSS_FIELD, UNSUPPORTED_VERSION, INVALID_ROOT).
  • Well-formedness vs content-validity400 for malformed XML, 422 for schema-valid-but-content-invalid, 200 for valid.
  • Municipality-specific warnings array (NFS-e partial coverage).
  • 99%+ cached uptime, versioned /v1/ API, and daily SEFAZ schema-drift monitoring.
  • MCP-compatible — AI agents can discover and call this API via Model Context Protocol.

Example response (200 — valid NF-e 4.00)

{
  "valid": true,
  "errors": [],
  "schema_version": "4.00",
  "schema_kind": "nfe",
  "municipality_specific_warnings": []
}

Use cases

  • ERP / accounting software — validate inbound supplier NF-e before importing into your ledger.
  • E-commerce checkout — pre-validate CT-e/NF-e during fulfillment to avoid SEFAZ rejections downstream.
  • Document-intake pipelines — gate a fiscal-document upload form with instant, human-readable error feedback.

 

 

API Documentation

Endpoints


Validate a Brazilian NF-e (mod 55), NFC-e (mod 65), or CT-e (mod 57) XML document against current SEFAZ schema rules.
Returns a JSON result with a valid flag, per-element typed errors (element path + error code), the auto-detected schema version and document kind, and any municipality-specific warnings.



                                                                            
POST https://zylalabs.com/api/12733/ct-e+xml+schema+compliance+api/24633/validate+nf-e+xml
                                                                            
                                                                        

Validate NF-e XML - Endpoint Features

Object Description
Request Body [Required] Text Plain

Free test requests remaining: 3 of 3.


INPUT PARAMETERS


API EXAMPLE RESPONSE

{"valid":true,"errors":[],"schema_version":"4.00","schema_kind":"nfe","municipality_specific_warnings":[]}

Validate NF-e XML - CODE SNIPPETS


curl --location --request POST 'https://zylalabs.com/api/12733/ct-e+xml+schema+compliance+api/24633/validate+nf-e+xml' --header 'Authorization: Bearer YOUR_API_KEY' 

--data-raw '

  
    
      
        35
        00000001
        VENDA
        55
        1
        1
        2026-05-19T10:00:00-03:00
        1
        1
        3550308
        1
        1
        0
        2
        1
        0
        1
        0
        1.0
      
      
        11222333000181
        EMPRESA TESTE LTDA
        
          RUA TESTE
          100
          CENTRO
          3550308
          SAO PAULO
          SP
          01000000
        
        123456789012
        3
      
      
        22333444000172
        CLIENTE TESTE LTDA
      
    
  
'

    

API Access Key & Authentication

After signing up, every developer is assigned a personal API access key, a unique combination of letters and digits provided to access to our API endpoint. To authenticate with the CT-e XML Schema Compliance API simply include your bearer token in the Authorization header.
Headers
Header Description
Authorization [Required] Should be Bearer access_key. See "Your API Access Key" above when you are subscribed.

Simple Transparent Pricing

No long-term commitment. Upgrade, downgrade, or cancel anytime. Free Trial includes up to 50 requests.

🚀 Enterprise

Starts at
$ 10,000/Year


  • Custom Volume
  • Custom Rate Limit
  • Specialized Customer Support
  • Real-Time API Monitoring

Customer favorite features

  • ✔︎ Only Pay for Successful Requests
  • ✔︎ Free 7-Day Trial
  • ✔︎ Multi-Language Support
  • ✔︎ One API Key, All APIs.
  • ✔︎ Intuitive Dashboard
  • ✔︎ Comprehensive Error Handling
  • ✔︎ Developer-Friendly Docs
  • ✔︎ Postman Integration
  • ✔︎ Secure HTTPS Connections
  • ✔︎ Reliable Uptime

CT-e XML Schema Compliance API FAQs

The API returns a JSON response that includes a validity flag, a list of per-element errors (with paths and error codes), the auto-detected schema version, the document kind, and any municipality-specific warnings.

Key fields in the response include "valid" (boolean), "errors" (array of error objects), "schema_version" (string), "schema_kind" (string), and "municipality_specific_warnings" (array).

The response is structured as a JSON object with top-level keys for validity, errors, schema version, schema kind, and municipality warnings, allowing easy access to each component.

The API provides validation results for NF-e, NFC-e, and CT-e XML documents, including error details, schema version, and municipality-specific warnings, ensuring comprehensive validation feedback.

Data accuracy is maintained through daily monitoring of SEFAZ schema updates, ensuring that the API uses the most current validation rules and structures for NF-e, NFC-e, and CT-e documents.

Typical use cases include validating supplier NF-e before ledger import in ERP systems, pre-validating CT-e/NF-e during e-commerce checkout, and ensuring compliance in document-intake pipelines.

Users can utilize the returned data by checking the "valid" flag to determine if the XML is valid, reviewing the "errors" array for specific issues, and addressing any municipality-specific warnings for compliance.

Standard data patterns include a "valid" flag of true for valid documents, an empty "errors" array, and specific error codes like MISSING_REQUIRED or INVALID_FORMAT for invalid documents, providing clear feedback on issues.

General FAQs

To obtain your API key, you first need to sign in to your account and subscribe to the API you want to use. Once subscribed, go to your Profile, open the Subscription section, and select the specific API. Your API key will be available there and can be used to authenticate your requests.

You can’t switch APIs during the free trial. If you subscribe to a different API, your trial will end and the new subscription will start as a paid plan.

If you don’t cancel before the 7th day, your free trial will end automatically and your subscription will switch to a paid plan under the same plan you originally subscribed to, meaning you will be charged and gain access to the API calls included in that plan.

The free trial ends when you reach 50 API requests or after 7 days, whichever comes first. 

No, the free trial is available only once, so we recommend using it on the API that interests you the most. Most of our APIs offer a free trial, but some may not include this option.

 Yes, we offer a 7-day free trial that allows you to make up to 50 API calls at no cost, so you can test our APIs without any commitment. 

Zyla API Hub is like a big store for APIs, where you can find thousands of them all in one place. We also offer dedicated support and real-time monitoring of all APIs. Once you sign up, you can pick and choose which APIs you want to use. Just remember, each API needs its own subscription. But if you subscribe to multiple ones, you'll use the same key for all of them, making things easier for you.

Prices are listed in USD (United States Dollar), EUR (Euro), CAD (Canadian Dollar), AUD (Australian Dollar), and GBP (British Pound). We accept all major debit and credit cards. Our payment system uses the latest security technology and is powered by Stripe, one of the world's most reliable payment companies. If you have any trouble paying by card, just contact us at [email protected]

Additionally, if you already have an active subscription in any of these currencies (USD, EUR, CAD, AUD, GBP), that currency will remain for subsequent subscriptions. You can change the currency at any time as long as you don't have any active subscriptions.
The local currency shown on the pricing page is based on the country of your IP address and is provided for reference only. The actual prices are in USD (United States Dollar). When you make a payment, the charge will appear on your card statement in USD, even if you see the equivalent amount in your local currency on our website. This means you cannot pay directly with your local currency.
Occasionally, a bank may decline the charge due to its fraud protection settings. We suggest reaching out to your bank initially to check if they are blocking our charges. Also, you can access the Billing Portal and change the card associated to make the payment. If these does not work and you need further assistance, please contact our team at [email protected]
Prices are determined by a recurring monthly or yearly subscription, depending on the chosen plan.
API calls are deducted from your plan based on successful requests. Each plan comes with a specific number of calls that you can make per month. Only successful calls, indicated by a Status 200 response, will be counted against your total. This ensures that failed or incomplete requests do not impact your monthly quota.
Zyla API Hub works on a recurring monthly subscription system. Your billing cycle will start the day you purchase one of the paid plans, and it will renew the same day of the next month. So be aware to cancel your subscription beforehand if you want to avoid future charges.
To upgrade your current subscription plan, simply go to the pricing page of the API and select the plan you want to upgrade to. The upgrade will be instant, allowing you to immediately enjoy the features of the new plan. Please note that any remaining calls from your previous plan will not be carried over to the new plan, so be aware of this when upgrading. You will be charged the full amount of the new plan.
To check how many API calls you have left for the current month, refer to the 'X-Zyla-API-Calls-Monthly-Remaining' field in the response header. For example, if your plan allows 1,000 requests per month and you've used 100, this field in the response header will indicate 900 remaining calls.
To see the maximum number of API requests your plan allows, check the 'X-Zyla-RateLimit-Limit' response header. For instance, if your plan includes 1,000 requests per month, this header will display 1,000.
The 'X-Zyla-RateLimit-Reset' header shows the number of seconds until your rate limit resets. This tells you when your request count will start fresh. For example, if it displays 3,600, it means 3,600 seconds are left until the limit resets.
Yes, you can cancel your plan anytime by going to your account and selecting the cancellation option on the Billing page. Please note that upgrades, downgrades, and cancellations take effect immediately. Additionally, upon cancellation, you will no longer have access to the service, even if you have remaining calls left in your quota.
After 7 days, you will be charged the full amount for the plan you were subscribed to during the trial. Therefore, it's important to cancel before the trial period ends. Refund requests for forgetting to cancel on time are not accepted.
When you subscribe to an API free trial, you can make up to 50 API calls. If you wish to make additional API calls beyond this limit, the API will prompt you to perform an "Start Your Paid Plan." You can find the "Start Your Paid Plan" button in your profile under Subscription -> Choose the API you are subscribed to -> Pricing tab.
Payout Orders are processed between the 20th and the 30th of each month. If you submit your request before the 20th, your payment will be processed within this timeframe.
You can contact us through our chat channel to receive immediate assistance. We are always online from 8 am to 5 pm (EST). If you reach us after that time, we will get back to you as soon as possible. Additionally, you can contact us via email at [email protected]

Please have a look at our Refund Policy: https://zylalabs.com/terms#refund


Related APIs