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
| Name | Type | Required | Description |
|---|---|---|---|
RequestedIncidentId | UUID | Yes | ID of the new incident |
PhoneNumber | string | Yes | Caller phone number |
Example
Typical Use Cases
- Creating an incident from an external system
- Deep-linking from a telephony or CRM system
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
| Name | Type | Required | Description |
|---|---|---|---|
id | UUID | No | Incident identifier |
PhoneNumber | string | No | Caller phone number to search for |
Date | ISO 8601 date | No | Day the incident was created on |
All parameters are optional; a parameter left empty counts as absent.
Resolution
| Given | Result |
|---|---|
id | Incident detail of that incident. PhoneNumber and Date are ignored |
PhoneNumber and/or Date, exactly one incident matches | Incident detail of that incident |
PhoneNumber and/or Date, no or several incidents match | Incident archive filtered by the same values |
| Nothing | Incident archive with its own default filters |
Examples
- https://portal.ng-sos.com/open-incident?id=21c79f3e-75fe-43ee-a4e0-bc7690c7cedd
- https://portal.ng-sos.com/open-incident?PhoneNumber=%2B420775123456&Date=2026-07-09
- https://portal.ng-sos.com/open-incident?PhoneNumber=%2B420775123456
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
idshows the portal's page not found screen; a well-formedidof an incident that does not exist shows the incident not found screen. Neither falls back to a search. Dateselects the whole day in the operator's local time zone, so pass a plain date such as2026-07-09.- Without
Datethe search uses the archive's default window — yesterday and today. PassDateto search any other day. PhoneNumbermatches 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
| Name | Type | Required | Description |
|---|---|---|---|
From | ISO 8601 datetime | No | Start date and time |
To | ISO 8601 datetime | No | End date and time |
PhoneNumber | string | No | Caller phone number |
CallerName | string | No | Caller 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