The server has received the request headers and the client should proceed to send the request body.

{sourceType}: Continue

The requester has asked the server to switch protocols and the server has agreed to do so.

{sourceType}: Switching protocols

The server has received and is processing the request, but no response is available yet.

{sourceType}: Processing

{sourceType} success

The request has been fulfilled, resulting in the creation of a new resource.

{sourceType}: Created

The request has been accepted for processing, but the processing has not been completed. It might or might not be eventually acted upon, and may be disallowed when processing occurs.

{sourceType}: Accepted

The server is a transforming proxy that received a 200 OK from its origin, but is returning a modified version of the origin's response.

{sourceType}: Non authoritative information

The server successfully processed the request and is not returning any content.

{sourceType}: No content

{sourceType}: Reset content

The server is delivering only part of the resource (byte serving) due to a range header sent by the client. The range header is used by HTTP clients to enable resuming of interrupted downloads,or split a download into multiple simultaneous streams.

{sourceType}: Partial content

The message body that follows is an XML message and can contain a number of separate response codes, depending on how many sub-requests were made.

{sourceType}: Multi status

The members of a DAV binding have already been enumerated in a preceding part of the (multistatus) response, and are not being included again.

{sourceType}: Already reported

The server has fulfilled a request for the resource, and the response is a representation of the result of one or more instance-manipulations applied to the current instance.

{sourceType}: Im used

Indicates multiple options for the resource from which the client may choose (via agent-driven content negotiation).

{sourceType}: Multiple choices

This and all future requests should be directed to the given URI

{sourceType}: Moved permanently

The HTTP/1.0 specification (RFC 1945) required the client to perform a temporary redirect (the original describing phrase was "Moved Temporarily"), but popular browsers implemented 302 with the functionality of a 303 See Other. Therefore, HTTP/1.1 added status codes 303 and 307 to distinguish between the two behaviours. However, some Web applications and frameworks use the 302 status code as if it were the 303.

{sourceType}: Found

The response to the request can be found under another URI using a GET method.

{sourceType}: See other

Indicates that the resource has not been modified since the version specified by the request headers If-Modified-Since or If-None-Match.

{sourceType}: Not modified

The requested resource is available only through a proxy, the address for which is provided in the response.

{sourceType}: Use proxy

No longer used. Originally meant "Subsequent requests should use the specified proxy."

{sourceType}: Switch proxy

In this case, the request should be repeated with another URI; however, future requests should still use the original URI.

{sourceType}: Temporary redirect

The request and all future requests should be repeated using another URI.

{sourceType}: Permanent redirect

The server cannot or will not process the request due to an apparent client error (e.g., malformed request syntax, too large size, invalid request message framing, or deceptive request routing).

{sourceType}: Bad request

Similar to 403 Forbidden, but specifically for use when authentication is required and has failed or has not yet been provided

{sourceType}: Unauthorized

Your organisation has exceeded the plan limit. Please reach out to your account manager.

{sourceType}: Payment required

The request was valid, but the server is refusing action. The user might not have the necessary permissions for a resource.

{sourceType}: Forbidden

The requested resource could not be found but may be available in the future. Subsequent requests by the client are permissible.

{sourceType}: Not found

A request method is not supported for the requested resource; for example, a GET request on a form that requires data to be presented via POST, or a PUT request on a read-only resource.

{sourceType}: Method not allowed

The requested resource is capable of generating only content not acceptable according to the Accept headers sent in the request.

{sourceType}: Not acceptable

The client must first authenticate itself with the proxy.

{sourceType}: Proxy authentication required

The client did not produce a request within the time that the server was prepared to wait. The client MAY repeat the request without modifications at any later time.

{sourceType}: Request timeout

Indicates that the request could not be processed because of conflict in the request, such as an edit conflict between multiple simultaneous updates.

{sourceType}: Conflict

Indicates that the resource requested is no longer available and will not be available again.

{sourceType}: Gone

The request did not specify the length of its content, which is required by the requested resource.

{sourceType}: Length required

The server does not meet one of the preconditions that the requester put on the request.

{sourceType}: Precondition failed

The request is larger than the server is willing or able to process. Previously called "Request Entity Too Large".

{sourceType}: Payload too large

The URI provided was too long for the server to process. Often the result of too much data being encoded as a query-string of a GET request, in which case it should be converted to a POST request. Called "Request-URI Too Long" previously.

{sourceType}: Uri too long

The request entity has a media type which the server or resource does not support.

{sourceType}: Unsupported media type

The client has asked for a portion of the file (byte serving), but the server cannot supply that portion.

{sourceType}: Range not satisfiable

The server cannot meet the requirements of the Expect request-header field.

{sourceType}: Expectation failed

This HTTP status is used as an Easter egg in some websites, including Google.com.

{sourceType}: I am a teapot

The request was directed at a server that is not able to produce a response (for example because a connection reuse).

{sourceType}: Misdirected request

The request was well-formed but was unable to be followed due to semantic errors, perhaps data required by the backend is missing

{sourceType}: Unprocessable entity

The resource that is being accessed is locked.

{sourceType}: Locked

The request failed due to failure of a previous request (e.g., a PROPPATCH).

{sourceType}: Failed dependency

The client should switch to a different protocol such as TLS/1.0, given in the Upgrade header field.

{sourceType}: Upgrade required

The origin server requires the request to be conditional.

{sourceType}: Precondition required

The user has sent too many requests in a given amount of time. Intended for use with rate-limiting schemes.

{sourceType}: Too many requests

The server is unwilling to process the request because either an individual header field, or all the header fields collectively, are too large.

