Templates & dynamic content

The app's lookup tables by name and size, without expanding their data grids, alongside the per-app storage quota and how much of it is used.

One lookup table with its full data grid expanded — the row keys and the column values Liquid resolves against at send time.

Writes a whole lookup table under name, replacing any table already there — this is a replace, not a merge. The body is either {"data": {...}} or the grid itself: an object of row key → object of columns, where every row must carry the same column names as the first.

One table may not exceed 200 KB, and one app's tables may not exceed 2 MB in total; either ceiling is a 413.

Deletes one lookup table. Messages and templates that still reference it by name are not rewritten — they will fail validation the next time they are saved or sent.

Streams one lookup table back as a CSV attachment — the same round trip the import route reads. Cells are escaped against spreadsheet formula injection, so a value beginning with =, +, - or @ comes back with a leading apostrophe.

Replaces the table under name from an uploaded CSV, sent as a multipart field called file. The header row is a key column followed by one or more value columns; duplicate column names, duplicate row keys and empty keys are all refused with the line number.

The CSV may not exceed 200 KB, and the app's 2 MB dynamic-content quota still applies; either is a 413.

Every saved template for one app, newest first, with its data payload expanded — plus the names of the built-in starter templates the console offers.

Saves a reusable push template. name, title and body are required. Optional fields include image_url, deep_link, data, localized languages, default_language, and validated platform_options.

Liquid in every field is validated up front, and any dynamic-content table it references must already exist — an unknown table is a 400 rather than a template that fails at send time. There is no API route that uploads an image: image_url must be an HTTPS URL, or a /media/... path produced by uploading through the console.

Deletes a saved template. Messages already sent from it keep the content they were sent with, but a scheduled message that still resolves this template by id will fail when it comes to send.

Updates content, localized languages, default language or platform presentation defaults on a saved template. The merged result is revalidated, so a Liquid reference that only breaks once combined with the untouched fields is caught here. A patch with none of those keys is a 400.

Messages already created from this template retain their content snapshot, including scheduled messages.