Bolivia SIAT e-Invoice Validator API - SFV

API ID 13426

Keyless Bolivia SFV/SIAT factura electronica validator: official SIN XSD, code ranges, totals math, CUF/CUFD reconstruction with Modulo 11 and Base16, XML-DSig signature check. Rule-coded JSON report.

280 ms avg response

API Documentation

Endpoints

Request
Simple liveness probe for monitoring and uptime checks. Returns {"status":"ok"} with HTTP 200 when the validation service is up and ready to accept documents. No parameters, no body required.
Endpoint ID: 29085
GET https://zylalabs.com/api/13426/bolivia+siat+e-invoice+validator+api+-+sfv/29085/health+check
INPUT PARAMETERS

Free test requests remaining: 3 of 3.

This endpoint does not require any input parameters.

API EXAMPLE RESPONSE
JSON
{
    "status": "ok"
}
Health check — CODE SNIPPETS

curl --location --request GET 'https://zylalabs.com/api/13426/bolivia+siat+e-invoice+validator+api+-+sfv/29085/health+check' --header 'Authorization: Bearer YOUR_API_KEY' 


    
Request
POST the raw factura electronica XML as the request body (Content-Type: application/xml). Returns a JSON validation report: valid, wellFormed, documentType, signatureValid, errorCount, warningCount and detailed rule-coded findings (BO-STRUCT-*, BO-CODE-*, BO-CUF-*, BO-MATH-*, BO-SIG-*) covering the official SIN XSDs, SIN parametric code ranges, the CUF control code rebuilt from the invoice header via the SIN Modulo 11 algorithm and Base16 encoding (CUFD recovered), totals math per Validaciones por Documento Sector, and the enveloped XML-DSig signature. A non-compliant invoice is still HTTP 200 - the verdict is "valid": false inside the JSON.
Endpoint ID: 29086
POST https://zylalabs.com/api/13426/bolivia+siat+e-invoice+validator+api+-+sfv/29086/validate+e-invoice
INPUT PARAMETERS

Validate e-invoice — Endpoint Features

Object Description
Request Body Required Json

Free test requests remaining: 3 of 3.


INPUT PARAMETERS

API EXAMPLE RESPONSE
JSON
{
    "valid": true,
    "wellFormed": true,
    "inputFormat": "xml",
    "documentType": "facturaElectronicaCompraVenta",
    "version": "1.0",
    "signatureValid": false,
    "errorCount": 0,
    "warningCount": 2,
    "findings": [
        {
            "level": "info",
            "ruleId": "BO-STRUCT-XSD",
            "text": "Document is valid against the official SIN facturaElectronicaCompraVenta XSD (ver. 23/08/2021).",
            "location": null,
            "occurrences": 1
        },
        {
            "level": "info",
            "ruleId": "BO-CUF-VERIFY",
            "text": "CUF VERIFIES: its Base16 prefix reproduces from the header via the SIN Modulo 11 self-check digit (modalidad=1, tipoEmision=1, tipoFactura=1); recovered CUFD control code = '67A75AC82F24C74'.",
            "location": "cabecera/cuf",
            "occurrences": 1
        },
        {
            "level": "warning",
            "ruleId": "BO-SIG-CERT-PARSE",
            "text": "Could not parse the embedded X.509 certificate: Could not parse certificate: java.io.IOException: Empty input",
            "location": "ds:X509Certificate",
            "occurrences": 1
        },
        {
            "level": "warning",
            "ruleId": "BO-SIG-DOC-DIGEST",
            "text": "Document digest MISMATCH: signed DigestValue WmFvnKBZIr9D37PaYuxM3aoXVu9nDZT+2MI1I+RUh8s= does not match the recomputed SHA-256 (inclusive z8Unw8lbp8Ab+GEUWpu5rdX0nY4y4HwiQBKb5yXdf0Y= / exclusive z8Unw8lbp8Ab+GEUWpu5rdX0nY4y4HwiQBKb5yXdf0Y=). The document content differs from what was signed, or a different canonicalization was used (the official SIN example ships a placeholder DigestValue and will land here).",
            "location": "ds:Reference[@URI='']",
            "occurrences": 1
        },
        {
            "level": "info",
            "ruleId": "BO-SIG-TRUST",
            "text": "Trust chain to a Bolivia digital-signature certification authority (the ADSIB / Entidad Certificadora hierarchy recognised for firma digital) is NOT verified here; that requires the national CA/root list and, for full assurance, an online revocation (CRL/OCSP) check. Structure and the embedded-certificate crypto are checked offline.",
            "location": null,
            "occurrences": 1
        }
    ]
}
Validate e-invoice — CODE SNIPPETS