{sourceType}: Request header fields too large

A server operator has received a legal demand to deny access to a resource or to a set of resources that includes the requested resource. The code 451 was chosen as a reference to the novel Fahrenheit 451.

{sourceType}: Unavailable for legal reasons

An error occurred while processing the request.

{sourceType} : Internal server error

The server either does not recognize the request method, or it lacks the ability to fulfill the request.

{sourceType}: Not implemented

The server was acting as a gateway or proxy and received an invalid response from the upstream server.

{sourceType}: Bad gateway

The server is currently unavailable (because it is overloaded or down for maintenance).

{sourceType}: Service unavailable

The server was acting as a gateway or proxy and did not receive a timely response from the upstream server.

{sourceType}: Gateway timeout

The server does not support the HTTP protocol version used in the request.

{sourceType}: Http version not supported

Transparent content negotiation for the request results in a circular reference.

{sourceType}: Variant also negotiates

The server is unable to store the representation needed to complete the request.

{sourceType}: Insufficient storage

The server detected an infinite loop while processing the request.

{sourceType}: Loop detected

Further extensions to the request are required for the server to fulfill it.

{sourceType}: Not extended

The request requires network authentication.

{sourceType}: Network authentication required

You have failed to login too many times. Please wait 24 hours and try again or contact support.

Too many failed login attempts

Please check the input file and try again. If the problem persists please contact support.

Something went wrong when processing this batch report

You don't have permission to create a batch report. Please try re-authenticating and try again. If the problem persists please contact support.

Not authorised to create a batch report

You don't have permission to create a batch report. Please contact your admin or support if the problem persists.

Forbidden to create a batch report

We could not find this batch report. If you are sure this should exist please contact support.

Batch report not found

Please check the request and try again, or contact support. Required fields for a batch report are ISO code, company ID, currency & accounts type

Unprocessable entity for Batch Reports

You have sent too many requests recently, please wait a few minutes and try again. If problem persists please contact support.

Too many requests to batch reports

We couldn't process this batch report. There was an unrecoverable backend error. Please try again later or contact support if this problem persists.

Batch reports error

We are currently experiencing high volumes of traffic. Please try again in a few minutes or contact support if this problem persists

Batch reports fetching timeout

You should be redirected to the batch reports page. If you aren't, please click the link below.

Batch report successfully created

Success

Please check the request, and the structure of your input file and try again.

Something went wrong when processing your batch report

Not authorised access create a batch report

Forbidden to access create a batch report

We could not find a batch report with that ID. If you are sure this should exist please contact support.

Please check the request and try again, or contact support if the problem persists.

Unprocessable entity when creating a batch report

We couldn't fetch this batch report. There was an unrecoverable backend error. Please try again later or contact support if this problem persists.

Something went wrong trying to fetch this batch report. Please check the request and try again.

Issue fetching batch report

You don't have permission to access this batch report. Please try re-authenticating.

Not authorised to access batch report

Forbidden to access batch report

We could not find this batch report. If you are sure this should exist, please contact support.

Please check the request and try again. If problem persists please contact support.

Unprocessable entity for batch report

Too many requests for batch report

We couldn't process this batch report. There was an unrecoverable backend error. Please try again later or contact support if this problem persists

Batch reports fetching error

Batch report successfully cancelled

Something went wrong when cancelling this batch report

We couldn't cancel this batch report. There was an unrecoverable backend error. Please try again later or contact support if this problem persists

Please wait while we cancel this batch report.

Cancelling batch report

A new company loan was added successfully

Bad request

Not found

Please try again later or contact support if this problem persists.

Internal server error

Service unavailable

Validation error

Please check your formatting of your file, or try again later.

{loan_count} failed to add to companies

{loan_count} successfully added to companies.

See each loan on the relevant company page.

Company found

The {type} file should now be available in the downloads folder.

Download successful

Something went wrong...

There was an error submitting your feedback. Please try again later or contact support if this problem persists.

Feedback not submitted

Feedback submitted

Country code of the company found in Codat is not supported.

Country code not found

Your integration was a success. You should now be able to see it on the main report page.

Integration successful

Please check what you entered and try again.

Something went wrong when processing your Codat Integration.

You don't have permission to access Codat Integrations. Please contact your admin.

Forbidden to access Codat Integration

We could not find a Codat Integration. If you are sure this should exist, please contact support.

Codat Integration not found

Please check the request and make sure you entered everything correctly before trying again. Contact support if the problem persists.

Unprocessable entity for Codat Integration

Too many requests to Codat Integration

We couldn't process your Codat integrations request for this report. There was an unrecoverable backend error. Please try again later or contact support if this problem persists.

Codat Integration error

Codat Integration timeout

Please ensure the currency is a correct ISO standard.

Invalid currency

Do you have a large list of companies to analyse? Or want to integrate our technology into your own. Integrate with our API to achieve all of this and more.

With only a company number, automatically source data from millions of SME’s. Take this data and generate a credit risk report using Wiserfunding’s SME Z-Score.

Got a lot of reports to run? You bring the company IDs and we’ll run them and let you know when every single report has been compiled for you and your team.

Company Age

Company ID

Company Name

Please select the currency for the company.

Currency

Please add the industry sector for the company.

Industry Sector

Please select the ISO code for the company.

ISO Code

Access not allowed

Please add the number of employees for the company.

Number of Employees

Find SME’s that fit your risk criteria and enable your to grow your business sustainably. We provide all parameters required to complete a successful search.

Something not making sense? Can't quite the data or the details in the report you want? Talk to us today and we can help you resolve these issues and get you back on track.

Loading...