ProductOSDocs

Entity reference · v1

launches

LCH-NNNNNNtable launch_planssoft delete

Launch plans tied to releases.

Endpoints

GET/api/v1/launches
POST/api/v1/launches
GET/api/v1/launches/{id}
PATCH/api/v1/launches/{id}
DELETE/api/v1/launches/{id}
POST/api/v1/launches/{id}/restore

Writable fields

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

FieldTypeConstraintsNotes
title*string
release_iduuid
statusstringdraft | planning | active | launched | completed
launch_datedate
checklistjson
channelsjson
notestext
is_draftboolean
metadatajson

Listing & filtering

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

Examples

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

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