Expedir un FUEC

POST

/fuec

const url = 'https://api.notiauto.co/v1/fuec';
const options = {
  method: 'POST',
  headers: {'X-API-Key': '<X-API-Key>', 'Content-Type': 'application/json'},
  body: '{"contract":"2489E9AD-2EE2-8E00-8EC9-32D5F69181C0","plate":"TLN810","drivers":["80218874"],"starts_on":"2026-04-15","ends_on":"2026-04-15","internal_number":"example","accept_warnings":false}'
};

try {
  const response = await fetch(url, options);
  const data = await response.json();
  console.log(data);
} catch (error) {
  console.error(error);
}

curl --request POST \
  --url https://api.notiauto.co/v1/fuec \
  --header 'Content-Type: application/json' \
  --header 'X-API-Key: <X-API-Key>' \
  --data '{ "contract": "2489E9AD-2EE2-8E00-8EC9-32D5F69181C0", "plate": "TLN810", "drivers": [ "80218874" ], "starts_on": "2026-04-15", "ends_on": "2026-04-15", "internal_number": "example", "accept_warnings": false }'

Requiere el scope fuec.write. Revisa los documentos con lo que reportó el RUNT (SOAT, revisión técnico-mecánica, pólizas RCC/RCE, tarjeta de operación, licencia de la categoría) y, si nada lo impide, numera y congela el FUEC. Si hay avisos (algo vence en medio del periodo), exige accept_warnings: true. Dispara el webhook fuec.issued.

Authorizations

ApiKey

Request Body^required

application/json

FuecIssueInput

object

contract

required

Id (uuid) del contrato

string format: uuid

plate

required

Placa de un vehículo registrado en la flota (sin terceros)

string

Example

TLN810

drivers

required

Documentos de 1 a 3 conductores registrados en la flota, en orden

Array<string>

Example

[
  "80218874"
]

starts_on

required

Desde hoy en adelante, dentro del contrato

string format: date

ends_on

required

Hasta el fin del contrato como máximo

string format: date

internal_number

Número interno del vehículo en la empresa; se guarda para los siguientes

string

nullable <= 20 characters

accept_warnings

Obligatorio en true si la revisión trae avisos (algo vence en medio)

boolean

Responses

201

Expedido

application/json

object

success

boolean

data

FuecExtract

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

object

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

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

Example

{
  "success": true,
  "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"
        }
      }
    ]
  }
}

403

El plan no trae el FUEC o la expedición ya se hace en el RUNT

application/json

Error

object

success

boolean

message

string

Example

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

422

Datos inválidos, faltan los datos de la empresa, o la revisión lo impide o trae avisos sin aceptar. En los dos últimos casos la respuesta trae readiness con el detalle.

application/json

object

message

string

errors

object

readiness

FuecReadiness

Si el vehículo y los conductores pueden salir con un FUEC en esas fechas, según lo que reportó el RUNT. block impide expedir; warn exige accept_warnings.

object

blocked

boolean

checks

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

warnings

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

suggested_ends_on

Último día en que todo sigue vigente, si algo vence en medio

string format: date

nullable

required_category

Licencia que exige el vehículo

string

nullable

Example

{
  "readiness": {
    "blocked": false,
    "checks": [
      {
        "subject": "vehicle",
        "subject_id": 1534,
        "label": "TLN810",
        "key": "soat",
        "status": "ok",
        "code": "soat.expires_during",
        "params": {
          "date": "2026-11-15"
        }
      }
    ],
    "warnings": [
      {
        "subject": "vehicle",
        "subject_id": 1534,
        "label": "TLN810",
        "key": "soat",
        "status": "ok",
        "code": "soat.expires_during",
        "params": {
          "date": "2026-11-15"
        }
      }
    ],
    "required_category": "C1"
  }
}

Expedir un FUEC

Authorizations

Request Bodyrequired

Example

Example

Responses

201

Example

403

Example

422

Example

Request Body^required