Approval Flow

When Yebo returns REQUIRE_APPROVAL, execution pauses. Nothing runs until a human explicitly approves on their device via biometric verification. Agents resume cleanly once the continuation token is issued.

This section is available to approved partners and pilot customers.

To access the full approval-flow reference including state transitions, continuation-token semantics, push delivery, expiry handling, and end-to-end examples, request access below.

Request Access | Start a Pilot

If you already have access, sign in to the developer portal: yebo.dev/login