GalaxyMobile Client API

DeleteDependent

The following routes are available for this service:
DELETE	/dependent	Remove a dependent from a user's profile.

**DeleteDependent** Parameters:
Name	Parameter	Data Type	Required	Description
IdNumber	query	string	Yes	ID Number of the primary user you wish to add a dependent onto.
DependentId	query	int	Yes	The Id of the dependent in the Galaxy system you wish to delete.

**ApiServiceRequest** Parameters:
Name	Parameter	Data Type	Required	Description
ApiKey	form	string	Yes	The API Key required for authentication

**DeleteDependentResponse** Parameters:
Name	Parameter	Data Type	Required	Description
Dependents	form	List<DependentData>	No	Updated list of the user's dependents.

**ApiServiceResponse** Parameters:
Name	Parameter	Data Type	Required
Description	form	string	No
Heading	form	string	No
WasSuccessful	form	bool	No
ModelState	form	Object	No

**DependentData** Parameters:
Name	Parameter	Data Type	Required	Description
DependentId	form	int	Yes	Dependent's Galaxy Id used for referring to or deleting.
FirstName	form	string	Yes	Dependent's first name.
Surname	form	string	Yes	Dependent's surname.
MobileNumber	form	string	Yes	Dependent's mobile contact number.
Email	form	string	Yes	Dependent's email address.
IdNumber	form	string	Yes	Depdendent's ID number.

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

HTTP + JSON

The following are sample HTTP requests and responses. The placeholders shown need to be replaced with actual values.

DELETE /dependent HTTP/1.1 
Host: galaxymobile.api.client.prod.86degrees.com 
Accept: application/json

HTTP/1.1 200 OK
Content-Type: application/json
Content-Length: length

{"Dependents":[{"DependentId":0,"FirstName":"String","Surname":"String","MobileNumber":"String","Email":"String","IdNumber":"String"}],"Description":"String","Heading":"String","WasSuccessful":false,"ModelState":{}}