POST /v1/flow-http-connections/{id}/verify
POST
/v1/flow-http-connections/{id}/verify
const url = 'https://seu-endereco-da-api/v1/flow-http-connections/example/verify';const options = {method: 'POST', headers: {Authorization: 'Bearer <token>'}};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request POST \ --url https://seu-endereco-da-api/v1/flow-http-connections/example/verify \ --header 'Authorization: Bearer <token>'Permissão que a Chave de acesso precisa: Gerenciar fluxos (flows:manage).
Authorizations
Seção intitulada “Authorizations”Parameters
Seção intitulada “Parameters”Path Parameters
Seção intitulada “Path Parameters”id
required
string
Responses
Seção intitulada “Responses”Media typeapplication/json
object
ok
required
The test call came back with a 2xx status
boolean
httpStatus
required
Null when the call never left (blocked address, network, timeout)
number
durationMs
required
number
errorCode
required
Timeout | url_blocked | redirect | http_status | network
string
errorMessage
required
string
logId
required
The Registro line written for this test call
string
explanation
required
The same explanation the Registro shows; null when ok
object
cause
required
Chave da causa no dicionário, por exemplo http_404, timeout, meta_131047 ou desconhecido
string
title
required
O que aconteceu, em português
string
whatToDo
required
O que fazer
string
possibleCauses
required
Causas prováveis, da mais comum para a menos comum
Array<string>
Example generated
{ "ok": true, "httpStatus": 1, "durationMs": 1, "errorCode": "example", "errorMessage": "example", "logId": "example", "explanation": { "cause": "example", "title": "example", "whatToDo": "example", "possibleCauses": [ "example" ] }}