curl --location --request POST 'https://zylalabs.com/api/13426/bolivia+siat+e-invoice+validator+api+-+sfv/29086/validate+e-invoice' --header 'Authorization: Bearer YOUR_API_KEY' 

--data-raw '
    
        1003579028
        Carlos Loza
        La Paz
        2846005
        1
        44AAEC00DBD34C819B4D7AFD5F91900D3A059E06A467A75AC82F24C74
        BQUE+QytqQUDBKVUFOSVRPQkxVRFZNVFVJBMDAwMDAwM
        0
        AV. JORGE LOPEZ #123
        
        2021-10-07T09:01:24.178
        Mi razon social
        1
        5115889
        
        51158891
        1
        
        99
        99
        1
        1
        99
        
        1
        
        
        Ley N° 453: Tienes derecho a recibir información sobre las características y contenidos de los
            servicios que utilices.
        
        pperez
        1
    
    
        451010
        49111
        JN-131231
        JUGO DE NARANJA EN VASO
        1
        1
        100
        0
        100
        124548
        545454
    
    
        
            
            
            
                
                    
                    
                
                
                WmFvnKBZIr9D37PaYuxM3aoXVu9nDZT+2MI1I+RUh8s=
            
        
        
            itb123fGGhh12DpFDFas34ASDAPpSSSSadasDasAS1smkRsj5ksdjasd8asdkasjd8asdkas8asdk21v
            a1qf+kBKLwF39mj+5zKo1qf+kBKLD42qD/+yxSMMS6DM5SywPxO1oyjnSZtObIe/45fdS4sE9+aNOn
            UncYUlSDAPpSSSSadasgIMWwlX2XMJ4SDAPpSSSSadas6qihJt/3dEIdta1RETSDAPpSSSSadas9S2W
            ALbT3VV8pjLqikVLcSDAPpSSSSadaseCKG8abcdssM0Wm8p+5grNNpSDAPpSSSSadasy4TvT4C3xS
            70zSbKWeBUUglRcU8FECEcacu+UJaBCgRW0S3Q==
        
        
            
                
                    TIIEuzCCZ7OgZIZsdZsDSZDSsdZsdSZSDZSDZKoZIhvcNZQEZBQZgbUxCzZZBgNVBZYTZkZ
                    TIIEuzCCZ7OgZIZsdZsDSZDSsdZsdSZSDZSDZKoZIhvcNZQEZBQZgbUxCzZZBgNVBZYTZkZ
                    bnRhbTlsbGZZZ1dVzdG9zLTdvYi5ibzCCZSIDQYZKoZIhvcNZQEBBQZDgasdaACZQoCggEB
                    TIIEuzCCZ7OgZIZsdZsDSZDSsdZsdSZSDZSDZKoZIhvcNZQEZBQZgbUxCzZZBgNVBZYTZkZ
                    bnRhbTlsbGZZZ1dVzdG9zLTdvYi5ibzCCZSIDQYZKoZIhvcNZQEBBQZDgasdaACZQoCggEB
                    TIIEuzCCZ7OgZIZsdZsDSZDSsdZsdSZSDZSDZKoZIhvcNZQEZBQZgbUxCzZZBgNVBZYTZkZ
                    bnRhbTlsbGZZZ1dVzdG9zLTdvYi5ibzCCZSIDQYZKoZIhvcNZQEBBQZDgasdaACZQoCggEB
                    k/IsZZEBEETRTEQYDVQQZEoxTDZzNTc5TDI4TTITZYZKoZIhvcNZQkBZiNhcT5vbGQucXVp
                    bnRhbTlsbGZZZ1dVzdG9zLTdvYi5ibzCCZSIDQYZKoZIhvcNZQEBBQZDgasdaACZQoCggEB
                    bnRhbTlsbGZZZ1dVzdG9zLTdvYi5ibzCCZSIDQYZKoZIhvcNZQEBBQZDgasdaACZQoCggEB
                    kTIh+T9dIRZ9GghiSZbP2Zk082ycgic2ZepdZLu7p2LEUZUhTXSXGZQkO4o/ZNZZk0ZQKgi
                    bnRhbTlsbGZZZ1dVzdG9zLTdvYi5ibzCCZSIDQYZKoZIhvcNZQEBBQZDgasdaACZQoCggEB
                    V8ZVyTkIDRCTcBYZO4ZZ8oV1UTbQEiDZZOYTZDHT2ZRy+kS+OzCdpZZKZZyds0ZClCZRlTg
                    bnRhbTlsbGZZZ1dVzdG9zLTdvYi5ibzCCZSIDQYZKoZIhvcNZQEBBQZDgasdaACZQoCggEB
                    Z1UdDQEZIE8DZuBgNVHREEZzZlhiNhcT5vZZZXVpbnRhbTlsbGZZZ1dVzdG9zLTdvYi5i7Z
                    bzBRBgNVHR8ESZBITEZgRKBChkBodHRczovL2Rlc2ZycT9sbG8uYRzZIuZ29iLTZvL2Rlc2
                    bnRhbTlsbGZZZ1dVzdG9zLTdvYi5ibzCCZSIDQYZKoZIhvcNZQEBBQZDgasdaACZQoCggEB
                    NRrZKQl3YhKZKRSZyeegVZIiXlYeEyOe5qdn3XdyTCDkz4bTn02KbcsnZP7oVTqsodBSd0B
                    ptrxqoqeZHhGBzEl5/vxDS/Sx4eO7ZXd1T4HtZntETdsZXZuPZZt4Vr57R/hqdZeTkk7uO9
                    bnRhbTlsbGZZZ1dVzdG9zLTdvYi5ibzCCZSIDQYZKoZIhvcNZQEBBQZDgasdaACZQoCggEB
                    YB+PC1LO7gnh4Zz9UsYb0YBG
                
            
        
    
