List attribute templates
No scope required — templates are schema, and GET /export already hands every one of them to any key on the directory. Gating the dedicated read while the bulk read is open would protect nothing and cost a caller a 40 MB export to answer "what fields exist".
listingType filters the way attribute RESOLUTION works, not the way the column reads: it returns the type-scoped templates plus the type-agnostic ones, which together are exactly the keys PUT .../attributes will accept on a listing of that type.
Request
- Base URL: https://api.epicdirectories.com
- URL: https://api.epicdirectories.com/public/v1/directories/{directory}/attribute-templates
- Auth: API key in header x-api-key
Path parameters
Query parameters
Templates applicable to this listing type, including type-agnostic ones.
Headers
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).
API Key for authentication
Response
Templates, ordered by listingType then key
Changes
No recorded changes to this operation across all 1 revision of this API.