ProductOSDocs

Entity reference · v1

market-signals

SIG-NNNNNNtable market_signalssoft delete

Individual data points feeding a market trend.

Endpoints

GET/api/v1/market-signals
POST/api/v1/market-signals
GET/api/v1/market-signals/{id}
PATCH/api/v1/market-signals/{id}
DELETE/api/v1/market-signals/{id}
POST/api/v1/market-signals/{id}/restore

Writable fields

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

FieldTypeConstraintsNotes
trend_iduuid
title*string
descriptiontext
sourcestring
source_urlstring
signal_datedate
tagsjson
ai_generatedboolean
is_draftboolean
metadatajson

Listing & filtering

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

Examples

curlbash
curl 'https://productos.ca/api/v1/market-signals?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/market-signals. 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/market-signals?limit=3

Generated from the API's entity configuration. This page is rebuilt on every deploy, so it always matches the live API.