Glowmarkt Notification System API
Alerting and messaging for Glow-based applications. Defines alert types, manages per-channel and per-culture message templates, sends alerts to users, and reports notification delivery and logs. Served from its own base path, /api/v0-1/ns.
Glowmarkt Notification System API is one of 5 APIs that Hildebrand publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include Notification, Alerts, Templates, and Messaging. The published artifact set on APIs.io includes an OpenAPI specification and an API reference.
This API exposes 15 operations across 10 paths, organized into 4 resource areas, and defines 16 schemas. It is described by OpenAPI 2.0, at version 1.0.0.
Requests are made against the base URL https://api.glowmarkt.com/api/v0-1/ns.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 6
Glowmarkt Notification System API declares
6 security schemes
for authenticating requests.
It defines a basic scheme (orgAppKeys).
It defines a basic scheme (appKeys).
An API key is passed in the header as token (devUserToken).
An API key is passed in the header as token (userToken).
An API key is passed in the header as applicationId (applicationId).
An API key is passed in the header as organizationId (organizationId).
Paths & Operations 15
Across 10 paths, the API surfaces 15 operations — 9 GET, 4 POST, 2 PUT. They span 4 resource areas: alerttype, alert, template, notification. Each is listed below with its method, path, parameters, and response codes.
The definition of an alert, what functionality the alert represents. It is an identifier which amongst other elements will point us to the correct template. An alert type belongs…
An application can send an alert to a customer across multiple channels (email, push, inbox) which will convey some type of specific message (defined by the alert type).
The template of the message that is being sent; it can be passed through as HTML or JSON. Each template has an alert type, is specific to a single channel of communication and a c…
When an application triggeers an alert, for each channel of communication a notification is created. This enables the system to monitor seperately whant happens in each channel.
Schemas 16
The contract defines 16 schemas that model the data the API accepts and returns. The most detailed are AlertReq (10 properties), Template (10 properties), NotificationLog (9 properties), TemplateReq (9 properties). Each schema is shown below with its type and property counts.
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from Hildebrand 4
Other APIs Hildebrand publishes across the network.
This is an independent, third-party profile of Glowmarkt Notification System API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.