Entity reference · v1
positioning
POS-NNNNNNtable positioningsoft deletePer-segment positioning statements.
Endpoints
GET
/api/v1/positioningPOST
/api/v1/positioningGET
/api/v1/positioning/{id}PATCH
/api/v1/positioning/{id}DELETE
/api/v1/positioning/{id}POST
/api/v1/positioning/{id}/restoreWritable fields
* required on create. PATCH treats every field as optional.
| Field | Type | Constraints | Notes |
|---|---|---|---|
| segment | string | ||
| value_proposition | text | ||
| differentiators | json | ||
| messaging_pillars | json | ||
| target_persona_id | uuid | ||
| sort_order | integer | ||
| is_draft | boolean | ||
| metadata | json |
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 · id_number
- Search (?q=): value_proposition
- Filters: ?segment= ?target_persona_id= , repeat any filter to OR multiple values
- Trash: hidden by default; pass
?include_deleted=true
Examples
curlbash
curl 'https://productos.ca/api/v1/positioning?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/positioning. 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/positioning?limit=3