Entity reference · v1
battle-card-criteria
tablebattle_card_criteriaPer-workspace rubric of comparison criteria used inside battle cards. Workspace-level config, not a Golden-Thread entity.
Endpoints
GET
/api/v1/battle-card-criteriaPOST
/api/v1/battle-card-criteriaGET
/api/v1/battle-card-criteria/{id}PATCH
/api/v1/battle-card-criteria/{id}DELETE
/api/v1/battle-card-criteria/{id}Writable fields
* required on create. PATCH treats every field as optional.
| Field | Type | Constraints | Notes |
|---|---|---|---|
| name* | string | ||
| description | text | ||
| category* | string | ||
| sort_order | integer | ≥ 0 |
Listing & filtering
- Pagination:
?limit=50&offset=0· max limit 200 - Default sort:
?sort=sort_order&order=asc - Sortable fields: created_at · updated_at · sort_order · name
- Search (?q=): name, description
- Filters: ?category= , repeat any filter to OR multiple values
Examples
curlbash
curl 'https://productos.ca/api/v1/battle-card-criteria?limit=10' \
-H "Authorization: Bearer $TOKEN"Try it out
Paste a token and hit a real endpoint. The request goes from your browser straight to /api/v1/battle-card-criteria. The token is held in this page only for the request and is never stored.
Try it out
Issue tokens in Settings → API tokens. Token never leaves this page.
GET/api/v1/battle-card-criteria?limit=3