Get a notification profile
Returns the details of a single notification profile by its identifier.
Path parameters
The id of the resource.
Response
A Notification Profile response
Example response
{
"data": {
"id": "12455643-3cf1-4683-ad23-1cd32f7d5e0a",
"created_at": "2019-10-15T10:07:15.527Z",
"updated_at": "2019-10-15T10:07:15.527Z"
}
}Changes
Changed in 3 of the 99 revisions of this API.20
- ▲
the
//response's property type changed fromstringtointeger, and format from no format toint32for statusresponse-property-type-changed
- ▲
the
//response's property type changed fromstringtointeger, and format from no format toint32for statusresponse-property-type-changed
- ▲
the
//response's property type changed fromstringtointeger, and format from no format toint32for statusresponse-property-type-changed
- ▲
the
//response's property type changed fromstringtointeger, and format from no format toint32for statusresponse-property-type-changed
- ▲
the
///response's property format changed fromjson-pointerto no format for statusresponse-property-type-changed
- ▲
the
///response's property format changed fromjson-pointerto no format for statusresponse-property-type-changed
- ▲
the
///response's property format changed fromjson-pointerto no format for statusresponse-property-type-changed
- ▲
the
///response's property format changed fromjson-pointerto no format for statusresponse-property-type-changed
This revision also has 34 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog
- ▲
- ▲
the
//response's property type changed fromintegertostring, and format fromint32to no format for statusresponse-property-type-changed
- ▲
the
//response's property type changed fromintegertostring, and format fromint32to no format for statusresponse-property-type-changed
- ▲
the
//response's property type changed fromintegertostring, and format fromint32to no format for statusresponse-property-type-changed
- ▲
the
//response's property type changed fromintegertostring, and format fromint32to no format for statusresponse-property-type-changed
This revision also has 64 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog
- ▲
- ▲
the
//response's property type changed fromstringtointeger, and format from no format toint32for statusresponse-property-type-changed
- ▲
the
//response's property type changed fromstringtointeger, and format from no format toint32for statusresponse-property-type-changed
- ▲
the
//response's property type changed fromstringtointeger, and format from no format toint32for statusresponse-property-type-changed
- ▲
the
//response's property type changed fromstringtointeger, and format from no format toint32for statusresponse-property-type-changed
- ▲
the
///response's property format changed fromjson-pointerto no format for statusresponse-property-type-changed
- ▲
the
///response's property format changed fromjson-pointerto no format for statusresponse-property-type-changed
- ▲
the
///response's property format changed fromjson-pointerto no format for statusresponse-property-type-changed
- ▲
the
///response's property format changed fromjson-pointerto no format for statusresponse-property-type-changed
This revision also has 41 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog
- ▲
Of the 99 revisions, 1 has no diff computed.