Skip to content

Shop check API

You send a shop address and get back the same check as on our website: verdict, trust score and the reasons behind it. That lets you build, for example, a warning before payment or a pre-check for support.

POST api.fakeshop.ai/api/check
{ "url": "https://beispiel-shop.example" }
200 OK
{
  "domain": "beispiel-shop.example",
  "score": 82,
  "verdict": "safe",
  "checkedAt": "2026-09-28T10:15:32.000Z",
  …
}

Shown on the websiteNo major warning

Fictional example with a made-up address (.example).

Three steps to your first result

  1. Create an account

    Sign up for the developer portal. 100 credits are free every month, one check costs one credit.

  2. Create a key

    Create a key under API keys. It starts with fsk_live_ and is shown only once. Store it on your server as the environment variable FAKESHOP_API_KEY.

    export FAKESHOP_API_KEY="fsk_live_…"
  3. Send your first call

    POST the shop address to https://api.fakeshop.ai/api/check. On 200 the result is in the response, on 202 you poll the status until it is ready.

Your first API call

Request to https://api.fakeshop.ai/api/check and a complete example response. The code samples cover the full flow including status polling and read the key from the environment variable FAKESHOP_API_KEY.

RequestPOST /api/check
# 1. Request the check
curl -sS -X POST "https://api.fakeshop.ai/api/check?lang=en" \
  -H "Content-Type: application/json" \
  -H "x-api-key: $FAKESHOP_API_KEY" \
  -d '{"url":"https://beispiel-shop.example","checkType":"shop"}'

# 2. Only on status 202: poll the status with the jobId until "completed" or "failed".
# Recommended: after 2 s, then every 3 to 5 s, give up after 3 minutes. Polling costs no credit.
curl -sS "https://api.fakeshop.ai/api/check/status/JOB_ID"

Response200 OK

Point at a field name or tap it to see what the field contains.

{: "beispiel-shop.example",: 82,: "safe",: "shop",: true,: "2026-09-28T10:15:32.000Z",: { "level": 4, "label": "no findings" },: "high",: "fashion",: "none",: "Fictional example: no clear warning signs in the features checked.",: "Still pay with a method that offers buyer protection.",: [{: "tradeRegister",: "Commercial register",: "ok",: "positive",: ["The company from the legal notice is registered under the stated number."]},{: "domainAge",: "Domain age",: "ok",: "positive",: ["The domain has been registered for 47 months."],: { "ageMonths": 47 }}],: [{: "tradeRegister",: "Commercial register",: "ok",: "positive",: ["…"]}],: {"kind": "ai","text": "Automated assessment, partly generated with AI. No guarantee, not legal advice. Liability as set out in our terms of use.","aiInvolved": true,"regulation": "EU 2024/1689 Art. 50","termsUrl": "https://fakeshop.ai/en/terms","methodUrl": "https://fakeshop.ai/en/methodology#ki-einsatz"}}

verdictsafe | suspicious | danger | not_a_shop | unreachable

Overall assessment.

verdict is a code value. The website shows safe as “No major warning”. All values

Access and limits

  • 50

    Without a key

    checks per day and IP address, free of charge

  • 100

    With a key

    credits per month for free, then 1 credit per check from your balance

  • 20

    Short-term limit

    checks per minute and IP address, with or without a key (429 too_many_requests)

  • JSON

    Format

    JSON over HTTPS, texts in German or English

Base URL

Servers, cron jobs, WordPress
https://api.fakeshop.aiFor all calls from servers. This address goes straight to our server, without a Cloudflare check in front.
Browser on fakeshop.ai
https://fakeshop.ai/apiRemains valid and serves our own website. Calls from data centres receive a Cloudflare challenge there: HTTP 403 with the header cf-mitigated: challenge and an HTML page instead of JSON.

The key belongs on your server. Third-party websites cannot call the API from the browser (CORS), and a key in frontend code would be readable by every visitor.

Authentication with an API key

Send the key in the x-api-key header. The header name is case-insensitive. Without a key, requests use the free quota per IP address. You create the key in the developer portal. With an account, 100 credits per month are free. We answer integration questions at [email protected].

