FUEC expedidos

GET

/fuec

curl --request GET \
  --url 'https://api.notiauto.co/v1/fuec?state=active&per_page=20' \
  --header 'X-API-Key: <X-API-Key>'

• Producción

Requiere el scope fuec.read. Los más recientes primero. Como el resto de listados, data es el paginador: los FUEC vienen en data.data.

Authorizations

• ApiKey

Parameters

Query Parameters

state

string

Allowed values: active upcoming expired voided

plate

string

contract

string format: uuid

Id (uuid) del contrato

per_page

integer

default: 20 <= 100

Responses

200

Listado paginado

Media typeapplication/json

object

success

boolean

data

object

data

Array<object>

FuecExtract

Un FUEC tal como se expidió (lo que imprime su PDF).

object

id

string format: uuid

number

21 dígitos (Res. 6652, art. 4)

string

formatted_number

string

state

string

Allowed values: active upcoming expired voided

starts_on

string format: date

ends_on

string format: date

issued_at

string format: date-time

issued_by

string

nullable

channel

string

Allowed values: web api

verification_code

El código del QR

string

verification_url

Página pública de verificación (lo que abre el QR)

string format: uri

pdf_url

string format: uri

contract

object

id

string format: uuid

nullable

number

integer

contractor_name

string

contractor_document

string

purpose

string

origin_destination

string

vehicle

object

plate

string

brand

string

nullable

line

string

nullable

model

string

nullable

class

string

nullable

internal_number

string

nullable

operation_card

string

nullable

drivers

Array<object>

object

name

string

document

string

license_number

string

nullable

license_category

string

nullable

license_expires_on

string format: date

nullable

warnings

Avisos aceptados al expedir

Array<object>

FuecCheck

Una línea de la revisión de documentos. code identifica el resultado (p. ej. soat.expired, license.not_qualified, rcc.unknown).

object

subject

Top-level OpenAPI document: info, servers, the API-key scheme, shared schemas and the endpoints that live in routes/api.php as closures rather than on a controller.

Everything here describes what the code actually returns, including the paginator-inside-data shape of the list endpoints — that is the published contract and consumers depend on it.

string

Allowed values: vehicle driver

subject_id

integer

label

Placa o nombre del conductor

string

key

string

status

string

Allowed values: ok warn block

code

string

params

object

voided_at

string format: date-time

nullable

void_reason

string

nullable

meta

PaginationMeta

object

current_page

integer

total

integer

per_page

integer

last_page

integer

Example

{
  "success": true,
  "data": {
    "data": [
      {
        "number": "425015512202602550001",
        "formatted_number": "425 0155 12 2026 0255 0001",
        "state": "active",
        "channel": "web",
        "verification_code": "K7QW2M9XRT",
        "warnings": [
          {
            "subject": "vehicle",
            "subject_id": 1534,
            "label": "TLN810",
            "key": "soat",
            "status": "ok",
            "code": "soat.expires_during",
            "params": {
              "date": "2026-11-15"
            }
          }
        ]
      }
    ]
  },
  "meta": {
    "current_page": 1,
    "total": 42,
    "per_page": 20,
    "last_page": 3
  }
}

403

Sin el scope o el plan no trae el FUEC

Media typeapplication/json

Error

object

success

boolean

message

string

Example

{
  "success": false,
  "message": "API key inválida o expirada."
}