Market Radar API
API referenceNewsletters

Its template

The theme and the blocks in order, each with its id, and the version the template is at.

GET
/newsletters/{id}/template

Authorization

key
AuthorizationBearer <token>

A key created in the app under Settings, API and MCP. Read keys read; Read and write keys also add, edit and delete companies, custom sources, groups and radars, and create, rename and delete folders.

In: header

Path Parameters

id*integer
Range0 < value <= 9007199254740991

Response Body

application/json

application/json

application/json

application/json

application/json

curl -X GET "https://example.com/newsletters/1/template"
{  "template": {    "version": 1,    "theme": {      "logo": {        "url": "string",        "width": -9007199254740991,        "height": -9007199254740991,        "name": "string"      },      "colors": {        "brand": "string",        "text": "string",        "background": "string"      },      "fonts": {        "headings": "geist",        "text": "geist"      }    },    "blocks": [      {        "id": "string",        "type": "header",        "title": "string",        "layout": "left",        "show": {          "logo": true,          "title": true,          "issue": true,          "date": true        }      }    ]  },  "template_version": "string"}

Delete a newsletter DELETE

Its issues, their web versions and its recipients' subscriptions go; no more issues are sent. Its radars and their signals stay.

Add a block POST

After the block named, or just above the footer; with the fields given, the rest as the editor's palette drops them. A radar block's kind follows its radars. Applies from the next issue assembled.