Published APIs

Published APIs expose approved operations to application clients through an Eden-managed contract. They are useful when a template or workflow needs a stable application-facing name, request shape, and authorization boundary.

Lifecycle

1. Define the approved template or workflow that will back the API.
2. Create the published API resource with POST /apis.
3. Inspect, update, or delete the resource through the APIs endpoint.
4. Execute it through the published API route documented in the Published APIs reference.

Related

• Published APIs reference
• Templates
• Workflow Definitions