1. Inicio
  2. Documentos
  3. NS NFe (English)
  4. Events
  5. NFe Correction Letter

NFe Correction Letter

Through the NF-e Correction Letter service, it’s possible to link a descriptive event of correction of information contained in the authorized NF-e.

Obs.: CC-e and CC are acronyms in portuguese for Correction Letter.


Production: POST https://nfe.ns.eti.br/nfe/cce

Input data
X-AUTH-TOKENUser access token1-1
chNFeNF-e access key1-1
tpAmbNF-e authorization environment type:
1 - Production
2 - Homologation
dhEventoDate and time of the correction1-1Sefaz Standard: YYYY-MM-DDTHH:MM:SS+UTC. E.g.: 2016-06-13T15:04:10-02:00
nSeqEventoEvent sequential number1-1Sequential of the event for the same type of event
The event author must number sequentially
xCorrecaoCorrection description to be carried out in the NF-e1-1E.g.: "VALIDADE DA LICENCA DE 01/09/2015 A 01/09/2016.".
Sefaz won't accept correction letters in english.
Translation: "License validity from DD/MM/YYYY to DD/MM/YYYY.".
Request example

NF-e CC-e request

curl -X POST \
    -H "Content-Type: application/json" \
    -d '{
         "X-AUTH-TOKEN": "YOUR_TOKEN", 
         "chNFe": "43161107364617000135550000000099461000094833", 
         "tpAmb": "2", 
         "dhEvento": "2016-11-28T19:06:14-02:00", 
         "nSeqEvento": "1", 
         "xCorrecao": "CC-e realizada para teste de integração"
Returned data
statusProcessing status code
motivoProcessing status literal description
retEventoObject containing the correction processing data at SefazOnly when status = 200
retEvento.cStatProcessing situation code
retEvento.xMotivoLiteral description of the processing situation at Sefaz
retEvento.chNFeNF-e access key
retEvento.dhRegEventoDate and time of event registration at SefazSefaz Standard: YYYY-MM-DDTHH:MM:SS+UTC. E.g.: 2016-06-13T15:04:10-02:00
retEvento.nProtSefaz authorization protocol number for the event
erroObject containing the error information in case the correction could not be carried out successfullyOnly when status is different from 200
erro.cStatError status code
erro.xMotivoError literal description
Return example

Successful return

  "status": 200,
  "motivo": "CC-e vinculada com sucesso",
  "retEvento": {
    "cStat": 135,
    "xMotivo": "Evento registrado e vinculado a NF-e",
    "chNFe": "43161107364617000135550000000099461000094833",
    "dhRegEvento": "2016-11-30T16:14:24-02:00",
    "nProt": "143160001515534"
Return codes
200CC-e linked successfully
-2Invalid access key
-3It was not possible to link the CC-e to the NF-e. Check the "erro" object for more information
Download the NF-e Correction Letter

You can download the complete CC-e event distribution information in XML or JSON and also a graphical representation of the same in PDF formar. For this, check the Event Download method in the NS NF-e API.

Como podemos ajudar?