Skip to content
Sign in Open an account
Open an account Sign in
Documentation
Reference 2 pages

Reference

Error responses

What each status code from the wall means, and what the wall's own screens mean.

On this page 6 sections
  1. HTTP responses from the wall
  2. Screens, not status codes
  3. The consent screen
  4. Click responses
  5. Postback responses
  6. Reporting one

There is no numeric error-code vocabulary to learn. The wall answers with HTTP status codes and with two named screens.

HTTP responses from the wall#

Code Cause Fix
400 userid missing, too long, or containing disallowed characters Max 191 characters, letters, digits and _ - . @ :. See URL parameters
403 sig missing or wrong on an app that requires signed wall URLs Signed URLs
404 appid does not exist Check the App ID. It is the public one, not the secret
429 Rate limit Rate limits. Sustained hits also raise a fraud flag

Screens, not status codes#

Two conditions render a page with a 200 rather than an error, because they are answers to the user rather than faults in the request.

"Unavailable" — the app is not active, or your publisher account is not approved. Check both in the dashboard. Also shown to an end user who has been banned for fraud on your account.

"No offers available in your country right now" — the request was fine and nothing passed the eligibility filter. Almost always a blacklist that is too broad, or a country with thin inventory. Turn on test mode and try a country override to confirm which.

Not an error. In the EU-27, the UK and the EEA, a user with no stored consent gets the consent screen. Declining shows an explanation and no offers, and no click is possible.

Click responses#

/click/{offer} answers with a 302 to the network's tracking URL, or redirects to a blocked screen when a fraud rule stops the click.

Only the link the wall renders works. Each offer's Start button carries a short-lived signature issued for that end user and that offer, so a click URL built by hand, copied to another user, or left open for hours shows the blocked screen. Reloading the offer issues a fresh link.

A blocked click still writes a row on our side, with the reason. It is visible in your Clicks report — a blocked click that produced no record would be a support question nobody could answer.

Never a 301: the tracking URL contains a single-use click ID, and a browser that cached a permanent redirect would send every later click to the first click's URL and attach the conversion to the wrong row.

Postback responses#

These run the other way — they are what your endpoint returns to us. Everything outside 2xx is a failure and is retried. See Retries & failure.

Reporting one#

Every response you can get from us is reproducible from a URL. When you open a ticket, send the full wall URL or the trans_id, not a screenshot of the screen — the screen is the same for six different causes.