Skip to main content
Call evaluate from a Shared Flow and raise a fault on block.

​
Coverage

Ask — the Shared Flow maps the verdict onto a boolean, so an ask gate is allowed and recorded. Write the rule as Block if you need a hard stop. Use it when Apigee is your API management layer and you can attach the Shared Flow with an environment flow hook, covering every proxy by default. Not when you can only attach it proxy by proxy and the catalog grows fast — each new proxy is born uncovered. Limits. No masking: the documented flow raises a fault or lets the request pass. Both PreFlow and PostFlow attachments are needed for full direction coverage. Full comparison: Coverage.
  1. Create an API key on the collector.
  2. AssignMessage — build { protocol, direction, payload, consumer_id, session_id } (client_id / developer app as consumer_id).
  3. ServiceCallout — POST evaluate with Authorization: Bearer.
  4. RaiseFault 403 when status == "block".
  5. On transform, replace the message body with transformed_payload.
  6. Attach with FlowCallout on the request path (direction: input) and response path (direction: output).