1. Inicio
  2. Documentos
  3. NS BPe (English)
  4. BPe Events
  5. Seat Change

Seat Change

Through this endpoint it is possible to change the seat / armchair / cabin without changing the values ​​or date of departure of a ticket previously authorized through the API.


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

Input Data
FieldDescriptionOccurrenceData TypeNotes
X-AUTH-TOKENSoftware house access token0-1StringCan also be sent in the request header
chBPeBP-e access key1-1Int
tpAmbType of BP-e authorization environment,
1 - Production,
2 - Approval
dhEventoEvent date and time1-1String ( date and time format )Sefaz Standard: YYYY-MM-DDTHH: MM: SS + UTC.
Ex.: 2016-06-13T15: 04: 10-02: 00
nProtBP-e authorization protocol number1-1Int
poltronaNumber of the new BP-e armchair / seat / cabin1-1Int
Request Example

Seat Change Request Example

curl -X POST \
-H "Content-Type: application/json" \
-d '{
      "chBPe": "99999999999999999999999999999999999999999999", 
      "tpAmb": 2, 
      "dhEvento": "2017-05-15T12:00:00-03:00", 
      "nProt": "999999999999999", 
      "poltrona": "2"
Returned Data
FieldDescriptionData TypeParent Notes
statusStatus codeInt
motivoLiteral description of processing statusString
retEventoObject containing the cancellation processing data at SefazObjectOnly in status = 200
cStatProcessing status codeIntretEvento
xMotivoLiteral description of the processing situation at SefazStringretEvento
chBPeBP-e access keyIntretEventoOnly when 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
nProtNúmero do protocolo de autorização do eventoIntretEventoOnly when cStat = 135
xmlXML de distribuição do evento de cancelamentoStringretEventoOnly when cStat = 135
erroObject containing the error information in case the cancellation cannot be carried out successfullyObjectOnly in different than 200
cStatError status codeInterro
xMotivoLiteral description of the errorStringerro
Response Example

Successful Response

    "status": 200,
    "motivo": "Processamento de evento realizado com sucesso",
    "retEvento": {
        "cStat": 135,
        "xMotivo": "Evento registrado e vinculado a BP-e",
        "chBPe": "99999999999999999999999999999999999999999999",
        "dhRegEvento": "2018-02-21T14:58:46-03:00",
        "nProt": "999999999999999",
        "xml": "<?xml version=\"1.0\" encoding=\"utf-8\"?><procEventoBPe versao=\"1.00\" xmlns=\"http://www.portalfiscal.inf.br/bpe\">...</procEventoBPe>"
Retuned Codes
200Successful event processing
-2Invalid access key
-3It was not possible to link the event to BP-e. Check the error object for more information

Como podemos ajudar?