| POST | /api/roles/{FromRoleId}/associatedroles/safetystaff/{ToRoleId} | ||
|---|---|---|---|
| POST | /api/roles/{FromRoleId}/associatedroles/organisation/{ToRoleId} |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| FromRoleId | query | Guid | Yes | 'From' object ID in the connection. |
| ToRoleId | query | Guid | Yes | 'To' object ID in the connection. |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| ResponseStatus | form | ResponseStatus | No |
To override the Content-type in your clients, use the HTTP Accept Header, append the .json suffix or ?format=json
To embed the response in a jsonp callback, append ?callback=myCallback
The following are sample HTTP requests and responses. The placeholders shown need to be replaced with actual values.
POST /api/roles/{FromRoleId}/associatedroles/safetystaff/{ToRoleId} HTTP/1.1
Host: pfapi.pstpf.com.au
Accept: application/json
Content-Type: application/json
Content-Length: length
{"FromRoleId":"00000000-0000-0000-0000-000000000000","ToRoleId":"00000000-0000-0000-0000-000000000000"}
HTTP/1.1 200 OK
Content-Type: application/json
Content-Length: length
{"ResponseStatus":{"ErrorCode":"String","Message":"String","StackTrace":"String","Errors":[{"ErrorCode":"String","FieldName":"String","Message":"String","Meta":{"String":"String"}}],"Meta":{"String":"String"}}}