1
We are trying to use eSocial BX to get some information about events sent.
For the call ConsultarIdentificadoresEventosTrabalhador
the following XML is sent (I removed the signature part):
<?xml version='1.0' encoding='utf-8'?>
<soap-env:Envelope
xmlns:soap-env="http://schemas.xmlsoap.org/soap/envelope/">
<soap-env:Header
xmlns:wsa="http://www.w3.org/2005/08/addressing">
<wsa:Action>http://www.esocial.gov.br/servicos/empregador/consulta/identificadores-eventos/v1_0_0/ServicoConsultarIdentificadoresEventos/ConsultarIdentificadoresEventosTrabalhador</wsa:Action>
<wsa:MessageID>urn:uuid:73b1c7f5-ec50-465a-8e27-06f36cd55692</wsa:MessageID>
<wsa:To>https://webservices.producaorestrita.esocial.gov.br/servicos/empregador/dwlcirurgico/WsConsultarIdentificadoresEventos.svc</wsa:To>
</soap-env:Header>
<soap-env:Body>
<ns0:ConsultarIdentificadoresEventosTrabalhador xmlns:ns0="http://www.esocial.gov.br/servicos/empregador/consulta/identificadores-eventos/v1_0_0">
<ns0:consultaEventosTrabalhador xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="ns0:ConsultarIdentificadoresEventosTrabalhador">
<ns0:consultaEventosTrabalhador>
<eSocial xmlns="http://www.esocial.gov.br/schema/consulta/identificadores-eventos/trabalhador/v1_0_0">
<consultaIdentificadoresEvts>
<ideEmpregador>
<tpInsc>1</tpInsc>
<nrInsc>12345678</nrInsc>
</ideEmpregador>
<consultaEvtsTrabalhador>
<cpfTrab>12345678900</cpfTrab>
<dtIni>2019-03-10T00:00:00</dtIni>
<dtFim>2019-04-10T23:59:59</dtFim>
</consultaEvtsTrabalhador>
</consultaIdentificadoresEvts>
</eSocial>
</ns0:consultaEventosTrabalhador>
</ns0:consultaEventosTrabalhador>
</ns0:ConsultarIdentificadoresEventosTrabalhador>
</soap-env:Body>
</soap-env:Envelope>
And the return is as follows:
<?xml version="1.0" encoding="UTF-8"?><eSocial xmlns="http://www.esocial.gov.br/schema/consulta/identificadores-eventos/retorno/v1_0_0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:s="http://schemas.xmlsoap.org/soap/envelope/">
<retornoConsultaIdentificadoresEvts>
<status>
<cdResposta>417</cdResposta>
<descResposta>Erro na estrutura da solicitação. targetNamespace inválido.</descResposta>
</status>
</retornoConsultaIdentificadoresEvts>
</eSocial>
Has anyone ever been through this? The same happens in other consultations of this service. We have already tried to contact eSocial support, but unfortunately we did not get a conclusive answer.
In the search here at Stackoverflow I found only problems related to the signature eSocialBX: Invalid signature error.
The error was in tag duplication
consultaEventosTrabalhador
. Fixed this, the system accepted the request and returned the event Ids.– alexdemari