Header
x-api-key: fsk_live_…

We store keys only as a hash. A lost key therefore cannot be shown again. You delete it and create a new one. You can set a daily limit per key.

Quotas and limits

Without a key, 50 checks per day and IP address are free. With a key, each check deducts one credit. All requests are also subject to a short-term limit of 20 checks per minute per IP address.

StatusError codeWhen
401invalid_api_keyKey unknown, copied incorrectly or deleted.
402insufficient_creditsThe credit balance is used up.
429quota_exceededDaily quota without a key used up, or the daily limit you set on the key reached. Retry-After gives the seconds until midnight UTC.
429too_many_requestsMore than 20 checks per minute per IP address.

What costs a credit

Costs one credit
Every accepted check with a key: response 200, also for stored results (cached: true) and for the verdicts unreachable or not_a_shop, as well as response 202.
Free
Input errors (400), rejected requests (401, 402, 403, 429) and every status poll.
Refunded
If the check fails (500 scan_failed, 504 scan_timeout or status failed), the credit is returned automatically. The portal statement then shows a refund.
Remaining balance
After every paid check, the header X-RateLimit-Remaining states your balance in credits. The 100 free credits are added by the first check of a calendar month (UTC).

Systematic scraping or abuse of the free quotas is prohibited and may lead to the IP address being blocked. For higher limits or production integrations, write to [email protected].

Fetch the result

POST /api/check responds with 200 when a stored result exists. If a new check is needed, you get 202 with a jobId and fetch the result with GET /api/check/status/<jobId>. A new check usually takes a few seconds, longer for slow or blocking sites.

  1. POST /api/check

    Response 200 with the result, or 202 with { "status": "queued", "jobId", "domain" }.

  2. GET /api/check/status/<jobId>

    First poll after 2 seconds, then every 3 to 5 seconds. No key needed, costs no credit.

  3. Result or give up

    On completed, the result is in result, in the same shape as the 200 response. After 3 minutes without a result, stop and ask again later.

Status poll responses

HTTPBodyMeaning and next step
200{ "status": "queued" }Waiting in the queue. Keep polling.
200{ "status": "processing" }Being checked right now. Keep polling.
200{ "status": "completed", "result": { … } }Done. result contains the check result.
200{ "status": "failed", "errorCode": "scan_failed" }Check failed. Stop polling; the credit is refunded.
404{ "errorCode": "job_not_found" }jobId unknown or expired. Jobs remain retrievable for one hour after they finish. After that, send POST /api/check again; if the result is stored, it comes back with 200.

The status poll has its own short-term limit of 120 requests per minute and IP address. If you check many shops at once, poll the open jobs one after another.

What the verdict values mean

The verdict field always returns an English code value. Our website shows verdict words for it; safe appears as “No major warning”, never as “safe”. A code value is not a recommendation, it summarises the features checked as of the check date.

verdictShown on the website*Meaning
safeNo major warningNo substantiated warning signs in the features checked. Not a recommendation and not a guarantee.
suspiciousSuspiciousA mixed picture: some features count in the shop’s favour, others are missing or unclear.
dangerDangerSeveral serious warning signs or an entry on an evaluated warning list.
not_a_shopNot a shopThe address does not lead to an online shop. score is null.
unreachableNot verifiableThe site could not be reached. score is null.

Automated assessment, partly generated with AI. No guarantee, not legal advice. Liability as set out in our terms of use. How we check.

API reference

POST /api/check accepts these parameters.

ParameterLocationTypeRequiredDescription
urlBodystringYesThe shop or website URL to check.
checkTypeBodyshop | websiteNoCheck profile. Default is shop. website allows a credibility check when the URL is not an online shop.
forceBodybooleanNoForces a new check instead of a stored result. Runs without the queue and only responds with the finished result, so it can take considerably longer. Costs one credit like any check.
langQueryde | enNoLanguage of the text fields (summary, recommendation, reasons). Alternatively via Accept-Language. Default is de.

