Skip to main content

Portal URL Documentation

This document describes public portal URLs that can be opened directly in a web browser.
They are intended for easy integration into third-party software, such as buttons, links, notifications, or external systems that need to open specific sections of the portal.

Base URL:
https://portal.ng-sos.com

Incident Overview​

Opens the overview of active incidents.

URL

/incident-list

Description

  • Opens the incident overview page
  • No url or query parameters

Example

Create Incident (Pre-filled Form)​

Opens the incident creation form with predefined values.

URL

/create-incident

Query Parameters​

NameTypeRequiredDescription
RequestedIncidentIdUUIDNoID of the new incident; a new UUID is generated when missing or invalid
PhoneNumberstringNoCaller phone number; the incident can be opened before the caller is known
CallerNamestringNoPre-filled caller name; displays an editable input when non-empty
LabelstringNoPre-filled incident label; displays an editable input when non-empty
SummarystringNoPre-filled incident summary; displays an editable textarea when non-empty
Location.LatitudenumberNoWGS84 latitude between -90 and 90
Location.LongitudenumberNoWGS84 longitude between -180 and 180
Location.CapturedAtUtcISO 8601 datetimeWith locationTime when the location was captured; it is stored separately from incident creation time

Example​

Typical Use Cases

  • Creating an incident from an external system
  • Deep-linking from a telephony or CRM system

Parameter names are case-insensitive. If a parameter occurs more than once, the last value is used. Unknown parameters are ignored. Location.Latitude, Location.Longitude, and Location.CapturedAtUtc form one value: if one is missing, Portal ignores the entire location. For a complete location, EMS validates the finite WGS84 coordinates and capture time. The location preview is read-only and the coordinates are not shown as text in the form.

Portal-created locations use the existing entered-caller domain path and are therefore always stored as Entered locations. Location.CapturedAtUtc is retained as the location capture time rather than the time the incident is created.

Open Incident​

Finds one incident and opens it. Callers that know the incident identifier pass it directly; callers that only know who called and when let the portal look the incident up.

This URL always redirects — to the incident detail when exactly one incident is identified, to the incident archive with the same search filters otherwise.

URL

/open-incident

Query Parameters​

NameTypeRequiredDescription
idUUIDNoIncident identifier
PhoneNumberstringNoCaller phone number to search for
DateISO 8601 dateNoDay the incident was created on

All parameters are optional; a parameter left empty counts as absent.

Resolution​

GivenResult
idIncident detail of that incident. PhoneNumber and Date are ignored
PhoneNumber and/or Date, exactly one incident matchesIncident detail of that incident
PhoneNumber and/or Date, no or several incidents matchIncident archive filtered by the same values
NothingIncident archive with its own default filters

Examples​

Typical Use Cases

  • Opening an incident from notifications
  • Direct links from third-party applications
  • A CAD system reopening the incident of a call it only knows the number and day of

Notes

  • This is the supported way to link to an incident. Which page the portal opens is an internal detail and may change; this URL is kept working across such changes.
  • A malformed id shows the portal's page not found screen; a well-formed id of an incident that does not exist shows the incident not found screen. Neither falls back to a search.
  • Date selects the whole day in the operator's local time zone, so pass a plain date such as 2026-07-09.
  • Without Date the search uses the archive's default window — yesterday and today. Pass Date to search any other day.
  • PhoneNumber matches the same way as in the archive, so a partial number matches too and can therefore return several incidents.
  • A malformed Date, or a search the portal could not run, ends on the archive, where the filters can be corrected and the search retried.

Incident Archive​

Opens the incident archive with filtering options.

URL

/incident-archive

Query Parameters​

NameTypeRequiredDescription
FromISO 8601 datetimeNoStart date and time
ToISO 8601 datetimeNoEnd date and time
PhoneNumberstringNoCaller phone number
CallerNamestringNoCaller name

Example​

Typical Use Cases

  • Reviewing incident history
  • Audit and reporting purposes

Integration Notes​

  • All URLs are intended to be opened in a web browser
  • Query parameters must be URL-encoded
  • Authentication and authorization are handled by the portal itself