Exposing Swagger/OpenAPI documentation is primarily a risk if your API has underlying security flaws, as it gives attackers a precise roadmap to find them.
Those detail every endpoint, parameter, and data model, making it easier to discover and exploit vulnerabilities like broken access control or injection points.
While a perfectly secure API mitigates the danger, protecting your documentation is a critical layer of defense that forces attackers to work without a map.
Severity: info
Fingerprint: 5733ddf49ff49cd12ec8532c2ec8532c2ec8532c2ec8532c2ec8532c2ec8532c
Public Swagger UI/API detected at path: /swagger/index.html
Exposing Swagger/OpenAPI documentation is primarily a risk if your API has underlying security flaws, as it gives attackers a precise roadmap to find them.
Those detail every endpoint, parameter, and data model, making it easier to discover and exploit vulnerabilities like broken access control or injection points.
While a perfectly secure API mitigates the danger, protecting your documentation is a critical layer of defense that forces attackers to work without a map.
Severity: info
Fingerprint: 5733ddf49ff49cd1aad035493b3b7350220f106cd625069a187bb674ce90f816
Public Swagger UI/API detected at path: /swagger/index.html - sample paths: GET / GET /ExternalNotification/AlterarStatusInadimplenteApropriacaoIndebita GET /ExternalNotification/InadimplenteBloqueio POST /Delinquency/InitialProcessing POST /PromotionalCode/DeletePromotionalList POST /PromotionalCode/InsertPromotionalList POST /PromotionalCode/UpdatePromotionalList PUT /Cache/Repopulate/AllPlansAsync PUT /Cache/Repopulate/AllSettingsByLatePaymentRuleSettings PUT /Cache/Repopulate/SearchAllLatePaymentRuleSettings PUT /Cache/Repopulate/SearchAllSettingsForUnauthorizedAppropriationSettings PUT /Cache/Repopulate/SearchAllUnauthorizedAppropriationSettings
Exposing Swagger/OpenAPI documentation is primarily a risk if your API has underlying security flaws, as it gives attackers a precise roadmap to find them.
Those detail every endpoint, parameter, and data model, making it easier to discover and exploit vulnerabilities like broken access control or injection points.
While a perfectly secure API mitigates the danger, protecting your documentation is a critical layer of defense that forces attackers to work without a map.
Severity: info
Fingerprint: 5733ddf49ff49cd1aad035496631fd7c9ff1ca3d3d86c1fd9621f7caf24848d0
Public Swagger UI/API detected at path: /swagger/index.html - sample paths:
GET /api/v1/orders/finished/document/{userDocument}
GET /api/v1/orders/reference-external-id/{referenceExternalId}
GET /api/v1/pedidos/Store/pedidos-processados/{orderId}
PATCH /api/v1/orders/reference-external-id
POST /api/v1/estorno
POST /api/v1/orders/return-orders
POST /api/v1/pedidos/Store/cancelar
POST /api/v1/pedidos/Store/csat/cadastro
POST /api/v1/pedidos/Store/nps/cadastro
POST /api/v1/pedidos/Store/pedido-entregue
Severity: info
Fingerprint: 5733ddf49ff49cd1aad035493b3a4c69a76b341fe7a162519f22336dc3038a45
Public Swagger UI/API detected at path: /swagger/index.html - sample paths:
GET /api/v1/pedidos/Store/pedidos-processados/{orderId}
POST /api/v1/estorno
POST /api/v1/pedidos/Store/cancelar
POST /api/v1/pedidos/Store/csat/cadastro
POST /api/v1/pedidos/Store/nps/cadastro
POST /api/v1/pedidos/Store/pedido-entregue
Exposing Swagger/OpenAPI documentation is primarily a risk if your API has underlying security flaws, as it gives attackers a precise roadmap to find them.
Those detail every endpoint, parameter, and data model, making it easier to discover and exploit vulnerabilities like broken access control or injection points.
While a perfectly secure API mitigates the danger, protecting your documentation is a critical layer of defense that forces attackers to work without a map.
Severity: info
Fingerprint: 5733ddf49ff49cd1aad03549211ff400fd07388c6e55c772cad05e8878fb733e
Public Swagger UI/API detected at path: /swagger/index.html - sample paths:
DELETE /BindPayment/v1/delete/{id}
DELETE /BindService/v1/delete/{id}
DELETE /BindTax/v1/delete/{id}
DELETE /RentalCycle/Omie/Payables/{installmentId}
DELETE /RentalCycle/Omie/Payments/{installmentId}
GET /
GET /BindConfiguration/v1/filter
GET /BindPayment/v1/filter
GET /BindService/v1/filter
GET /BindTax/v1/filter
GET /OmieConfiguration/Filter
GET /ProcessInstallment/Filter
GET /ProcessRentalCycle/Filter
GET /ProcessWebhook/Filter
GET /RentalCycle/Omie/Payments/CanRemoveOld/{installmentId}
GET /ServiceOrder/ExternalIntegration
GET /ServiceOrder/FaturamentoFilter
GET /UserIntegrationCode/GetById/{userId}
POST /BigQuery/v1/cancelar-recebebimento
POST /BigQuery/v1/excluir-contas-a-receber
POST /BigQuery/v1/lancar-recebebimento
POST /BindConfiguration/v1/create
POST /BindInvoice/v1/ResetInstallmentMexico/{installmentId}
POST /BindInvoice/v1/ResetPaymentMexico/{installmentId}
POST /BindPayment/v1/create
POST /BindService/v1/create
POST /BindTax/v1/create
POST /CheckingAccounting/Adt/{installmentId}
POST /CheckingAccounting/PaidGuarantee/{installmentId}
POST /Enqueue/CreatePayableRefundedUserWithdraw/{installmentId}
POST /Enqueue/CreatePayableRefundedUserWithdrawWithDate/{installmentId}
POST /Enqueue/InformPaidInstallmentMexico/{installmentId}
POST /Enqueue/LeaseTerminationAccountPayable/{installmentId}
POST /Enqueue/ModifyInstallmentMexico/{installmentId}
POST /Enqueue/ReconcileInstallment
POST /Enqueue/ReconcileInstallmentBatch
POST /Enqueue/ReconcileInstallmentDayToDay
POST /Enqueue/ReconcileInstallmentOperation
POST /Enqueue/RentalCycleFinalizationAccountPayable/{rentalCycleId}
POST /Enqueue/UserAbandonmentAccounting/{userId}
POST /Enqueue/UserAbandonmentCompensation/{installmentId}
POST /Enqueue/UserAbandonmentRefund/{userId}
POST /HangfireManager/RequeueInactiveJobs
POST /OmieConfiguration/InsertList
POST /OmieConfiguration/Upsert
POST /OmieWebhook/AccountsPayableWriteOff
POST /Receivables/Adt/EarlyPayment/{installmentId}
POST /Receivables/Adt/Withdraw/{installmentId}
POST /Receivables/Adt/{installmentId}
POST /RentalCycle/Omie/Payment
POST /ServiceOrder/ListSyncErp
POST /ServiceOrder/SyncErp/{parcelaId}
POST /ServiceOrder/SyncRemote
POST /User/IntegrateByInstallmentId
POST /User/IntegrateByInstallmentRentalCycleId
POST /User/IntegrateByUserId
POST /UserIntegrationCode/UpdateIntegrationCode
PUT /BindConfiguration/v1/update/{id}
PUT /BindPayment/v1/update/{id}
PUT /BindService/v1/update/{id}
PUT /BindTax/v1/update/{id}
Exposing Swagger/OpenAPI documentation is primarily a risk if your API has underlying security flaws, as it gives attackers a precise roadmap to find them.
Those detail every endpoint, parameter, and data model, making it easier to discover and exploit vulnerabilities like broken access control or injection points.
While a perfectly secure API mitigates the danger, protecting your documentation is a critical layer of defense that forces attackers to work without a map.
Severity: info
Fingerprint: 5733ddf49ff49cd12ec8532c2ec8532c2ec8532c2ec8532c2ec8532c2ec8532c
Public Swagger UI/API detected at path: /swagger/index.html
Severity: info
Fingerprint: 5733ddf49ff49cd1aad03549276be4eebcafd3a2aa78ab43449b80b2e8e244eb
Public Swagger UI/API detected at path: /swagger/index.html - sample paths:
GET /api/v1/ActuatorOrgan/get-all
GET /api/v1/ActuatorOrgan/{code}
GET /api/v1/CategoryActuatorOrgan/get-all
GET /api/v1/Dnit/ait-detalhes/{autoInfracaoCode}
GET /api/v1/Dnit/check-status-ticket
GET /api/v1/Dnit/indicate-ticket/{autoInfracaoCode}
GET /api/v1/Mexico/{plate}
GET /api/v1/PaymentBank/get-all
GET /api/v1/Senatran/Crawler/Status
GET /api/v1/Senatran/buscar-infracoes-detalhes-por-placa/{cnpj}/{placa}
GET /api/v1/Senatran/get-all-token
GET /api/v1/Senatran/get-detalhes-infracao/{cnpj}/{placa}/{chaveInfracao}
GET /api/v1/Senatran/get-detalhes-veiculo/{cnpj}/{placa}/{renavam}
GET /api/v1/Senatran/get-log-senatran/{veiculoId}
GET /api/v1/Senatran/get-veiculos-usuario/{cnpj}
GET /api/v1/Senatran/plate-stamping/{plate}/{qrCode}
GET /api/v1/Senatran/visualizar-boleto/{cnpj}/{placa}/{chaveInfracao}
GET /api/v1/Ticket/Efrotas/cnpj/{cnpj}
GET /api/v1/Ticket/Efrotas/vehicle/{vehicleId}
GET /api/v1/Ticket/files
GET /api/v1/Ticket/get-ticket-details/{ticketId}
GET /api/v1/Ticket/get-tickets-by-plate/{plate}
GET /api/v1/Ticket/notificate-changes
GET /api/v1/Ticket/ticket-brazil
GET /api/v1/TicketPayment/buscar-multas-vencer
GET /api/v1/TicketSignature/ticket-signature/unverified
GET /api/v1/TicketsConfiguration/get-all
GET /api/v1/TicketsConfiguration/{type}
PATCH /api/v1/Ticket/{ticketId}/exemptions
POST /api/v1/ActuatorOrgan/upsert
POST /api/v1/CategoryActuatorOrgan
POST /api/v1/Dnit/indicate-ticket-list
POST /api/v1/Dnit/update-status-list
POST /api/v1/Dnit/upsert-token
POST /api/v1/MailBatch/close-mail-batch
POST /api/v1/MailBatch/create-mail-batch-and-indicate
POST /api/v1/MailBatch/reproccess-mail-batch
POST /api/v1/MailBatch/update-indicaton-file
POST /api/v1/MailBatch/update-mail-batch-file
POST /api/v1/OcrProcess
POST /api/v1/PaymentBank/upsert
POST /api/v1/Regulatory/download-document-crlv
POST /api/v1/Regulatory/download-document-crlv-by-plate
POST /api/v1/Senatran/Crawler/Enable
POST /api/v1/Senatran/Crawler/Start
POST /api/v1/Senatran/Crawler/Stop
POST /api/v1/Senatran/buscar-multas-por-placa
POST /api/v1/Senatran/download-documento-crlv
POST /api/v1/Senatran/download-documento-crlv-por-placa
POST /api/v1/Senatran/gerar-token-senatran/{code}
POST /api/v1/Senatran/reconhecimento-sne/{cnpj}/{placa}/{chaveInfracao}
POST /api/v1/Senatran/solicitar-boleto-desconto20/{cnpj}/{placa}/{chaveInfracao}
POST /api/v1/Senatran/solicitar-boleto-desconto40/{cnpj}/{placa}/{chaveInfracao}
POST /api/v1/Senatran/solicitar-boleto-sem-desconto/{cnpj}/{placa}/{chaveInfracao}
POST /api/v1/Senatran/upsert-token
POST /api/v1/Serpro/efrotas-event-receiver
POST /api/v1/Ticket/Efrotas/CaptureTicketByParams
POST /api/v1/Ticket/change-state-ticket-nic-not-pay
POST /api/v1/Ticket/files-concatenate
POST /api/v1/Ticket/fire-mexico-ticket-notification
POST /api/v1/Ticket/get-ticket-for-update-signature
POST /api/v1/Ticket/notificate-changes/{ticketId}
POST /api/v1/Ticket/send-email
POST /api/v1/Ticket/update-ticket-choice-status
POST /api/v1/Ticket/update-ticket-doc-status
POST /api/v1/Ticket/update-ticket-impeditivo-status
POST /api/v1/Ticket/update-ticket-not-edited
POST /api/v1/Ticket/update-ticket-rollback-nic-status
POST /api/v1/Ticket/{ticketId}/nic/cancel
POST /api/v1/Ticket/{ticketId}/nic/choose
POST /api/v1/TicketAlertNotification/fici-generator-alert/{multaId}
POST /api/v1/TicketPayment/municipal-fines/{veiculoEventoMultaId}
POST /api/v1/TicketPayment/municipal-identify-driver
POST /api/v1/TicketTrafic/GenerateContractResponsibility/{ticketId}
POST /api/v1/TicketsConfiguration
POST /api/v1/TrackingCodeHistory/insert-tracking-history
POST /api/v1/TrackingCodeHistory/tracking-history-bind
PUT /api/v1/ActuatorOrgan/Migrate-Actuator-Organ-without-addressId
PUT /api/v1/Senatran/ticket-billet/{veiculoEventoMultaId}
PUT /api/v1/Senatran/ticket-update-due-date/{veiculoEventoMultaId}
PUT /api/v1/Ticket/update-download-notification/{id}
PUT /api/v1/Ticket/{ticketId}/driver
Severity: info
Fingerprint: 5733ddf49ff49cd1aad03549276be4eebcafd3a2aa78ab43449b80b26342fa11
Public Swagger UI/API detected at path: /swagger/index.html - sample paths:
GET /api/v1/ActuatorOrgan/get-all
GET /api/v1/ActuatorOrgan/{code}
GET /api/v1/CategoryActuatorOrgan/get-all
GET /api/v1/Dnit/ait-detalhes/{autoInfracaoCode}
GET /api/v1/Dnit/check-status-ticket
GET /api/v1/Dnit/indicate-ticket/{autoInfracaoCode}
GET /api/v1/Mexico/{plate}
GET /api/v1/PaymentBank/get-all
GET /api/v1/Senatran/Crawler/Status
GET /api/v1/Senatran/buscar-infracoes-detalhes-por-placa/{cnpj}/{placa}
GET /api/v1/Senatran/get-all-token
GET /api/v1/Senatran/get-detalhes-infracao/{cnpj}/{placa}/{chaveInfracao}
GET /api/v1/Senatran/get-detalhes-veiculo/{cnpj}/{placa}/{renavam}
GET /api/v1/Senatran/get-log-senatran/{veiculoId}
GET /api/v1/Senatran/get-veiculos-usuario/{cnpj}
GET /api/v1/Senatran/plate-stamping/{plate}/{qrCode}
GET /api/v1/Senatran/visualizar-boleto/{cnpj}/{placa}/{chaveInfracao}
GET /api/v1/Ticket/Efrotas/cnpj/{cnpj}
GET /api/v1/Ticket/Efrotas/vehicle/{vehicleId}
GET /api/v1/Ticket/files
GET /api/v1/Ticket/get-ticket-details/{ticketId}
GET /api/v1/Ticket/get-tickets-by-plate/{plate}
GET /api/v1/Ticket/notificate-changes
GET /api/v1/TicketPayment/buscar-multas-vencer
GET /api/v1/TicketsConfiguration/get-all
GET /api/v1/TicketsConfiguration/{type}
PATCH /api/v1/Ticket/{ticketId}/exemptions
POST /api/v1/ActuatorOrgan/upsert
POST /api/v1/CategoryActuatorOrgan
POST /api/v1/Dnit/indicate-ticket-list
POST /api/v1/Dnit/update-status-list
POST /api/v1/Dnit/upsert-token
POST /api/v1/MailBatch/close-mail-batch
POST /api/v1/MailBatch/create-mail-batch-and-indicate
POST /api/v1/MailBatch/reproccess-mail-batch
POST /api/v1/MailBatch/update-indicaton-file
POST /api/v1/MailBatch/update-mail-batch-file
POST /api/v1/OcrProcess
POST /api/v1/PaymentBank/upsert
POST /api/v1/Regulatory/download-document-crlv
POST /api/v1/Regulatory/download-document-crlv-by-plate
POST /api/v1/Senatran/Crawler/Enable
POST /api/v1/Senatran/Crawler/Start
POST /api/v1/Senatran/Crawler/Stop
POST /api/v1/Senatran/buscar-multas-por-placa
POST /api/v1/Senatran/download-documento-crlv
POST /api/v1/Senatran/download-documento-crlv-por-placa
POST /api/v1/Senatran/gerar-token-senatran/{code}
POST /api/v1/Senatran/reconhecimento-sne/{cnpj}/{placa}/{chaveInfracao}
POST /api/v1/Senatran/solicitar-boleto-desconto20/{cnpj}/{placa}/{chaveInfracao}
POST /api/v1/Senatran/solicitar-boleto-desconto40/{cnpj}/{placa}/{chaveInfracao}
POST /api/v1/Senatran/solicitar-boleto-sem-desconto/{cnpj}/{placa}/{chaveInfracao}
POST /api/v1/Senatran/upsert-token
POST /api/v1/Serpro/efrotas-event-receiver
POST /api/v1/Ticket/Efrotas/CaptureTicketByParams
POST /api/v1/Ticket/change-state-ticket-nic-not-pay
POST /api/v1/Ticket/files-concatenate
POST /api/v1/Ticket/fire-mexico-ticket-notification
POST /api/v1/Ticket/get-ticket-for-update-signature
POST /api/v1/Ticket/notificate-changes/{ticketId}
POST /api/v1/Ticket/send-email
POST /api/v1/Ticket/update-ticket-choice-status
POST /api/v1/Ticket/update-ticket-doc-status
POST /api/v1/Ticket/update-ticket-impeditivo-status
POST /api/v1/Ticket/update-ticket-not-edited
POST /api/v1/Ticket/update-ticket-rollback-nic-status
POST /api/v1/Ticket/{ticketId}/nic/cancel
POST /api/v1/Ticket/{ticketId}/nic/choose
POST /api/v1/TicketAlertNotification/fici-generator-alert/{multaId}
POST /api/v1/TicketPayment/municipal-fines/{veiculoEventoMultaId}
POST /api/v1/TicketPayment/municipal-identify-driver
POST /api/v1/TicketTrafic/GenerateContractResponsibility/{ticketId}
POST /api/v1/TicketsConfiguration
POST /api/v1/TrackingCodeHistory/insert-tracking-history
POST /api/v1/TrackingCodeHistory/tracking-history-bind
PUT /api/v1/ActuatorOrgan/Migrate-Actuator-Organ-without-addressId
PUT /api/v1/Senatran/ticket-billet/{veiculoEventoMultaId}
PUT /api/v1/Senatran/ticket-update-due-date/{veiculoEventoMultaId}
PUT /api/v1/Ticket/update-download-notification/{id}
PUT /api/v1/Ticket/{ticketId}/driver
Severity: info
Fingerprint: 5733ddf49ff49cd1aad03549276be4eebcafd3a2aa78ab43449b80b2c0e25552
Public Swagger UI/API detected at path: /swagger/index.html - sample paths:
GET /api/v1/ActuatorOrgan/get-all
GET /api/v1/ActuatorOrgan/{code}
GET /api/v1/CategoryActuatorOrgan/get-all
GET /api/v1/Dnit/ait-detalhes/{autoInfracaoCode}
GET /api/v1/Dnit/check-status-ticket
GET /api/v1/Dnit/indicate-ticket/{autoInfracaoCode}
GET /api/v1/Mexico/{plate}
GET /api/v1/PaymentBank/get-all
GET /api/v1/Senatran/Crawler/Status
GET /api/v1/Senatran/buscar-infracoes-detalhes-por-placa/{cnpj}/{placa}
GET /api/v1/Senatran/get-all-token
GET /api/v1/Senatran/get-detalhes-infracao/{cnpj}/{placa}/{chaveInfracao}
GET /api/v1/Senatran/get-detalhes-veiculo/{cnpj}/{placa}/{renavam}
GET /api/v1/Senatran/get-log-senatran/{veiculoId}
GET /api/v1/Senatran/get-veiculos-usuario/{cnpj}
GET /api/v1/Senatran/plate-stamping/{plate}/{qrCode}
GET /api/v1/Senatran/visualizar-boleto/{cnpj}/{placa}/{chaveInfracao}
GET /api/v1/Ticket/Efrotas/cnpj/{cnpj}
GET /api/v1/Ticket/Efrotas/vehicle/{vehicleId}
GET /api/v1/Ticket/files
GET /api/v1/Ticket/get-ticket-details/{ticketId}
GET /api/v1/Ticket/get-tickets-by-plate/{plate}
GET /api/v1/Ticket/notificate-changes
GET /api/v1/TicketPayment/buscar-multas-vencer
GET /api/v1/TicketsConfiguration/get-all
GET /api/v1/TicketsConfiguration/{type}
PATCH /api/v1/Ticket/{ticketId}/exemptions
POST /api/v1/ActuatorOrgan/upsert
POST /api/v1/CategoryActuatorOrgan
POST /api/v1/Dnit/indicate-ticket-list
POST /api/v1/Dnit/update-status-list
POST /api/v1/Dnit/upsert-token
POST /api/v1/MailBatch/close-mail-batch
POST /api/v1/MailBatch/create-mail-batch-and-indicate
POST /api/v1/MailBatch/reproccess-mail-batch
POST /api/v1/MailBatch/update-indicaton-file
POST /api/v1/MailBatch/update-mail-batch-file
POST /api/v1/OcrProcess
POST /api/v1/PaymentBank/upsert
POST /api/v1/Regulatory/download-document-crlv
POST /api/v1/Regulatory/download-document-crlv-by-plate
POST /api/v1/Senatran/Crawler/Enable
POST /api/v1/Senatran/Crawler/Start
POST /api/v1/Senatran/Crawler/Stop
POST /api/v1/Senatran/buscar-multas-por-placa
POST /api/v1/Senatran/download-documento-crlv
POST /api/v1/Senatran/download-documento-crlv-por-placa
POST /api/v1/Senatran/gerar-token-senatran/{code}
POST /api/v1/Senatran/reconhecimento-sne/{cnpj}/{placa}/{chaveInfracao}
POST /api/v1/Senatran/solicitar-boleto-desconto20/{cnpj}/{placa}/{chaveInfracao}
POST /api/v1/Senatran/solicitar-boleto-desconto40/{cnpj}/{placa}/{chaveInfracao}
POST /api/v1/Senatran/solicitar-boleto-sem-desconto/{cnpj}/{placa}/{chaveInfracao}
POST /api/v1/Senatran/upsert-token
POST /api/v1/Serpro/efrotas-event-receiver
POST /api/v1/Ticket/Efrotas/CaptureTicketByParams
POST /api/v1/Ticket/change-state-ticket-nic-not-pay
POST /api/v1/Ticket/files-concatenate
POST /api/v1/Ticket/fire-mexico-ticket-notification
POST /api/v1/Ticket/get-ticket-for-update-signature
POST /api/v1/Ticket/notificate-changes/{ticketId}
POST /api/v1/Ticket/send-email
POST /api/v1/Ticket/update-ticket-choice-status
POST /api/v1/Ticket/update-ticket-doc-status
POST /api/v1/Ticket/update-ticket-impeditivo-status
POST /api/v1/Ticket/update-ticket-not-edited
POST /api/v1/Ticket/update-ticket-rollback-nic-status
POST /api/v1/TicketAlertNotification/fici-generator-alert/{multaId}
POST /api/v1/TicketPayment/municipal-fines/{veiculoEventoMultaId}
POST /api/v1/TicketPayment/municipal-identify-driver
POST /api/v1/TicketTrafic/GenerateContractResponsibility/{ticketId}
POST /api/v1/TicketsConfiguration
POST /api/v1/TrackingCodeHistory/insert-tracking-history
POST /api/v1/TrackingCodeHistory/tracking-history-bind
PUT /api/v1/ActuatorOrgan/Migrate-Actuator-Organ-without-addressId
PUT /api/v1/Senatran/ticket-billet/{veiculoEventoMultaId}
PUT /api/v1/Senatran/ticket-update-due-date/{veiculoEventoMultaId}
PUT /api/v1/Ticket/update-download-notification/{id}
PUT /api/v1/Ticket/{ticketId}/driver
Exposing Swagger/OpenAPI documentation is primarily a risk if your API has underlying security flaws, as it gives attackers a precise roadmap to find them.
Those detail every endpoint, parameter, and data model, making it easier to discover and exploit vulnerabilities like broken access control or injection points.
While a perfectly secure API mitigates the danger, protecting your documentation is a critical layer of defense that forces attackers to work without a map.
Severity: info
Fingerprint: 5733ddf49ff49cd1aad03549128dd1cd96ac6d5096ac6d5096ac6d5096ac6d50
Public Swagger UI/API detected at path: /swagger/index.html - sample paths: GET /InitialBalance/check POST /InitialBalance/update
Exposing Swagger/OpenAPI documentation is primarily a risk if your API has underlying security flaws, as it gives attackers a precise roadmap to find them.
Those detail every endpoint, parameter, and data model, making it easier to discover and exploit vulnerabilities like broken access control or injection points.
While a perfectly secure API mitigates the danger, protecting your documentation is a critical layer of defense that forces attackers to work without a map.
Severity: info
Fingerprint: 5733ddf49ff49cd1aad035499adb4b75a5b9b5e23a775b9de18ab5becaa0943b
Public Swagger UI/API detected at path: /swagger/index.html - sample paths:
GET /api/v1/carbon-credit/users/journeys
GET /api/v1/carbon-credit/vehicles
GET /api/v1/customer-integration
GET /api/v1/customer/{individualRegistration}/eligibility
POST /api/v1/force-events/user-onboarding
Severity: info
Fingerprint: 5733ddf49ff49cd1aad035499adb4b75a5b9b5e23a775b9d9ae9466e9ae9466e
Public Swagger UI/API detected at path: /swagger/index.html - sample paths: GET /api/v1/carbon-credit/users/journeys GET /api/v1/carbon-credit/vehicles GET /api/v1/customer-integration POST /api/v1/force-events/user-onboarding
Severity: info
Fingerprint: 5733ddf49ff49cd1aad035499adb4b75a5b9b5e23a775b9d3a775b9d3a775b9d
Public Swagger UI/API detected at path: /swagger/index.html - sample paths: GET /api/v1/carbon-credit/users/journeys GET /api/v1/carbon-credit/vehicles GET /api/v1/customer-integration
Exposing Swagger/OpenAPI documentation is primarily a risk if your API has underlying security flaws, as it gives attackers a precise roadmap to find them.
Those detail every endpoint, parameter, and data model, making it easier to discover and exploit vulnerabilities like broken access control or injection points.
While a perfectly secure API mitigates the danger, protecting your documentation is a critical layer of defense that forces attackers to work without a map.
Severity: info
Fingerprint: 5733ddf49ff49cd1aad03549cdf589784409014f9a62c5a02312f0847a691dd4
Public Swagger UI/API detected at path: /swagger/index.html - sample paths: GET /VirtualOdometer/GetFuelSavingsLastWeek GET /VirtualOdometer/GetUserYearRetrospective GET /VirtualOdometer/GetValidationFlexPlan GET /VirtualOdometer/GetVirtualOdometer GET /VirtualOdometer/GetVirtualOdometerLastWeek
Exposing Swagger/OpenAPI documentation is primarily a risk if your API has underlying security flaws, as it gives attackers a precise roadmap to find them.
Those detail every endpoint, parameter, and data model, making it easier to discover and exploit vulnerabilities like broken access control or injection points.
While a perfectly secure API mitigates the danger, protecting your documentation is a critical layer of defense that forces attackers to work without a map.
Severity: info
Fingerprint: 5733ddf49ff49cd1aad0354924426c475428151f7e9ba72e74441d9ecf928b16
Public Swagger UI/API detected at path: /swagger/index.html - sample paths:
DELETE /api/v1/dynamic-reissue-integration/{id}
GET /api/v1/dynamic-reissue
GET /api/v1/dynamic-reissue-integration
GET /api/v1/dynamic-reissue/{id}
GET /api/v1/file-manager/download/{id}
GET /api/v1/session/{sessionKey}
POST /api/v1/AutoReissue
POST /api/v1/AutoReissue/mx
POST /api/v1/dynamic-reissue/beautify
POST /api/v1/dynamic-reissue/execute/{slug}
POST /api/v1/dynamic-reissue/staging/{context}
POST /api/v1/dynamic-reissue/validate
POST /api/v1/file-manager/upload
POST /api/v1/session
Exposing Swagger/OpenAPI documentation is primarily a risk if your API has underlying security flaws, as it gives attackers a precise roadmap to find them.
Those detail every endpoint, parameter, and data model, making it easier to discover and exploit vulnerabilities like broken access control or injection points.
While a perfectly secure API mitigates the danger, protecting your documentation is a critical layer of defense that forces attackers to work without a map.
Severity: info
Fingerprint: 5733ddf49ff49cd1aad03549a723573b51d4b2a1b8bfebfd1688000b1688000b
Public Swagger UI/API detected at path: /swagger/index.html - sample paths: GET /api/v1/Configuration POST /Senatran/hcaptcha-solver POST /api/v1/CoreJob/execute-job POST /api/v1/CoreJob/execute-job-sync
Exposing Swagger/OpenAPI documentation is primarily a risk if your API has underlying security flaws, as it gives attackers a precise roadmap to find them.
Those detail every endpoint, parameter, and data model, making it easier to discover and exploit vulnerabilities like broken access control or injection points.
While a perfectly secure API mitigates the danger, protecting your documentation is a critical layer of defense that forces attackers to work without a map.
Severity: info
Fingerprint: 5733ddf49ff49cd1aad035492f0c342e488f5041437a5cb75d8cbeaa5d8cbeaa
Public Swagger UI/API detected at path: /swagger/index.html - sample paths:
GET /api/v1/ValidateBypassImages/inspection-photos
GET /api/v1/ValidateBypassImages/{serviceId}
POST /api/v1/ValidateBypassImages
POST /api/v1/ValidateBypassImages/inspection-photos-body-json/process
Exposing Swagger/OpenAPI documentation is primarily a risk if your API has underlying security flaws, as it gives attackers a precise roadmap to find them.
Those detail every endpoint, parameter, and data model, making it easier to discover and exploit vulnerabilities like broken access control or injection points.
While a perfectly secure API mitigates the danger, protecting your documentation is a critical layer of defense that forces attackers to work without a map.
Severity: info
Fingerprint: 5733ddf49ff49cd1aad035499c166320da512024f7fa056db566a67e44253ce7
Public Swagger UI/API detected at path: /swagger/index.html - sample paths:
DELETE /api/v1/EvaluationPrinciple/evaluation/{evaluationId}/principle/{principleId}
DELETE /api/v1/cycle/{cycleId}/employee/{cycleEmployeeId}
GET /api/v1/Assignment
GET /api/v1/Assignment/direct-leader
GET /api/v1/Assignment/has-adjusted-evaluation
GET /api/v1/Cycle
GET /api/v1/Cycle/{id}
GET /api/v1/Dashboard
GET /api/v1/Dashboard/has-role/{role}
GET /api/v1/Evaluation
GET /api/v1/Evaluation/final/cycles
GET /api/v1/Evaluation/previous-for-adjusted
GET /api/v1/Evaluation/previous-for-final
GET /api/v1/EvaluationPrinciple/evaluation/{evaluationId}
GET /api/v1/EvaluationPrinciple/evaluation/{evaluationId}/principles/adjusted
GET /api/v1/EvaluationPrinciple/evaluation/{evaluationId}/principles/calibrated
GET /api/v1/EvaluationPrinciple/evaluation/{evaluationId}/principles/consolidated
GET /api/v1/EvaluationPrinciple/evaluation/{evaluationId}/principles/final
GET /api/v1/EvaluationPrinciple/evaluation/{evaluationId}/principles/original
GET /api/v1/Principle/all
GET /api/v1/Principle/unique-values
GET /api/v1/RatingAuditLog
GET /api/v1/RatingAuditLog/export-csv
GET /api/v1/Report/cycle/{cycleId}
GET /api/v1/Report/ended-cycles
GET /api/v1/cycle/{cycleId}/employee
POST /api/v1/Evaluation/adjusted
POST /api/v1/Evaluation/calibrated
POST /api/v1/Evaluation/consolidated
POST /api/v1/Evaluation/final
POST /api/v1/Evaluation/original
POST /api/v1/Evaluation/submit-with-data
POST /api/v1/Evaluation/{id}/approve
POST /api/v1/Evaluation/{id}/reject
POST /api/v1/Evaluation/{id}/submit
POST /api/v1/EvaluationPrinciple
POST /api/v1/ImportEmployees/upload
POST /api/v1/Principle
PUT /api/v1/Assignment/{id}
PUT /api/v1/Principle/{id}
Severity: info
Fingerprint: 5733ddf49ff49cd1aad035499c166320da512024f7fa056db566a67e14497390
Public Swagger UI/API detected at path: /swagger/index.html - sample paths:
DELETE /api/v1/EvaluationPrinciple/evaluation/{evaluationId}/principle/{principleId}
DELETE /api/v1/cycle/{cycleId}/employee/{cycleEmployeeId}
GET /api/v1/Assignment
GET /api/v1/Assignment/direct-leader
GET /api/v1/Assignment/has-adjusted-evaluation
GET /api/v1/Cycle
GET /api/v1/Cycle/{id}
GET /api/v1/Dashboard
GET /api/v1/Dashboard/has-role/{role}
GET /api/v1/Evaluation
GET /api/v1/Evaluation/previous-for-adjusted
GET /api/v1/Evaluation/previous-for-final
GET /api/v1/EvaluationPrinciple/evaluation/{evaluationId}
GET /api/v1/EvaluationPrinciple/evaluation/{evaluationId}/principles/adjusted
GET /api/v1/EvaluationPrinciple/evaluation/{evaluationId}/principles/calibrated
GET /api/v1/EvaluationPrinciple/evaluation/{evaluationId}/principles/consolidated
GET /api/v1/EvaluationPrinciple/evaluation/{evaluationId}/principles/final
GET /api/v1/EvaluationPrinciple/evaluation/{evaluationId}/principles/original
GET /api/v1/Principle/all
GET /api/v1/Principle/unique-values
GET /api/v1/RatingAuditLog
GET /api/v1/RatingAuditLog/export-csv
GET /api/v1/cycle/{cycleId}/employee
POST /api/v1/Evaluation/adjusted
POST /api/v1/Evaluation/calibrated
POST /api/v1/Evaluation/consolidated
POST /api/v1/Evaluation/final
POST /api/v1/Evaluation/original
POST /api/v1/Evaluation/submit-with-data
POST /api/v1/Evaluation/{id}/approve
POST /api/v1/Evaluation/{id}/reject
POST /api/v1/Evaluation/{id}/submit
POST /api/v1/EvaluationPrinciple
POST /api/v1/ImportEmployees/upload
POST /api/v1/Principle
PUT /api/v1/Assignment/{id}
PUT /api/v1/Principle/{id}
Severity: info
Fingerprint: 5733ddf49ff49cd1aad035499c166320da512024f7fa056d002bcbc72d480181
Public Swagger UI/API detected at path: /swagger/index.html - sample paths:
DELETE /api/v1/EvaluationPrinciple/evaluation/{evaluationId}/principle/{principleId}
DELETE /api/v1/cycle/{cycleId}/employee/{cycleEmployeeId}
GET /api/v1/Assignment
GET /api/v1/Cycle
GET /api/v1/Cycle/{id}
GET /api/v1/Dashboard
GET /api/v1/Dashboard/has-role/{role}
GET /api/v1/Evaluation
GET /api/v1/EvaluationPrinciple/evaluation/{evaluationId}
GET /api/v1/EvaluationPrinciple/evaluation/{evaluationId}/principles/calibrated
GET /api/v1/EvaluationPrinciple/evaluation/{evaluationId}/principles/consolidated
GET /api/v1/EvaluationPrinciple/evaluation/{evaluationId}/principles/original
GET /api/v1/Principle/all
GET /api/v1/Principle/unique-values
GET /api/v1/RatingAuditLog
GET /api/v1/RatingAuditLog/export-csv
GET /api/v1/cycle/{cycleId}/employee
POST /api/v1/Evaluation/calibrated
POST /api/v1/Evaluation/consolidated
POST /api/v1/Evaluation/original
POST /api/v1/Evaluation/submit-with-data
POST /api/v1/Evaluation/{id}/submit
POST /api/v1/EvaluationPrinciple
POST /api/v1/ImportEmployees/upload
POST /api/v1/Principle
PUT /api/v1/Assignment/{id}
PUT /api/v1/Principle/{id}
Exposing Swagger/OpenAPI documentation is primarily a risk if your API has underlying security flaws, as it gives attackers a precise roadmap to find them.
Those detail every endpoint, parameter, and data model, making it easier to discover and exploit vulnerabilities like broken access control or injection points.
While a perfectly secure API mitigates the danger, protecting your documentation is a critical layer of defense that forces attackers to work without a map.
Severity: info
Fingerprint: 5733ddf49ff49cd1aad0354979f97ac3afeb620bffc176fb475b13ee09b6436c
Public Swagger UI/API detected at path: /swagger/index.html - sample paths:
GET /api/v1/Example
GET /api/v1/File
GET /api/v1/File/{id}
GET /api/v1/File/{id}/download
POST /api/v1/File/upload
Exposing Swagger/OpenAPI documentation is primarily a risk if your API has underlying security flaws, as it gives attackers a precise roadmap to find them.
Those detail every endpoint, parameter, and data model, making it easier to discover and exploit vulnerabilities like broken access control or injection points.
While a perfectly secure API mitigates the danger, protecting your documentation is a critical layer of defense that forces attackers to work without a map.
Severity: info
Fingerprint: 5733ddf49ff49cd1aad03549b41909ef304717fddde66a0805206662b1a4399b
Public Swagger UI/API detected at path: /swagger/index.html - sample paths:
GET /api/v1/CustomPoliceReportText
GET /api/v1/CustomPoliceReportText/{id}
GET /api/v1/Document/{vehicleId}/Dossier
GET /api/v1/Document/{vehicleId}/PoliceReport
GET /api/v1/Document/{vehicleId}/PowerOfAttorney
GET /api/v1/DossierType
GET /api/v1/DossierType/{id}
GET /api/v1/PoliceReport
GET /api/v1/PoliceReport/by-vehicle/{vehicleId}
POST /api/v1/Dossier/download-bulk
POST /api/v1/Dossier/{vehicleId}
POST /api/v1/Dossier/{vehicleId}/evidences
Exposing Swagger/OpenAPI documentation is primarily a risk if your API has underlying security flaws, as it gives attackers a precise roadmap to find them.
Those detail every endpoint, parameter, and data model, making it easier to discover and exploit vulnerabilities like broken access control or injection points.
While a perfectly secure API mitigates the danger, protecting your documentation is a critical layer of defense that forces attackers to work without a map.
Severity: info
Fingerprint: 5733ddf49ff49cd1aad03549a5a52ee172d778349a17d52bd830abadb80e242b
Public Swagger UI/API detected at path: /swagger/index.html - sample paths:
GET /_ah/health
GET /_ah/liveness
GET /_ah/startup
GET /api/v1/Servico/veiculo/{veiculoId}
POST /api/v1/Servico/applyDistribution
POST /api/v1/Servico/apreensao/{servicoId}
POST /api/v1/Servico/distribute
Exposing Swagger/OpenAPI documentation is primarily a risk if your API has underlying security flaws, as it gives attackers a precise roadmap to find them.
Those detail every endpoint, parameter, and data model, making it easier to discover and exploit vulnerabilities like broken access control or injection points.
While a perfectly secure API mitigates the danger, protecting your documentation is a critical layer of defense that forces attackers to work without a map.
Severity: info
Fingerprint: 5733ddf49ff49cd12ec8532c2ec8532c2ec8532c2ec8532c2ec8532c2ec8532c
Public Swagger UI/API detected at path: /swagger/index.html
Exposing Swagger/OpenAPI documentation is primarily a risk if your API has underlying security flaws, as it gives attackers a precise roadmap to find them.
Those detail every endpoint, parameter, and data model, making it easier to discover and exploit vulnerabilities like broken access control or injection points.
While a perfectly secure API mitigates the danger, protecting your documentation is a critical layer of defense that forces attackers to work without a map.
Severity: info
Fingerprint: 5733ddf49ff49cd12ec8532c2ec8532c2ec8532c2ec8532c2ec8532c2ec8532c
Public Swagger UI/API detected at path: /swagger/index.html
Severity: info
Fingerprint: 5733ddf49ff49cd1aad0354998f8f83d160ff75d8f0e87e0894ba2eac5bd26f2
Public Swagger UI/API detected at path: /swagger/index.html - sample paths:
GET /api/installment-staging/v1/external-reference/{externalReference}
GET /api/installment-staging/v1/id/{messageId}
GET /api/raw-persistence/v1/id/{messageId}
POST /api/installment-staging/v1/filter
POST /api/installment-staging/v1/unstage-create
POST /api/installment-staging/v1/unstage-create-job
POST /api/messaging-confirmation/v1/externalReference
POST /api/outbox-reprocess/v1/create/sync
POST /api/raw-persistence/v1/filter
POST /api/reprocessing-queue/v1/create
Severity: info
Fingerprint: 5733ddf49ff49cd1aad0354998f8f83d160ff75dac0fe05df19cb8e09d4560b7
Public Swagger UI/API detected at path: /swagger/index.html - sample paths:
GET /api/installment-staging/v1/external-reference/{externalReference}
GET /api/installment-staging/v1/id/{messageId}
GET /api/messaging-confirmation/v1/externalReference/{externalReference}
GET /api/raw-persistence/v1/id/{messageId}
POST /api/installment-staging/v1/filter
POST /api/installment-staging/v1/unstage-create
POST /api/installment-staging/v1/unstage-create-job
POST /api/outbox-reprocess/v1/create/sync
POST /api/raw-persistence/v1/filter
POST /api/reprocessing-queue/v1/create
Exposing Swagger/OpenAPI documentation is primarily a risk if your API has underlying security flaws, as it gives attackers a precise roadmap to find them.
Those detail every endpoint, parameter, and data model, making it easier to discover and exploit vulnerabilities like broken access control or injection points.
While a perfectly secure API mitigates the danger, protecting your documentation is a critical layer of defense that forces attackers to work without a map.
Severity: info
Fingerprint: 5733ddf49ff49cd12ec8532c2ec8532c2ec8532c2ec8532c2ec8532c2ec8532c
Public Swagger UI/API detected at path: /swagger/index.html
Severity: info
Fingerprint: 5733ddf49ff49cd1aad035495996960a346e893de4a8eb4ce654a8e9953d1fca
Public Swagger UI/API detected at path: /swagger/index.html - sample paths:
DELETE /api/v1/control-tower-user-params/branches/{userId}
DELETE /api/v1/control-tower-user-params/{id}
DELETE /api/v1/customer-debt-service/{id}
DELETE /api/v1/customer-debt/{id}
DELETE /api/v1/customer-vehicle-transfer-tag/{id}
DELETE /api/v1/customer-vehicle-transfer/{id}
DELETE /api/v1/notes/category-notes/{id}
DELETE /api/v1/user-support/{UserSupportId}
DELETE /api/v1/work-schedule-base/{id}
DELETE /api/v1/work-schedule-type/{id}
DELETE /api/v1/work-schedule/{id}
GET /api/v1/accounting-closing
GET /api/v1/accounting-closing/{accountCloseId}
GET /api/v1/control-tower-service-events
GET /api/v1/control-tower-service-events/getLinkTracking/{userId}
GET /api/v1/control-tower-support-events
GET /api/v1/control-tower-user-params
GET /api/v1/control-tower-user-params/userId/{userId}
GET /api/v1/customer-debt
GET /api/v1/customer-debt-accountable
GET /api/v1/customer-debt-service
GET /api/v1/customer-debt-tag
GET /api/v1/customer-debt/by-user/{userId}
GET /api/v1/customer-debt/by-vehicle
GET /api/v1/customer-debt/card-open
GET /api/v1/customer-debt/{customerDebtId}
GET /api/v1/customer-vehicle-transfer
GET /api/v1/customer-vehicle-transfer-comments/card-comments/{id}
GET /api/v1/customer-vehicle-transfer-comments/{id}
GET /api/v1/customer-vehicle-transfer-files/card-files/{id}
GET /api/v1/customer-vehicle-transfer-files/{id}
GET /api/v1/customer-vehicle-transfer-tag
GET /api/v1/customer-vehicle-transfer/GetAllCards
GET /api/v1/distribution-configuration
GET /api/v1/distribution-configuration/{placeId}
GET /api/v1/distribution-result
GET /api/v1/distribution-result/{id}
GET /api/v1/employee-geo-limits
GET /api/v1/employee-outsourcing
GET /api/v1/employee-outsourcing/list-all
GET /api/v1/employee-outsourcing/{id}
GET /api/v1/employee-skill
GET /api/v1/employee-skill/{id}
GET /api/v1/mobile/minimum-android-version
GET /api/v1/mobile/notifications/{usuarioSuporteId}
GET /api/v1/notes/category-notes/{entityType}
GET /api/v1/notes/{entityType}/{entityId}
GET /api/v1/outsourcing-organization
GET /api/v1/outsourcing-organization/inactives
GET /api/v1/outsourcing-organization/list-all
GET /api/v1/outsourcing-organization/list-all/with-shipments
GET /api/v1/outsourcing-organization/phone-number/{vehicleExternalId}
GET /api/v1/outsourcing-organization/{id}
GET /api/v1/outsourcing-organization/{organizationId}/employees/with-shipments
GET /api/v1/parameter-configuration/{name}
GET /api/v1/rescue-vehicle-params
GET /api/v1/rescue-vehicle-params/support-user/{id}
GET /api/v1/rescue-vehicle-params/warehouse/branchs
GET /api/v1/rescue-vehicle-params/{id}
GET /api/v1/service-address/{id}
GET /api/v1/service-configuration
GET /api/v1/service-configuration/{placeId}
GET /api/v1/service-configuration/{placeId}/serviceGroupType/{serviceGroupTypeId}
GET /api/v1/service-history/balance
GET /api/v1/service-history/balance/internal
GET /api/v1/service-history/balance/organizations
GET /api/v1/service-history/dashboard
GET /api/v1/service-history/dashboard-organization
GET /api/v1/service-history/get-service-supplies/{vehicleId}/{days}
GET /api/v1/service-tags
GET /api/v1/service-tags/by-id
GET /api/v1/service-tags/tags-by-service-type-id
GET /api/v1/service-tags/{serviceId}/tags
GET /api/v1/service-type-supply
GET /api/v1/service-type-supply/{serviceTypeId}
GET /api/v1/service-type-supply/{serviceTypeId}/{vehicleModelType}
GET /api/v1/service-value/{serviceId}/{situationId}
GET /api/v1/service-voice-history/validate-call-details
GET /api/v1/support-ticket
GET /api/v1/support-ticket/is-definition-collection
GET /api/v1/support-ticket/rejections
GET /api/v1/support-ticket/rejections/grouped
GET /api/v1/support-ticket/rejections/list-types
GET /api/v1/support-ticket/{id}
GET /api/v1/support-ticket/{id}/payment-promise
GET /api/v1/vehicle
GET /api/v1/vehicle/list-all
GET /api/v1/vehicle/search
GET /api/v1/vehicle/vehicles-organization/{userId}
GET /api/v1/vehicle/{id}
GET /api/v1/warehouse/catalog
GET /api/v1/warehouse/devolution/branch/{branchId}
GET /api/v1/warehouse/finalize/{AddressCatalogId}
GET /api/v1/warehouse/order/{veiculoSuporteId}
GET /api/v1/warehouse/orders
GET /api/v1/warehouse/orders/active
GET /api/v1/warehouse/report/{veiculoSuporteId}
GET /api/v1/warehouse/v2/orders
GET /api/v1/warehouse/v2/warehouse/clearcache/{CacheName}
GET /api/v1/warehouse/v2/warehouse/{LugarId}
GET /api/v1/warehouse/vehicleSupplies/{veiculoTipoId}
GET /api/v1/warehouse/vistory
GET /api/v1/work-schedule
GET /api/v1/work-schedule-base
GET /api/v1/work-schedule-events/jornada
GET /api/v1/work-schedule-events/usuarioSuporte
GET /api/v1/work-schedule-records/actives
GET /api/v1/work-schedule-records/vehicle/{vehicleId}/AtDate/{date}
GET /api/v1/work-schedule-records/{workScheduleId}
GET /api/v1/work-schedule-timeline/usuario/{usuarioSuporteId}
GET /api/v1/work-schedule-type/{countryId}
GET /api/v1/work-schedule/actives
GET /api/v1/work-schedule/shifts
GET /api/v1/work-schedule/status
GET /api/v1/work-schedule/{usuarioSuporteId}
GET /support-ticket/{id}
PATCH /api/v1/customer-debt/accountable
PATCH /api/v1/customer-debt/situation
PATCH /api/v1/customer-debt/update-days-overdue
PATCH /api/v1/customer-vehicle-transfer/move-phase
PATCH /api/v1/employee-outsourcing/active/{userId}
PATCH /api/v1/rescue-vehicle-params/warehouse-version
PATCH /api/v1/support-ticket/link-conversation
PATCH /api/v1/support-ticket/{id}/unlink-conversation
PATCH /api/v1/vehicle-support/activate/{vehicleSupportId}
PATCH /api/v1/vehicle/active/{vehicleId}
POST /api/v1/customer-debt-tag/tags-by-customer-debt
POST /api/v1/customer-debt/add-customer-debt-event
POST /api/v1/customer-vehicle-transfer-comments
POST /api/v1/customer-vehicle-transfer-files
POST /api/v1/customer-vehicle-transfer/remove-tag-card
POST /api/v1/distribution-result/execution
POST /api/v1/distribution-result/geometry
POST /api/v1/mobile-log/logs
POST /api/v1/mobile-log/logs-in-batch
POST /api/v1/mobile/register
POST /api/v1/mobile/sendMessage
POST /api/v1/mobile/unregister
POST /api/v1/monitor-flow-response
POST /api/v1/mottu-field
POST /api/v1/notes
POST /api/v1/notes/category-notes
POST /api/v1/ocr/validate-vehicle/{vehicleId}
POST /api/v1/outsourcing-organization/{id}/migrate
POST /api/v1/service-address
POST /api/v1/service-voice-history/create-call
POST /api/v1/service-voice-history/create-call-details
POST /api/v1/service-voice-history/default-create-call-details
POST /api/v1/support-ticket/tags-ticket-support
POST /api/v1/user-support/disconnectOffline
POST /api/v1/user-support/setOnlineStatus/{online}
POST /api/v1/user-support/transferVehicle
POST /api/v1/warehouse-branch
POST /api/v1/warehouse/finalize/address
POST /api/v1/warehouse/finalize/v3/{veiculoSuporteId}
POST /api/v1/warehouse/order
POST /api/v1/warehouse/order-reprocess
POST /api/v1/warehouse/report/address
POST /api/v1/warehouse/v2/consume
POST /api/v1/work-schedule-base/generate-work-schedule/{usuarioSuporteId}
POST /api/v1/work-schedule-base/generate-work-schedules
POST /api/v1/work-schedule-base/generate-work-schedules-by-branch/{branchId}
POST /api/v1/work-schedule-base/generate-work-schedules-v2
POST /api/v1/work-schedule-records
POST /api/v1/work-schedule-type
POST /api/v1/work-schedule/pause-start
POST /api/v1/work-schedule/pause-stop
PUT /api/v1/distribution-configuration/{id}
PUT /api/v1/employee-geo-limits/{id}
PUT /api/v1/employee-outsourcing/{id}/sign-terms
PUT /api/v1/mobile/notifications/{notificationId}/accept
PUT /api/v1/mobile/notifications/{notificationId}/read
PUT /api/v1/mobile/notifications/{notificationId}/render
PUT /api/v1/outsourcing-organization/activate
PUT /api/v1/parameter-configuration
PUT /api/v1/service-configuration/{id}
PUT /api/v1/warehouse/v2/order
Severity: info
Fingerprint: 5733ddf49ff49cd1aad035495996960a346e893de4a8eb4ce654a8e971909430
Public Swagger UI/API detected at path: /swagger/index.html - sample paths:
DELETE /api/v1/control-tower-user-params/branches/{userId}
DELETE /api/v1/control-tower-user-params/{id}
DELETE /api/v1/customer-debt-service/{id}
DELETE /api/v1/customer-debt/{id}
DELETE /api/v1/customer-vehicle-transfer-tag/{id}
DELETE /api/v1/customer-vehicle-transfer/{id}
DELETE /api/v1/user-support/{UserSupportId}
DELETE /api/v1/work-schedule-base/{id}
DELETE /api/v1/work-schedule/{id}
GET /api/v1/accounting-closing
GET /api/v1/accounting-closing/{accountCloseId}
GET /api/v1/control-tower-service-events
GET /api/v1/control-tower-service-events/getLinkTracking/{userId}
GET /api/v1/control-tower-support-events
GET /api/v1/control-tower-user-params
GET /api/v1/control-tower-user-params/userId/{userId}
GET /api/v1/customer-debt
GET /api/v1/customer-debt-accountable
GET /api/v1/customer-debt-service
GET /api/v1/customer-debt-tag
GET /api/v1/customer-debt/by-user/{userId}
GET /api/v1/customer-debt/by-vehicle
GET /api/v1/customer-debt/card-open
GET /api/v1/customer-debt/{customerDebtId}
GET /api/v1/customer-vehicle-transfer
GET /api/v1/customer-vehicle-transfer-comments/card-comments/{id}
GET /api/v1/customer-vehicle-transfer-comments/{id}
GET /api/v1/customer-vehicle-transfer-files/card-files/{id}
GET /api/v1/customer-vehicle-transfer-files/{id}
GET /api/v1/customer-vehicle-transfer-tag
GET /api/v1/customer-vehicle-transfer/GetAllCards
GET /api/v1/distribution-configuration
GET /api/v1/distribution-configuration/{placeId}
GET /api/v1/distribution-result
GET /api/v1/distribution-result/{id}
GET /api/v1/employee-geo-limits
GET /api/v1/employee-outsourcing
GET /api/v1/employee-outsourcing/list-all
GET /api/v1/employee-outsourcing/{id}
GET /api/v1/employee-skill
GET /api/v1/employee-skill/{id}
GET /api/v1/mobile/notifications/{usuarioSuporteId}
GET /api/v1/outsourcing-organization
GET /api/v1/outsourcing-organization/inactives
GET /api/v1/outsourcing-organization/list-all
GET /api/v1/outsourcing-organization/{id}
GET /api/v1/parameter-configuration/{name}
GET /api/v1/rescue-vehicle-params
GET /api/v1/rescue-vehicle-params/support-user/{id}
GET /api/v1/rescue-vehicle-params/{id}
GET /api/v1/service-address/{id}
GET /api/v1/service-configuration
GET /api/v1/service-configuration/{placeId}
GET /api/v1/service-configuration/{placeId}/serviceGroupType/{serviceGroupTypeId}
GET /api/v1/service-history/balance
GET /api/v1/service-history/balance/internal
GET /api/v1/service-history/balance/organizations
GET /api/v1/service-history/dashboard
GET /api/v1/service-history/dashboard-organization
GET /api/v1/service-history/get-service-supplies/{vehicleId}/{days}
GET /api/v1/service-tags
GET /api/v1/service-tags/by-id
GET /api/v1/service-tags/tags-by-service-type-id
GET /api/v1/service-type-supply
GET /api/v1/service-type-supply/{serviceTypeId}
GET /api/v1/service-type-supply/{serviceTypeId}/{vehicleModelType}
GET /api/v1/service-value/{serviceId}/{situationId}
GET /api/v1/service-voice-history/validate-call-details
GET /api/v1/support-ticket
GET /api/v1/support-ticket/is-definition-collection
GET /api/v1/support-ticket/rejections
GET /api/v1/support-ticket/rejections/grouped
GET /api/v1/support-ticket/rejections/list-types
GET /api/v1/support-ticket/{id}
GET /api/v1/support-ticket/{id}/payment-promise
GET /api/v1/vehicle
GET /api/v1/vehicle/list-all
GET /api/v1/vehicle/search
GET /api/v1/vehicle/{id}
GET /api/v1/warehouse/catalog
GET /api/v1/warehouse/devolution/branch/{branchId}
GET /api/v1/warehouse/finalize/{AddressCatalogId}
GET /api/v1/warehouse/order/{veiculoSuporteId}
GET /api/v1/warehouse/orders
GET /api/v1/warehouse/orders/active
GET /api/v1/warehouse/report/{veiculoSuporteId}
GET /api/v1/warehouse/v2/orders
GET /api/v1/warehouse/v2/warehouse/clearcache/{CacheName}
GET /api/v1/warehouse/v2/warehouse/{LugarId}
GET /api/v1/warehouse/vehicleSupplies/{veiculoTipoId}
GET /api/v1/warehouse/vistory
GET /api/v1/work-schedule
GET /api/v1/work-schedule-base
GET /api/v1/work-schedule-events/jornada
GET /api/v1/work-schedule-events/usuarioSuporte
GET /api/v1/work-schedule-records/actives
GET /api/v1/work-schedule-records/vehicle/{vehicleId}/AtDate/{date}
GET /api/v1/work-schedule-records/{workScheduleId}
GET /api/v1/work-schedule-timeline/usuario/{usuarioSuporteId}
GET /api/v1/work-schedule/actives
GET /api/v1/work-schedule/shifts
GET /api/v1/work-schedule/status
GET /api/v1/work-schedule/{usuarioSuporteId}
GET /support-ticket/{id}
PATCH /api/v1/customer-debt/accountable
PATCH /api/v1/customer-debt/situation
PATCH /api/v1/customer-debt/update-days-overdue
PATCH /api/v1/customer-vehicle-transfer/move-phase
PATCH /api/v1/employee-outsourcing/active/{userId}
PATCH /api/v1/support-ticket/link-conversation
PATCH /api/v1/support-ticket/{id}/unlink-conversation
PATCH /api/v1/vehicle/active/{vehicleId}
POST /api/v1/customer-debt-tag/tags-by-customer-debt
POST /api/v1/customer-debt/add-customer-debt-event
POST /api/v1/customer-vehicle-transfer-comments
POST /api/v1/customer-vehicle-transfer-files
POST /api/v1/customer-vehicle-transfer/remove-tag-card
POST /api/v1/distribution-result/execution
POST /api/v1/distribution-result/geometry
POST /api/v1/mobile-log/logs
POST /api/v1/mobile-log/logs-in-batch
POST /api/v1/mobile/register
POST /api/v1/mobile/sendMessage
POST /api/v1/mobile/unregister
POST /api/v1/mottu-field
POST /api/v1/ocr/validate-vehicle/{vehicleId}
POST /api/v1/service-address
POST /api/v1/service-voice-history/create-call
POST /api/v1/service-voice-history/create-call-details
POST /api/v1/service-voice-history/default-create-call-details
POST /api/v1/support-ticket/tags-ticket-support
POST /api/v1/user-support/disconnectOffline
POST /api/v1/user-support/setOnlineStatus/{online}
POST /api/v1/vehicle/simple
POST /api/v1/warehouse-branch
POST /api/v1/warehouse/finalize/address
POST /api/v1/warehouse/finalize/v3/{veiculoSuporteId}
POST /api/v1/warehouse/order
POST /api/v1/warehouse/order-reprocess
POST /api/v1/warehouse/report/address
POST /api/v1/warehouse/v2/consume
POST /api/v1/work-schedule-base/generate-work-schedule/{usuarioSuporteId}
POST /api/v1/work-schedule-base/generate-work-schedules
POST /api/v1/work-schedule-base/generate-work-schedules-by-branch/{branchId}
POST /api/v1/work-schedule-base/generate-work-schedules-v2
POST /api/v1/work-schedule-records
POST /api/v1/work-schedule/pause-start
POST /api/v1/work-schedule/pause-stop
PUT /api/v1/distribution-configuration/{id}
PUT /api/v1/employee-geo-limits/{id}
PUT /api/v1/employee-outsourcing/{id}/sign-terms
PUT /api/v1/mobile/notifications/{notificationId}/accept
PUT /api/v1/mobile/notifications/{notificationId}/read
PUT /api/v1/mobile/notifications/{notificationId}/render
PUT /api/v1/outsourcing-organization/activate/{organizationId}
PUT /api/v1/parameter-configuration
PUT /api/v1/service-configuration/{id}
PUT /api/v1/warehouse/v2/order
Exposing Swagger/OpenAPI documentation is primarily a risk if your API has underlying security flaws, as it gives attackers a precise roadmap to find them.
Those detail every endpoint, parameter, and data model, making it easier to discover and exploit vulnerabilities like broken access control or injection points.
While a perfectly secure API mitigates the danger, protecting your documentation is a critical layer of defense that forces attackers to work without a map.
Severity: info
Fingerprint: 5733ddf49ff49cd1aad0354977ca33874d52570a6665b719b143756e032f33c4
Public Swagger UI/API detected at path: /swagger/index.html - sample paths:
DELETE /api/v1/agency/{id}/labels
DELETE /api/v1/dispatch-metadata/{id}
DELETE /api/v1/dispatch/{id}
GET /api/v1/agency
GET /api/v1/courier
GET /api/v1/dispatch
GET /api/v1/dispatch-event
GET /api/v1/dispatch-metadata
GET /api/v1/integration-token
GET /api/v1/integration-token/{name}
GET /api/v1/postalcode
GET /api/v1/uniquecode/codes
POST /api/v1/file-manager/upload
POST /api/v1/uniquecode/check-usage
POST /api/v1/uniquecode/consume
POST /api/v1/uniquecode/generate-pattern
PUT /api/v1/agency/labels
PUT /api/v1/dispatch-event/schedule-update
PUT /api/v1/dispatch-metadata/upsert
PUT /api/v1/dispatch/send
PUT /api/v1/dispatch/upsert
PUT /api/v1/dispatch/{id}/send
Severity: info
Fingerprint: 5733ddf49ff49cd1aad0354977ca33874d52570a6665b719b143756e8e9c194c
Public Swagger UI/API detected at path: /swagger/index.html - sample paths:
DELETE /api/v1/agency/{id}/labels
DELETE /api/v1/dispatch-metadata/{id}
DELETE /api/v1/dispatch/{id}
GET /api/v1/agency
GET /api/v1/courier
GET /api/v1/dispatch
GET /api/v1/dispatch-event
GET /api/v1/dispatch-metadata
GET /api/v1/integration-token
GET /api/v1/integration-token/{name}
GET /api/v1/postalcode
GET /api/v1/uniquecode/codes
POST /api/v1/file-manager/upload
POST /api/v1/uniquecode/check-usage
POST /api/v1/uniquecode/consume
POST /api/v1/uniquecode/generate-pattern
PUT /api/v1/agency/labels
PUT /api/v1/dispatch-event/schedule-update
PUT /api/v1/dispatch-metadata/upsert
PUT /api/v1/dispatch/upsert
PUT /api/v1/dispatch/{id}/send
Severity: info
Fingerprint: 5733ddf49ff49cd1aad0354977ca33874d52570a6665b719b143756ec298f1b9
Public Swagger UI/API detected at path: /swagger/index.html - sample paths:
DELETE /api/v1/agency/{id}/labels
DELETE /api/v1/dispatch-metadata/{id}
DELETE /api/v1/dispatch/{id}
GET /api/v1/agency
GET /api/v1/courier
GET /api/v1/dispatch
GET /api/v1/dispatch-event
GET /api/v1/dispatch-metadata
GET /api/v1/file-manager/redirect/{id}
GET /api/v1/postalcode
POST /api/v1/file-manager/upload
PUT /api/v1/agency/labels
PUT /api/v1/dispatch-event/schedule-update
PUT /api/v1/dispatch-metadata/upsert
PUT /api/v1/dispatch/upsert
PUT /api/v1/dispatch/{id}/send
Severity: info
Fingerprint: 5733ddf49ff49cd1aad0354977ca33874d52570a6665b719b143756e62fd3dd8
Public Swagger UI/API detected at path: /swagger/index.html - sample paths:
DELETE /api/v1/agency/{id}/labels
DELETE /api/v1/dispatch-metadata/{id}
DELETE /api/v1/dispatch/{id}
GET /api/v1/agency
GET /api/v1/dispatch
GET /api/v1/dispatch-event
GET /api/v1/dispatch-metadata
GET /api/v1/file-manager/redirect/{id}
GET /api/v1/postalcode
POST /api/v1/file-manager/upload
PUT /api/v1/agency/labels
PUT /api/v1/dispatch-event/schedule-update
PUT /api/v1/dispatch-metadata/upsert
PUT /api/v1/dispatch/upsert
PUT /api/v1/dispatch/{id}/send
Exposing Swagger/OpenAPI documentation is primarily a risk if your API has underlying security flaws, as it gives attackers a precise roadmap to find them.
Those detail every endpoint, parameter, and data model, making it easier to discover and exploit vulnerabilities like broken access control or injection points.
While a perfectly secure API mitigates the danger, protecting your documentation is a critical layer of defense that forces attackers to work without a map.
Severity: info
Fingerprint: 5733ddf49ff49cd1aad0354971c3908fe370b7be9aa2d86bd4525f18d4525f18
Public Swagger UI/API detected at path: /swagger/index.html - sample paths: GET /api/v1/Auth/token GET /api/v1/VtexSalesOrderIntegrator/configuration/webhook POST /api/v1/VtexSalesOrderIntegrator/configure/webhook POST /api/v1/VtexSalesOrderIntegrator/receive/order
Exposing Swagger/OpenAPI documentation is primarily a risk if your API has underlying security flaws, as it gives attackers a precise roadmap to find them.
Those detail every endpoint, parameter, and data model, making it easier to discover and exploit vulnerabilities like broken access control or injection points.
While a perfectly secure API mitigates the danger, protecting your documentation is a critical layer of defense that forces attackers to work without a map.
Severity: info
Fingerprint: 5733ddf49ff49cd1aad0354957e7046dc57bb9450c4724b6560de67a6247a4b4
Public Swagger UI/API detected at path: /swagger/index.html - sample paths:
GET /api/v1/table-auditing
GET /api/v1/table-auditing/{id}
GET /api/v1/transfer-orders/for-admin
GET /api/v1/transfer-orders/for-operator
GET /api/v1/transfer-orders/vehicle-models
GET /api/v1/transfer-orders/{id}
GET /api/v1/transfer-orders/{transferOrderId}/tracking-map
GET /api/v1/transport-companies
GET /api/v1/transport-companies/{id}
GET /api/v1/vehicles-for-transfer/{transferOrderId}
PATCH /api/v1/transfer-orders/{transferOrderId}/cancel
PATCH /api/v1/transfer-orders/{transferOrderId}/destination-branch
PATCH /api/v1/transfer-orders/{transferOrderId}/remove-vehicle/{vehicleId}
PATCH /api/v1/transfer-orders/{transferOrderId}/vehicle-quantity
PATCH /api/v1/vehicles-for-transfer/add-vehicle
PATCH /api/v1/vehicles-for-transfer/confirm-batch-transfer
PATCH /api/v1/vehicles-for-transfer/receive
PATCH /api/v1/vehicles-for-transfer/remove
POST /api/v1/transfer-orders
Severity: info
Fingerprint: 5733ddf49ff49cd1aad0354957e7046dc57bb9450c4724b6560de67a48eb32f8
Public Swagger UI/API detected at path: /swagger/index.html - sample paths:
GET /api/v1/table-auditing
GET /api/v1/table-auditing/{id}
GET /api/v1/transfer-orders/for-admin
GET /api/v1/transfer-orders/for-operator
GET /api/v1/transfer-orders/vehicle-models
GET /api/v1/transfer-orders/{id}
GET /api/v1/transfer-orders/{transferOrderId}/tracking-map
GET /api/v1/transport-companies
GET /api/v1/transport-companies/{id}
GET /api/v1/vehicles-for-transfer/{transferOrderId}
PATCH /api/v1/transfer-orders/{transferOrderId}/cancel
PATCH /api/v1/transfer-orders/{transferOrderId}/destination-branch
PATCH /api/v1/transfer-orders/{transferOrderId}/vehicle-quantity
PATCH /api/v1/vehicles-for-transfer/add-vehicle
PATCH /api/v1/vehicles-for-transfer/confirm-batch-transfer
PATCH /api/v1/vehicles-for-transfer/receive
PATCH /api/v1/vehicles-for-transfer/remove
POST /api/v1/transfer-orders
Exposing Swagger/OpenAPI documentation is primarily a risk if your API has underlying security flaws, as it gives attackers a precise roadmap to find them.
Those detail every endpoint, parameter, and data model, making it easier to discover and exploit vulnerabilities like broken access control or injection points.
While a perfectly secure API mitigates the danger, protecting your documentation is a critical layer of defense that forces attackers to work without a map.
Severity: info
Fingerprint: 5733ddf49ff49cd1aad0354979f97ac379f97ac379f97ac379f97ac379f97ac3
Public Swagger UI/API detected at path: /swagger/index.html - sample paths: GET /api/v1/Example
Exposing Swagger/OpenAPI documentation is primarily a risk if your API has underlying security flaws, as it gives attackers a precise roadmap to find them.
Those detail every endpoint, parameter, and data model, making it easier to discover and exploit vulnerabilities like broken access control or injection points.
While a perfectly secure API mitigates the danger, protecting your documentation is a critical layer of defense that forces attackers to work without a map.
Severity: info
Fingerprint: 5733ddf49ff49cd1aad035494039cbcd6f6414b41a7390ffde38396e7f75a4a7
Public Swagger UI/API detected at path: /swagger/index.html - sample paths:
GET /api/sync/jobs
GET /api/sync/jobs/{jobId}
GET /api/sync/jobs/{jobId}/result
POST /api/Sync/batch-sync-v2-to-v3
POST /api/Sync/create-v2
POST /api/Sync/sync-by-document
POST /api/Sync/sync-by-guid
POST /api/Sync/sync-by-id
POST /api/Sync/sync-by-id-v3
POST /api/Sync/sync-v2-to-v3
POST /api/Sync/sync-v3-to-v2
Exposing Swagger/OpenAPI documentation is primarily a risk if your API has underlying security flaws, as it gives attackers a precise roadmap to find them.
Those detail every endpoint, parameter, and data model, making it easier to discover and exploit vulnerabilities like broken access control or injection points.
While a perfectly secure API mitigates the danger, protecting your documentation is a critical layer of defense that forces attackers to work without a map.
Severity: info
Fingerprint: 5733ddf49ff49cd1aad03549d957e87dfef6c9bdf73b26af6ed9d87d5325dc83
Public Swagger UI/API detected at path: /swagger/index.html - sample paths:
GET /api/v1/test-rider-parameters
GET /api/v1/test-rider-parameters/{id}
GET /api/v1/test-riders
GET /api/v1/test-riders/{id}
GET /api/v1/test-riders/{id}/current-location
GET /api/v1/test-riders/{id}/location-history
POST /api/v1/users-driver-licenses/upload
POST /api/v1/users-driver-licenses/user-validation
PUT /api/v1/test-riders/finish
Exposing Swagger/OpenAPI documentation is primarily a risk if your API has underlying security flaws, as it gives attackers a precise roadmap to find them.
Those detail every endpoint, parameter, and data model, making it easier to discover and exploit vulnerabilities like broken access control or injection points.
While a perfectly secure API mitigates the danger, protecting your documentation is a critical layer of defense that forces attackers to work without a map.
Severity: info
Fingerprint: 5733ddf49ff49cd1aad03549eec801a32c4670332c4670332c4670332c467033
Public Swagger UI/API detected at path: /swagger/index.html - sample paths: GET /api/v1/example GET /api/v1/messaging
Exposing Swagger/OpenAPI documentation is primarily a risk if your API has underlying security flaws, as it gives attackers a precise roadmap to find them.
Those detail every endpoint, parameter, and data model, making it easier to discover and exploit vulnerabilities like broken access control or injection points.
While a perfectly secure API mitigates the danger, protecting your documentation is a critical layer of defense that forces attackers to work without a map.
Severity: info
Fingerprint: 5733ddf49ff49cd12ec8532c2ec8532c2ec8532c2ec8532c2ec8532c2ec8532c
Public Swagger UI/API detected at path: /swagger/index.html
Exposing Swagger/OpenAPI documentation is primarily a risk if your API has underlying security flaws, as it gives attackers a precise roadmap to find them.
Those detail every endpoint, parameter, and data model, making it easier to discover and exploit vulnerabilities like broken access control or injection points.
While a perfectly secure API mitigates the danger, protecting your documentation is a critical layer of defense that forces attackers to work without a map.
Severity: info
Fingerprint: 5733ddf49ff49cd1aad03549d0e213394c5769528880c6d75423a52fefa47ccc
Public Swagger UI/API detected at path: /swagger/index.html - sample paths:
GET /api/params
GET /api/params/{parameters}/value
GET /api/params/{parameter}/details
PATCH /api/params/{parameter}/value
PUT /api/params/{parameter}
Exposing Swagger/OpenAPI documentation is primarily a risk if your API has underlying security flaws, as it gives attackers a precise roadmap to find them.
Those detail every endpoint, parameter, and data model, making it easier to discover and exploit vulnerabilities like broken access control or injection points.
While a perfectly secure API mitigates the danger, protecting your documentation is a critical layer of defense that forces attackers to work without a map.
Severity: info
Fingerprint: 5733ddf49ff49cd1aad035494378c760589ca7eb0d54d4a97670924f8e732c7a
Public Swagger UI/API detected at path: /swagger/index.html - sample paths:
GET /api/insights
GET /api/insights/{id}
GET /api/layers/dynamic
GET /api/layers/dynamic/{h3Index}
GET /api/layers/open-orders
GET /api/layers/open-orders/{h3Index}
GET /api/layers/sla-ecommerce
GET /api/layers/sla-ecommerce/{h3Index}
GET /api/layers/sla-food
GET /api/layers/sla-food/{h3Index}
GET /api/layers/temperature
GET /api/layers/temperature/{h3Index}
GET /api/layers/weather
GET /api/layers/weather/{h3Index}
GET /api/maps
Open service 35.238.232.9:443 · financescheduler.mottu.cloud
2026-01-23 16:21
HTTP/1.1 302 Found Date: Fri, 23 Jan 2026 16:21:26 GMT Content-Length: 0 Connection: close Set-Cookie: INGRESSCOOKIE=1769185286.699.10445.364475|9308c1d67d1121669dfd20dd75108e8f; Path=/; Secure; HttpOnly Location: /hangfire Strict-Transport-Security: max-age=31536000; includeSubDomains
Open service 35.238.232.9:443 · supply-chain-accounting-api.mottu.cloud
2026-01-23 14:25
HTTP/1.1 404 Not Found Date: Fri, 23 Jan 2026 14:25:28 GMT Content-Length: 0 Connection: close Strict-Transport-Security: max-age=31536000; includeSubDomains
Open service 35.238.232.9:443 · accountancy-outbox-api.mottu.cloud
2026-01-23 13:47
HTTP/1.1 404 Not Found Date: Fri, 23 Jan 2026 13:48:00 GMT Content-Length: 0 Connection: close Strict-Transport-Security: max-age=31536000; includeSubDomains
Open service 35.238.232.9:443 · mottu-store-backend.mottu.cloud
2026-01-23 12:26
HTTP/1.1 404 Not Found Date: Fri, 23 Jan 2026 12:26:46 GMT Content-Length: 0 Connection: close Strict-Transport-Security: max-age=31536000; includeSubDomains
Open service 35.238.232.9:443 · accountinggateway.mottu.cloud
2026-01-23 11:50
HTTP/1.1 302 Found Date: Fri, 23 Jan 2026 11:50:54 GMT Content-Length: 0 Connection: close Set-Cookie: INGRESSCOOKIE=1769169055.385.6510.225969|74abe7f7a8dc789ff11509ee6120a7f2; Path=/; Secure; HttpOnly Location: /hangfire Strict-Transport-Security: max-age=31536000; includeSubDomains
Open service 35.238.232.9:443 · partner-integration-api.mottu.cloud
2026-01-23 11:15
HTTP/1.1 404 Not Found Date: Fri, 23 Jan 2026 11:15:52 GMT Content-Length: 0 Connection: close x-request-id: 02244df5b6c3b9a70368fff7b58fd6d6 Strict-Transport-Security: max-age=31536000; includeSubDomains
Open service 35.238.232.9:443 · tickets-manager.mottu.cloud
2026-01-23 10:53
HTTP/1.1 404 Not Found Date: Fri, 23 Jan 2026 10:53:47 GMT Content-Length: 0 Connection: close Strict-Transport-Security: max-age=31536000; includeSubDomains
Open service 35.238.232.9:443 · assessement-test-api.mottu.cloud
2026-01-23 10:47
HTTP/1.1 503 Service Temporarily Unavailable Date: Fri, 23 Jan 2026 10:47:21 GMT Content-Type: text/html Content-Length: 190 Connection: close Strict-Transport-Security: max-age=31536000; includeSubDomains Page title: 503 Service Temporarily Unavailable <html> <head><title>503 Service Temporarily Unavailable</title></head> <body> <center><h1>503 Service Temporarily Unavailable</h1></center> <hr><center>nginx</center> </body> </html>
Open service 35.238.232.9:443 · beta-monitor-field-service.mottu.cloud
2026-01-23 09:22
HTTP/1.1 404 Not Found Date: Fri, 23 Jan 2026 09:22:20 GMT Content-Length: 0 Connection: close x-correlation-id: 6fc1cf1e-0e3d-4945-aed3-13c2b89d868e Strict-Transport-Security: max-age=31536000; includeSubDomains
Open service 35.238.232.9:443 · platform-courier-api.mottu.cloud
2026-01-23 08:25
HTTP/1.1 404 Not Found Date: Fri, 23 Jan 2026 08:25:08 GMT Content-Length: 0 Connection: close Strict-Transport-Security: max-age=31536000; includeSubDomains
Open service 35.238.232.9:443 · regulatory-api.mottu.cloud
2026-01-23 07:43
HTTP/1.1 404 Not Found Date: Fri, 23 Jan 2026 07:43:24 GMT Content-Length: 0 Connection: close Strict-Transport-Security: max-age=31536000; includeSubDomains
Open service 35.238.232.9:443 · historicorodagem.mottu.cloud
2026-01-23 07:32
HTTP/1.1 404 Not Found Date: Fri, 23 Jan 2026 07:32:55 GMT Content-Length: 0 Connection: close Strict-Transport-Security: max-age=31536000; includeSubDomains
Open service 35.238.232.9:443 · payments-backend.mottu.cloud
2026-01-23 03:44
HTTP/1.1 404 Not Found Date: Fri, 23 Jan 2026 03:44:21 GMT Content-Length: 0 Connection: close X-Trace-Id: 4318191719212420347-0HNIQ5525TDK6:00000001 Strict-Transport-Security: max-age=31536000; includeSubDomains
Open service 35.238.232.9:443 · validacao-bypass-imagem-api.mottu.cloud
2026-01-22 23:43
HTTP/1.1 404 Not Found Date: Thu, 22 Jan 2026 23:43:47 GMT Content-Length: 0 Connection: close Strict-Transport-Security: max-age=31536000; includeSubDomains
Open service 35.238.232.9:443 · oficios-resposta-bff.mottu.cloud
2026-01-22 22:20
HTTP/1.1 404 Not Found Date: Thu, 22 Jan 2026 22:20:30 GMT Content-Length: 0 Connection: close Strict-Transport-Security: max-age=31536000; includeSubDomains
Open service 35.238.232.9:443 · delivery-financial-backend.mottu.cloud
2026-01-22 18:58
HTTP/1.1 404 Not Found Date: Thu, 22 Jan 2026 18:58:04 GMT Content-Type: text/html Content-Length: 146 Connection: close Strict-Transport-Security: max-age=31536000; includeSubDomains Page title: 404 Not Found <html> <head><title>404 Not Found</title></head> <body> <center><h1>404 Not Found</h1></center> <hr><center>nginx</center> </body> </html>
Open service 35.238.232.9:443 · oficios-resposta-bff.mottu.cloud
2026-01-10 02:05
HTTP/1.1 404 Not Found Date: Sat, 10 Jan 2026 02:05:32 GMT Content-Length: 0 Connection: close Strict-Transport-Security: max-age=31536000; includeSubDomains
Open service 35.238.232.9:443 · monitor-test-rider-api.mottu.cloud
2026-01-09 02:42
HTTP/1.1 404 Not Found Date: Fri, 09 Jan 2026 02:42:43 GMT Content-Length: 0 Connection: close x-request-id: 72334d595d871576f902fab62156bdaf Strict-Transport-Security: max-age=31536000; includeSubDomains
tickets-manager.mottu.cloud 4 platform-courier-api.mottu.cloud 4 beta-monitor-field-service.mottu.cloud 3 accountancy-outbox-api.mottu.cloud 3 evaluation-cycle-api.mottu.cloud 3 partner-integration-api.mottu.cloud 3 monitor-transfer-api.mottu.cloud 2 mottu-store-backend.mottu.cloud 2 oficios-resposta-bff.mottu.cloud 2 rpa-core-job.mottu.cloud 1 regulatory-api.mottu.cloud 1 historicorodagem.mottu.cloud 1 payments-backend.mottu.cloud 1 validacao-bypass-imagem-api.mottu.cloud 1 financescheduler.mottu.cloud 1 delivery-financial-backend.mottu.cloud 1 monitor-test-rider-api.mottu.cloud 1 assessement-test-api.mottu.cloud 1 accountinggateway.mottu.cloud 1 monitor-bo.mottu.cloud 1 monitor-services.mottu.cloud 1 monitor-apreensoes.mottu.cloud 1 ecm-integrator-api.mottu.cloud 1 supply-chain-accounting-api.mottu.cloud 1 agendamento-api.mottu.cloud 1 user-sync-api.mottu.cloud 1 deliveryparams.mottu.cloud 1 delivery-maps.mottu.cloud 1