Answers "would this destination be permitted", without creating anything.
POST
/v1/m/eventing/egress-policy/check
const url = 'https://example.com/v1/m/eventing/egress-policy/check';const options = { method: 'POST', headers: {Authorization: 'Bearer <token>', 'Content-Type': 'application/json'}, body: '{"endpoint":"example","subscription_id":"example"}'};
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://example.com/v1/m/eventing/egress-policy/check \ --header 'Authorization: Bearer <token>' \ --header 'Content-Type: application/json' \ --data '{ "endpoint": "example", "subscription_id": "example" }'Answers “would this destination be permitted”, without creating anything.
Authorizations
Section titled “Authorizations ”Parameters
Section titled “ Parameters ”Header Parameters
Section titled “Header Parameters ” X-Olivares-Tenant
string format: uuid
Target tenant id; required when the principal can act in more than one tenant.
Request Body required
Section titled “Request Body required ” Media type application/json
object
endpoint
required
HTTPS destination to check; configured loopback development may also accept HTTP. The deployment policy and DNS/IP safety checks remain authoritative.
string
subscription_id
string
Example generated
{ "endpoint": "example", "subscription_id": "example"}Responses
Section titled “ Responses ”OK
Media type application/json
object
Example generated
{}Bad request
Media type application/json
object
Example generated
{}Unauthenticated
Media type application/json
object
Example generated
{}Forbidden
Media type application/json
object
Example generated
{}Not found
Media type application/json
object
Example generated
{}Conflict / setup required
Media type application/json
object
Example generated
{}Rate limited
Media type application/json
object
Example generated
{}