...
| Excerpt | ||
|---|---|---|
| ||
Allows a user to manipulate a person's |
...
system |
...
of |
...
record |
...
record |
...
via |
...
a |
...
real-time |
...
API. |
...
SoR Person
The SoR Person resource as defined by the Open Registry is identified by the following URI:
| Code Block |
|---|
/people/sor/{sorSource}/{sorId}
{code}
|
Note:
...
{sorSource
...
}
...
is
...
something
...
like
...
Registrar,
...
HR,
...
etc.
...
Delete
...
SoR
...
Person
...
| Code Block |
|---|
HTTP DELETE /people/sor/{sorSource}/{sorId}
{ |
| Code Block |
|---|
HTTP DELETE /people/sor/{sorSource}{sorId}?mistake=true {code] #* HTTP response entity body: #** empty (in case of 204) #* HTTP status codes: #** 204: the system of record person resource has been successfully deleted #** 400: if one of the required arguments is missing #** 404: the system of record person resource is not found #** 401/403: the authentication/authorization fails #** 500: any other server error that |
- HTTP response entity body:
- empty (in case of 204)
- HTTP status codes:
- 204: the system of record person resource has been successfully deleted
- 400: if one of the required arguments is missing
- 404: the system of record person resource is not found
- 401/403: the authentication/authorization fails
- 500: any other server error that occurs
- HTTP response entity body: