A status-page notice: a coloured edge for the current state, the incident title, a stepper of states and the latest update.
These are real renders from the API with the example values in the table below. Switch the size above: the same template lays itself out for all 6 sizes — send size or sizes with the request.
For SaaS, hosting and status-page tools sharing an incident or a maintenance window. The status sets the colour (red, orange, blue, green or violet) and how far the stepper is lit; maintenance shows its own three steps. Up to five affected components are listed as chips with a "+N" for the rest, and the update text is clamped. Wide and square frames run the stepper across with the update below it; vertical frames run it down the side with the update under the current step.
Every field is optional. Long text shrinks to fit instead of overflowing; an image field takes a public URL that we fetch on our side.
| Field | Type | Description | Example |
|---|---|---|---|
title |
text | Incident title. default: Service disruption | Elevated error rates on image renders |
service |
text | Product or service name in the brand chip. | Northwind Cloud |
status |
text | One of investigating, identified, monitoring, resolved or maintenance. one of: investigating | identified | monitoring | resolved | maintenance default: investigating | monitoring |
update |
text | Latest update, shown in the callout. | A fix is live on the render pool. Error rates are back to normal and we are watching the queue. |
started |
text | When it started, e.g. Oct 26, 2026 · 08:12 UTC. | Oct 26, 2026 · 08:12 UTC |
components |
text |
Affected components separated by ;, e.g. Render API;Webhooks. Up to five chips.
|
Render API;Webhooks;Dashboard |
site |
text | Status page address. | status.northwind.dev |
logo |
image URL | Service logo, round. | https://example.com/images/logo-northwind.png |
accent |
colour | Brand colour as hex, e.g. #6366f1. Drives buttons, highlights and the background glow. default: #4f46e5 | #4f46e5 |
theme |
dark | light | Colour scheme: dark or light. default: light | — |
Use the slug as template. The response holds the URL of the finished PNG; ?wait=true keeps the connection open until it is ready.
curl -X POST "https://shareglint.com/v1/images?wait=true" \
-H "Authorization: Bearer sk_live_YOUR_KEY" \
-H "Content-Type: application/json" \
-d '{
"template": "incident-update",
"modifications": {
"title": "Elevated error rates on image renders",
"service": "Northwind Cloud",
"status": "monitoring",
"update": "A fix is live on the render pool. Error rates are back to normal and we are watching the queue.",
"started": "Oct 26, 2026 · 08:12 UTC",
"components": "Render API;Webhooks;Dashboard",
"site": "status.northwind.dev",
"logo": "https://example.com/images/logo-northwind.png"
}
}'
For static sites, Webflow, Shopify and no-code tools: put the fields in the query string and sign it with your signing secret. The first request renders the image, every later one is a redirect to the cached file. How to compute the signature.
<meta property="og:image" content="https://shareglint.com/i/acc_YOUR_ACCOUNT_ID/incident-update.png?components=Render%20API%3BWebhooks%3BDashboard&service=Northwind%20Cloud&site=status.northwind.dev&started=Oct%2026%2C%202026%20%C2%B7%2008%3A12%20UTC&status=monitoring&title=Elevated%20error%20rates%20on%20image%20renders&update=A%20fix%20is%20live%20on%20the%20render%20pool.%20Error%20rates%20are%20back%20to%20normal%20and%20we%20are%20watching%20the%20queue.&s=YOUR_SIGNATURE">
accent and theme change per request. For anything more, copy the template into your account: you get an ordinary HTML template with the same fields that you can edit in the dashboard or through the API. If the slug is free on your account, the copy takes it — your integrations switch to your version without changing a line.
curl -X POST "https://shareglint.com/v1/templates/library/incident-update/copy" \
-H "Authorization: Bearer sk_live_YOUR_KEY"