public

List recipe definitions

No scope required — recipes are schema, and GET /export already carries every definition to any key on the directory.

Full definitions, not summaries: a recipe is four small JSON objects, and the caller most likely to list them is one about to PATCH one and needs scope in hand to merge into. Ordered by slug rather than newest-first, so two consecutive builds are comparable.

Note this is the definitions, not their results. GET .../recipes/:recipe executes.

get/public/v1/directories/{directory}/recipes

Request

  • Base URL: https://api.epicdirectories.com
  • URL: https://api.epicdirectories.com/public/v1/directories/{directory}/recipes
  • Auth: API key in header x-api-key

Path parameters

directorystring required

Query parameters

recipeTypestring

Only recipes of this type.

Headers

Idempotency-Keystring

Optional. Send a unique key per logical operation to make retries safe. 1-256 characters, and only letters, digits, - and _ — colons and other separators are rejected with 400. A retry with the same key replays the original response (status + body) instead of re-executing. Cached for 24h. Reusing a key with a different request body returns 409 — note that a timestamp in the body (e.g. fetchedAt) turns an otherwise-stable key into a permanent 409, so either omit it (snapshots default it server-side) or fold a payload digest into the key. Skipped on 5xx responses (transient errors should be retried fresh).

x-api-keystring required

API Key for authentication

Response

Recipe definitions, ordered by slug

Changes

No recorded changes to this operation across all 1 revision of this API.