Entity reference · v1

messaging

MSG-NNNNNNtable messaging_frameworkssoft delete

Per-segment messaging frameworks (headline, key messages, proof, objections).

Endpoints

GET/api/v1/messagingList messaging

POST/api/v1/messagingCreate messaging

GET/api/v1/messaging/{id}Read one

PATCH/api/v1/messaging/{id}Update

DELETE/api/v1/messaging/{id}Soft-delete (?hard=true to skip trash)

POST/api/v1/messaging/{id}/restoreRestore from trash

Writable fields

* required on create. PATCH treats every field as optional.

Field	Type	Constraints	Notes
title*	string
segment	string
headline	string
subheadline	string
key_messages	json
proof_points	json
objection_handling	json
persona_id	uuid
competitor_id	uuid
is_draft	boolean
metadata	json

Listing & filtering

Pagination: ?limit=50&offset=0 · max limit 200
Default sort: ?sort=created_at&order=desc
Sortable fields: created_at · updated_at · title · id_number
Search (?q=): title, headline, subheadline
Filters: ?segment= ?persona_id= ?competitor_id= , repeat any filter to OR multiple values
Trash: hidden by default; pass ?include_deleted=true

Examples

curlbash

curl 'https://productos.ca/api/v1/messaging?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/messaging. The token is held in this page only for the request and is never stored.

Try it out

API token

Issue tokens in Settings → API tokens. Token never leaves this page.

GET/api/v1/messaging?limit=3