Skip to main content

DGII 60 — DGII token invalid or expired

Token DGII inválido o expirado

FieldValue
DGII code60
CategoryInternal
HTTP status401
RetryableYes
Tenant fixableNo
Problem.typehttps://errors.api.erply.pro/dgii-60-token-invalido
Pending details

This entry is partially documented. Please contact us via /docs/support if you encounter this code in production so we can prioritise it.

Probable cause

DGII rejected the e-CF with code 60 in the Internal category.

How to fix

  1. Review the detail field of the received Problem for more context.
  2. Verify the payload against the published OpenAPI schema.
  3. If the error persists, open a ticket at /docs/support including the correlationId and dgii.trackId.

Example application/problem+json response

{
"type": "https://errors.api.erply.pro/dgii-60-token-invalido",
"title": "DGII token invalid or expired",
"status": 401,
"detail": "DGII code 60: DGII token invalid or expired",
"instance": "/v1/invoices",
"correlationId": "1-65fa7c3a-6f9c2d8e0a1b2c3d4e5f6789",
"dgii": {
"code": "60",
"trackId": "20260501-DGII-9988"
}
}

Source

DGII PSFE Technical Spec + Norma 06-04. Exact citation pending review by the compliance specialist.