'

    

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 Bolivia SIAT e-Invoice Validator API - SFV 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.

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

(Save 2 months with annual billing 🎉)

🚀 Enterprise Plan

Starts at
$ 10,000/Year


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

Overview

Keyless Bolivia SFV/SIAT factura electronica validator: official SIN XSD, code ranges, totals math, CUF/CUFD reconstruction with Modulo 11 and Base16, XML-DSig signature check. Rule-coded JSON report.

Bolivia SIAT e-Invoice Validator API - SFV FAQs

The GET Health check endpoint returns a simple JSON object indicating the service status. The POST Validate e-invoice endpoint returns a detailed JSON validation report, including fields like "valid," "wellFormed," "documentType," and findings related to structure, code verification, and signature validity.

Key fields in the POST Validate e-invoice response include "valid" (boolean), "wellFormed" (boolean), "documentType" (string), "signatureValid" (boolean), "errorCount" (integer), "warningCount" (integer), and "findings" (array of detailed validation results).

The response data is structured in a JSON format. It includes a top-level object with validation status fields, followed by an array of "findings" that detail specific validation results, categorized by level (info, warning, error) and rule ID.

The GET Health check provides service status. The POST Validate e-invoice offers comprehensive validation results for electronic invoices, including compliance with official SIN XSDs, CUF verification, and signature checks, along with detailed findings.

Data accuracy is maintained through adherence to official SIN XSD standards and validation rules. The API checks invoice structure, code ranges, and signature validity, ensuring compliance with established regulations and algorithms like Modulo 11.

Typical use cases include validating electronic invoices for compliance with Bolivian tax regulations, ensuring proper formatting and structure, and verifying the authenticity of invoices through signature checks and CUF validation.

Users can utilize the returned data by checking the "valid" field to determine invoice compliance. They can also review "findings" for specific issues, such as structure or signature problems, allowing for targeted corrections before resubmission.

Standard data patterns include a boolean "valid" field indicating compliance, a "wellFormed" field confirming XML structure, and an array of "findings" that detail validation results. Users can expect a mix of informational messages and warnings based on the invoice's compliance status.

General FAQs

To obtain your API key, first sign in to your account and navigate to the API you want to use. From the API's Pricing section, choose a plan and complete the subscription process. Once subscribed, return to the API page and you will see your API Access Key displayed at the top of the documentation page. You can use this key 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.

The free trial lasts for 7 days and allows you to make up to 50 API requests.

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. If the API offers a free trial, you will see a "Free 7-Day Trial" option in its Pricing section. The trial lasts for 7 days and allows up to 50 API requests, enabling you to evaluate the API before subscribing to a paid plan.

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.

You can monitor your API usage through the response headers included with every request:

x-zyla-api-calls-monthly-used: Shows the total number of API requests you have used during the current billing period.
x-zyla-api-calls-monthly-remaining: Shows the number of API requests you have remaining for the current billing period.

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 subscription at any time. Simply go to the Pricing section of the API you're subscribed to and click the "Unsubscribe" button.

Please note that upgrades, downgrades, and cancellations take effect immediately. Once your subscription is canceled, access to the service will end immediately, regardless of any remaining API calls 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.
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