AD endpoint definitions use natural language descriptions rather than table-based configuration. This gives the platform more context to construct requests and interpret responses accurately.

Within Project Builder, you can prompt Ed the Builder to create AD endpoint definitions by providing any of the following:

  • An OpenAPI spec
  • API documentation or a REST API reference page
  • A raw curl command or prose description of the endpoint

AD endpoint definitions support more flexible request construction and response handling than traditional endpoints This includes the ability to draw values from multiple data sources within your project and reason about nested structures and conditional logic. Traditional endpoints do not support these capabilities.

To call an AD endpoint definition within your project, you need an AD logic block. To use an AD endpoint definition outside of Project Builder, create an AD logic block to call the endpoint, then reference that logic block from a traditional logic block.

Example prompts

For example, you could prompt Ed the Builder to:

  • "Create an endpoint definition using this OpenAPI spec." [paste spec]
  • "Build an endpoint that calls this API and filters results by order number." [paste documentation content]
  • "Set up an endpoint definition for this REST API so I can query invoice records by supplier." [paste API reference content]