Resume a waiting flow

Call this when your system is ready for a flow that is paused on a Wait for webhook node to continue. It's the URL shown on that node in Flow Builder. See Wait for webhook in the Flow Builder guide.

Body. A JSON object, up to 16 KB.

  • app_id is required. It's the application's session UUID (the app_session returned by Run a flow), not the numeric application ID.
  • Fields the node lists as Input variables are saved to the application's data and can be used by the next nodes.
  • Any other fields are saved on the application under wait_webhook_metadata.

Matching. LendAPI finds the application by app_id within your tenant, checks that it is running this flow, and finishes the wait it is paused on. The same URL serves every Wait for webhook node in the flow, whichever one the application is waiting on. A test_ key looks in Sandbox and a live_ key looks in Production.

What happens next. The response only confirms receipt. The flow continues in the background on the node's success path. If the node has only a timeout path, the run ends instead. If nobody calls before the node's Max wait time, the flow follows the timeout path if there is one, or stops.

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Path Params
uuid
required

The flow's ID (UUID). Copy it from the flow's API tab in Flow Builder.

Body Params
uuid
required

The application's session UUID (app_session from Run a flow).

Responses

401

Unauthorized. The API key is not valid or not active. The body is empty.

Language
Credentials
Header
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json