POST
/
api
/
v1
/
employees
/
{employee_id}
/
member_requests
/
termination
curl --request POST \
  --url https://fulfillment.noyo.com/api/v1/employees/{employee_id}/member_requests/termination \
  --header 'Content-Type: application/json' \
  --data '{
  "employee_id": "6dc22bed-27fc-458c-b732-bdaf5b5a1031",
  "last_work_date": "2020-01-15",
  "reason": "voluntary",
  "signature_date": "2020-01-01"
}'
{
  "body": {
    "employee_id": "6dc22bed-27fc-458c-b732-bdaf5b5a1031",
    "last_work_date": "2020-01-15",
    "reason": "voluntary",
    "signature_date": "2020-01-01"
  },
  "created": 1557512389,
  "employee_id": "6dc22bed-27fc-458c-b732-bdaf5b5a1031",
  "id": "dd9a1813-34f7-4c7e-86bc-f041f2cbd9a1",
  "modified": 1564440756,
  "request_type": "termination",
  "status": "processing",
  "transactions": [
    "f4ecdaa5-e019-4a24-98c7-2caee9a58ccd"
  ]
}

The Member Request workflow is now deprecated in favor of using Member Snapshot

Path Parameters

​
employee_id
string
required

The unique identifier of the employee related to the member request

Example:

"6dc22bed-27fc-458c-b732-bdaf5b5a1031"

Body

application/json

Response

201 - application/json
Successful Response - Returns the new Member Request

The response is of type object.