In the Affiliates postbacks slice of Statistics, you can check the logs of the affiliates' postback. The article describes what to do if you see the wrong HTTP code in the HTTP code column.
Before you begin
There are different reasons why you might get the wrong status code in the HTTP code column. Here are the most common codes:
HTTP status code '0': the affiliate's server rejected the request, or the request did not reach the server.
Solution: double-check the Postback URL setup with the affiliate (if there are any typos, if the domain name is live and running).
HTTP status code '400' or '900': the server cannot process the request, because there's something it takes as a client error.
Solution: check all characters, encodings, and make sure the affiliate's server can accept them. Most probably, there's a technical error on the affiliate's side.
HTTP status code '404': Affise server did not find a current representation for the target resource or is not willing to disclose that one exists.
HTTP status code '500': the affiliate's server does not respond and does not accept the Postback URL on their side.
What to do with error status codes
If you cannot understand what the status code means, do the following:
Step 1. Test the Postback URL:
Copy the Postback URL.
Place the Postback URL in the browser address bar and click Enter.
In the response, you can see the same error as in statistics.
If you don't see the error in the browser, the problem is solved.
⚠️ You can use this method only if the affiliate's server accepts the Postback URL sent by the GET method.
Step 2. Do the following:
If you don't see the error in the browser, ask your affiliate why the affiliate's server responded with an error that time.
If you see the error in the browser, contact your affiliate directly to find out the reason for the error. Check the Postback URL with your affiliate, and make sure the Postback URL is correct and has no errors or typos.
📃 Related topics
Please contact the Affise Customer Support team regarding all raised questions via the e-mail: [email protected].