Skip to main content
Call Darwin’s API from a server-side HTTP module and keep the API key in a protected connection.
Private custom-app testing is the current path. Darwin is not yet a public Make app; publication requires automated checks followed by Make’s manual QA review.
Search first, then map the selected capabilityId and capabilityRevision directly into Start action. Save actionId in the scenario’s durable data store if the work can outlive one execution. Use routers for nonterminal states. A successful HTTP response can still mean Darwin needs input, connection, payment, or approval before work can continue.

​
Scenario pattern

Use a new requestId for each new logical mutation. Reuse the same ID only when the scenario retries the identical request after a transport failure.
Last modified on September 22, 2026