/accounts

GET /accounts/me/rejecttypes 1065 (ready) Gets the file reject types
This request requires authentication headers to be set. See HTTP Headers below.
Gets the file reject types that an account can make use of if he decides to reject a file.
Response field details :
Name Type Description
id integer The ID of the reject type
rejectionTextstringThe short description of the rejection
descriptionstringThe long description of the rejection and in which cases it can be used
The response of this request has a Content-Type of application/json.
Any request should supply an Accept header explicitly accepting this Content-Type, e.g. Accept: application/json.
When an Accept header is missing, or it has another value, 406 Not Acceptable is returned.

HTTP Headers

Name Type Required Default value Description
X-Client-Token string true The token identifying the client of the API
X-Session-Token string true The token identifying the session of the current user

Example response

[{
	"id": 6,
	"rejectionText": "Test_Rejection_type_5",
	"description": "Some details are incorrect",
	"_type": "GetRejectTypeResponseBody"
},
{
	"id": 7,
	"rejectionText": "Test_Rejection_type_6",
	"description": "Test Reason 6",
	"_type": "GetRejectTypeResponseBody"
},
{
	"id": 5,
	"rejectionText": "Test_Rejection_type_4",
	"description": "File is corrupt",
	"_type": "GetRejectTypeResponseBody"
}] 

Errors

The following 400 Bad Request errors can be expected, and should be handled by the developer:

Code Message Example
missing_header A required header was not supplied
{
  "code": "missing_header",
  "message": "A required header was not supplied.",
  "headerName": "X-Client-Token"
}

Status Codes

200 OK
The resource was found
400 Bad Request
The request could not be understood by the server due to malformed syntax. The client SHOULD NOT repeat the request without modifications
401 Unauthorized
The request requires user authentication
403 Forbidden
The client has no permission to access the resource
404 Not Found
The resource was not found
406 Not Acceptable
The requested resource is only capable of generating content not acceptable according to the Accept headers sent in the request
408 Request Timeout
The request timed out
410 Gone
The requested resource is no longer available and will not be available again
500 Internal Server Error
The server encountered an unexpected condition which prevented it from fulfilling the request
503 Service Unavailable
The server is currently unavailable (because it is overloaded or down for maintenance)
GET /accounts/me/rejecttypes/{language} 1078 (ready) Gets the file reject types in specified language
This request requires authentication headers to be set. See HTTP Headers below.
Gets the file reject types in specified language for session account
The response of this request has a Content-Type of application/json.
Any request should supply an Accept header explicitly accepting this Content-Type, e.g. Accept: application/json.
When an Accept header is missing, or it has another value, 406 Not Acceptable is returned.

HTTP Headers

Name Type Required Default value Description
X-Client-Token string true The token identifying the client of the API
X-Session-Token string true The token identifying the session of the current user

URL Parameters

Name Type Required Description Example(s)
language string true Language (2 Letter ISO code) to provide Rejection reasons onto NL

Example response

[{
	"id": 6,
	"rejectionText": "Test_Rejection_type_5",
	"description": "Some details are incorrect",
	"_type": "GetRejectTypeResponseBody"
},
{
	"id": 7,
	"rejectionText": "Test_Rejection_type_6",
	"description": "Test Reason 6",
	"_type": "GetRejectTypeResponseBody"
},
{
	"id": 5,
	"rejectionText": "Test_Rejection_type_4",
	"description": "File is corrupt",
	"_type": "GetRejectTypeResponseBody"
}] 

Errors

The following 400 Bad Request errors can be expected, and should be handled by the developer:

Code Message Example
missing_header A required header was not supplied
{
  "code": "missing_header",
  "message": "A required header was not supplied.",
  "headerName": "X-Client-Token"
}

Status Codes

200 OK
The resource was found
400 Bad Request
The request could not be understood by the server due to malformed syntax. The client SHOULD NOT repeat the request without modifications
401 Unauthorized
The request requires user authentication
403 Forbidden
The client has no permission to access the resource
404 Not Found
The resource was not found
406 Not Acceptable
The requested resource is only capable of generating content not acceptable according to the Accept headers sent in the request
408 Request Timeout
The request timed out
410 Gone
The requested resource is no longer available and will not be available again
500 Internal Server Error
The server encountered an unexpected condition which prevented it from fulfilling the request
503 Service Unavailable
The server is currently unavailable (because it is overloaded or down for maintenance)