Paraguay RUC Lookup API: Confirm a Taxpayer Name and Full RUC

Updated November 2026

This guide shows how to look up a company in Paraguay by RUC with Verifik’s API: the endpoint, its parameters, a request you can paste into a terminal, the documented response and errors, and what to watch for when you put it in production. Everything below comes from the official endpoint documentation.

Company records in Paraguay

Paraguay’s Registro Único del Contribuyente (RUC) is managed by the Dirección Nacional de Ingresos Tributarios (DNIT), which took over from the former Subsecretaría de Estado de Tributación (SET). For individuals the RUC is the cédula number plus a check digit; companies receive a number starting with 80.

Verifik’s endpoint takes the RUC without the check digit and returns the registered name and the full RUC including the digit.

If the use case is clear, create an account and test the endpoint from your own code.

How to call the Paraguay RUC API

Endpoint: GET https://api.verifik.co/v2/py/company. Send your token in the Authorization: Bearer header. Parameters, as documented:

Request example with placeholder values (replace them with your user’s data):

curl --location --request GET 'https://api.verifik.co/v2/py/company?documentType=RUC&documentNumber=80012345' \
--header 'Accept: application/json' \
--header 'Authorization: Bearer <token>'

200 response from the docs (personal data masked):

{
  "data": {
    "businessName": "EMPRESA EJEMPLO S.A.",
    "documentNumber": "80012345",
    "documentType": "RUC",
    "fullRUC": "80012345-6"
  },
  "signature": {
    "dateTime": "October 10, 2025 5:32 PM",
    "message": "Certified by Verifik.co"
  },
  "id": "NI85Y"
}

A successful call returns HTTP 200 with a data object containing: businessName, documentNumber, documentType, fullRUC. Every response also carries a signature (timestamp and “Certified by Verifik.co”) and a unique id you can store as evidence of the check.

Documented errors for /v2/py/company

• 401 UNAUTHORIZED (“Authentication required”): the token is missing or invalid; check the Authorization header.
• 404 NotFound (“Record not found”): no record was found; do not treat it as a match and route the case to review or ask for another document.
• 409 MissingParameter (“documentType must be one of: [RUC]”): a required parameter is missing or has an invalid value; fix the request instead of retrying it as is.
• 500 InternalServerError (“Server error”): a server or source error; retry with backoff and log the request id.

Integration tips

• Send the RUC body without the check digit; the response returns fullRUC with it.
• A RUC that does not start with 80 usually belongs to an individual; check whether that is expected.
• documentType must be RUC.
• For individuals, pair this with the Paraguay CIC check to confirm the person behind the RUC.

Personal data and terms of use

Company records can include personal data about partners, officers or representatives. Use the API only for a lawful purpose you can document, such as onboarding, fraud prevention or contract checks, collect consent where the local law requires it, and keep only the fields you need. Usage is governed by the smartCHECK terms and conditions.

Pricing

Each successful request consumes credits from your Verifik plan. Current plans and per-endpoint costs are on the smartCHECK pricing page.

Related guides and documentation

• Paraguay CIC verification API
• Bolivia NIT company lookup API
• Endpoint documentation (English)
• Documentation in Spanish

Start testing

Create a Verifik account to get your API token, or book a meeting if you want to review coverage and volumes with the team.