1. Inicio
  2. Documentos
  3. NS BPe (English)
  4. BPe Events
  5. Luggage Excess

Luggage Excess

Through the excess baggage charge event service, it is possible to inform the excess baggage charge at the BP-e.

Note: This event has rules and deadlines defined by the Secretariat of Finance that must be considered and respected. For more information click here and check the most up-to-date version of the Sefaz Taxpayer Guidance Manual.


Production: POST https://bpe.ns.eti.br/v1/bpe/excessobag

Input Data
FieldDescriptionOccurrenceData TypeSizeNotes
X-AUTH-TOKENSoftware Access Token0-1StringCan also be sent in the request header
chBPeBP-e access key1-1Int44
tpAmbType of BP-e authorization environment:
1 - Production,
2 - Approval
dhEventoDate and time the event occurred1-1String ( date and time format )25Sefaz Standard:
Ex .: 2016-06-13T15: 04:10-02:00
nProtBP-e authorization protocol number1-1Int15
qBagagemNumber of luggage volumes loaded1-1Int20
vTotBagTotal value of the service1-1Int13 + 2 decimals ( Ex: 9999999999999,99
Request Example
Luggage Excess Request Event
curl -X POST \
-H "Content-Type: application/json" \
-d '{
      "tpAmb": "2", 
      "dhEvento": "2020-08-19T17:32:00-03:00", 
      "nProt": "143200000264094", 
      "qBagagem": "10", 
      "vTotBag": "10000.00"
Returned Data
FiledDescriptionData TypeParentNotes
statusProcessing status codeInt
motivoLiteral description of processing statusString
retEventoObject containing the cancellation processing data at SefazObjectOnly when status = 200
cStatProcessing status codeIntretEvento
xMotivoLiteral description of the processing situation at SefazStringretEvento
chBPeBP-e access keyIntretEventoOnly with cStat = 135
dhRegEventoDate and time of the event registration at SefazString ( date and time format )retEventoSefaz Standard: YYYY-MM-DDTHH: MM: SS + UTC.
Ex .: 2016-06-13T15: 04:10-03:00
Only in cStat = 135
nProtEvent authorization protocol numberIntretEventoOnly with cStat = 135
xmlEvent distribution XMLStringretEventoOnly with cStat = 135
Object containing the error information in case the cancellation cannot be carried out successfully
ObjectOnly when status is different than 200
cStatError status codeInterro
xMotivoLiteral description of the errorStringerro
Response Examples

Successful Response

    "status": 200,
    "motivo": "Processamento de evento realizado com sucesso",
    "retEvento": {
        "cStat": 135,
        "xMotivo": "Evento registrado e vinculado a BP-e",
        "chBPe": "43180207364617000135630000000000301000000081",
        "dhRegEvento": "2018-02-21T14:58:46-03:00",
        "nProt": "143180000002623",
        "xml": "<?xml version=\"1.0\" encoding=\"utf-8\"?><procEventoBPe versao=\"1.00\" xmlns=\"http://www.portalfiscal.inf.br/bpe\">...</procEventoBPe>"
Returned Codes
200Successfully linked event
-2Invalid access key
-3The event could not be linked. Check the error object for more information
Luggage Excess Event Download

You can download the complete event distribution information in XML or JSON. To do this, check the Download Events method in the NS BP-e API.

Como podemos ajudar?