GET /api/check/status/<jobId> only takes the jobId from the 202 response in the path. No key is needed there.

Machine-readable description (OpenAPI 3.1) for generating clients: /api/openapi.json

Try it with your own key

The console sends real requests to POST /api/check, polls the status on 202 and shows status code, headers and body unchanged. Your key stays in this browser: it is only sent as a header to fakeshop.ai and is kept at most in this tab’s storage.

Request

Only sent as the x-api-key header to fakeshop.ai. Without a key, the free quota of your IP address applies.

checkType
lang

Without a key, the request counts towards the free quota of your IP address. Esc cancels.

Response

Ready
  1. Request
  2. Status poll
  3. Result

No request sent yet.

Public endpoints without a key

The two endpoints below are public. The button calls them from your browser and shows the response unchanged.

Recorded response from 3 October 2026 (not fetched yet)

200 OK
{
  "totalChecks": 79554,
  "fakeShopsDetected": 37513,
  "cleanShops": 42036,
  "checksToday": 0,
  "fakeQuota": 0.4715413429871534,
  "updatedAt": "2026-10-03T12:10:29.861Z"
}

Equivalent to this call: curl "https://api.fakeshop.ai/api/stats"

The numbers and domains in the live response change with our data. For fields and status codes, follow the reference above.

About the stats response: fakeQuota is fakeShopsDetected divided by totalChecks (0.47 equals 47%). checksToday counts the checks since UTC midnight, so the value is close to 0 shortly after midnight.

Caching and privacy

Stored results

We store every result per domain and serve it again while it is valid: unclear results (suspicious) and special cases for up to 7 days, clear verdicts (safe, danger) for up to 90 days, manually classified domains for up to 365 days. If a site was last unreachable, the next request checks it again.

cached: true and checkedAt show whether and when the check ran. If you cache results yourself, base their validity on checkedAt. force: true forces a new check.

Privacy

Send only the shop address. Paths and parameters containing your customers’ data, such as email addresses, order numbers or tokens, do not belong in url.

Check results refer to the shop and are public: a result page for a checked domain may appear on fakeshop.ai.

For every key we store a hash instead of the plain text, the number of requests per day and, per day, the requesting IP addresses with counts. You see this overview in the portal under API keys. Privacy policy.

Credit prices

One credit equals one check. You buy credits once in the developer portal, without a subscription. Prices as of: 02/10/2026.

  • Starter

    100credits

    €4.90

    €0.049 per check

  • Standard

    1,000credits

    €24.00

    €0.024 per check

  • Pro

    5,000credits

    €89.00

    €0.018 per check

  • Business

    25,000credits

    €299.00

    €0.012 per check

Free: 100 credits per month with an account, 50 checks per day and IP without a key.

Changes and version

The API has one response shape without a version parameter. New fields may be added. Treat unknown fields as optional and your integration stays unaffected.

    • Base URL https://api.fakeshop.ai for server calls.
    • Input errors (400) no longer cost a credit. New error codes invalid_url, invalid_json, scan_timeout and origin_not_allowed.
    • Failed checks are refunded automatically.
    • Status poll with its own short-term limit of 120 requests per minute and IP address.
    • Console on this page and in the portal to try the API with your own key.
    • OpenAPI description at /api/openapi.json.

Further public endpoints

These endpoints need no key and cost no credits.

  • GET /api/warnlist
    Parameters

    limit (default 50, max 1000), offset

    Returns

    Domains on the warning list with category and check date

  • GET /api/fakeshops
    Parameters

    limit (default 50, max 200)

    Returns

    Listed shops (warning list or assessment Danger) with product category

  • GET /api/stats
    Parameters

    none

    Returns

    Totals: domains checked, shops listed, timestamp

  • GET /api/iban-check
    Parameters

    iban (max. 30 requests per minute and IP)

    Returns

    Whether there are approved reports for this IBAN, count, date of the first

A key for production use

You create the key yourself in the developer portal; 100 credits per month are free. Integration questions, higher volumes and bug reports go to [email protected].

Go to developer portal