1Fetch Client API

CheckAccount

The following routes are available for this service:
GET	/checkaccount	Check account limit and remaining account amount

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

**CheckAccountResponse** Parameters:
Name	Parameter	Data Type	Required	Description
AccountLimit	form	decimal	No	The total monthly limit for account payments, will be negative if there is no limit
AccountRemaining	form	decimal	No	The amount that can still be used this month, will be negative if there is no account limit
AllowDataProcessing	form	bool	No	Shows if this account is allowed to place real orders or quotes

**ApiServiceResponse** Parameters:
Name	Parameter	Data Type	Required	Description
Description	form	string	Yes	Information about the response.
Heading	form	string	Yes	Heading or summary of the response.
WasSuccessful	form	boolean	Yes	Did the intended operation for this response complete successfully?

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 /checkaccount HTTP/1.1 
Host: 1fetch.api.client.prod.86degrees.com 
Accept: application/xml

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

<CheckAccountResponse xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/WebService.ClientServiceModel">
  <Description xmlns="http://schemas.datacontract.org/2004/07/WebService.ClientServiceModel.Base">String</Description>
  <Heading xmlns="http://schemas.datacontract.org/2004/07/WebService.ClientServiceModel.Base">String</Heading>
  <WasSuccessful xmlns="http://schemas.datacontract.org/2004/07/WebService.ClientServiceModel.Base">false</WasSuccessful>
  <AccountLimit>0</AccountLimit>
  <AccountRemaining>0</AccountRemaining>
  <AllowDataProcessing>false</AllowDataProcessing>
</CheckAccountResponse>