Service

GetNeededNectVerification

The following routes are available for this service:
GET	/NectVerification/Check

**GetNeededNectVerification** Parameters:
Name	Parameter	Data Type	Required	Description
UserId	query	long	No

**UserNectResponse** Parameters:
Name	Parameter	Data Type	Required
AccountId	form	long	No
NectVerificationNeeded	form	bool	No
UserId	form	long	No
UserEMail	form	string	No
NectVerificationSuccess	form	bool	No
NectCaseUID	form	string	No
NectVerificationTimeStamp	form	DateTime?	No

To override the Content-type in your clients, use the HTTP Accept Header, append the .xml suffix or ?format=xml

HTTP + XML

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

GET /NectVerification/Check HTTP/1.1 
Host: api.helferportal.de 
Accept: application/xml

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

<UserNectResponse xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/HelferPortal.ApiModel.Common">
  <AccountId>0</AccountId>
  <NectCaseUID>String</NectCaseUID>
  <NectVerificationNeeded>false</NectVerificationNeeded>
  <NectVerificationSuccess>false</NectVerificationSuccess>
  <NectVerificationTimeStamp>0001-01-01T00:00:00</NectVerificationTimeStamp>
  <UserEMail>String</UserEMail>
  <UserId>0</UserId>
</UserNectResponse>