Frequently Asked Questions
Everything we get asked most often. Can't find your answer? Write to support@restoapi.org.
How do I sign up?
Enter your email on /login, we send a 6-digit code via email, you enter it back. No password to remember, no card to add. $0.50 free trial is credited on first signup — enough for 3+ Basic tasks.
How long does signup take?
Under 30 seconds. Email → code → done. Session cookie is valid 90 days with sliding refresh, so you stay logged in.
Do I need a credit card to try?
No. Free trial is automatic. You only need a top-up when you've used your $0.50 credit and want to keep going.
What's the minimum top-up?
$5. Bank transfer for now — write to support. Stripe (card payments) coming in v2.
What if a job fails?
Automatic refund. Your transaction history shows the original charge AND the refund transaction with the failure reason. You never pay for broken data.
Can I get a discount?
Yes — include_media=false in your job options gives you −30% off any tier. Discounts auto-applied, breakdown returned in the response.
Volume discounts?
For 10k+ tasks/month, write to support. We can talk custom pricing or a dedicated worker pool.
How does billing work technically?
Charge happens before the job goes to queue — if your balance is too low, you get HTTP 402 immediately. Refund happens automatically if the worker fails. Every transaction has a unique ID and is fully auditable in Billing.
How fresh is the data?
Real-time. Every job hits the source live. We don't cache or pre-scrape — the moment you call, that's the snapshot you get. Restaurant changed prices 5 minutes ago? You'll see new prices.
Which platforms are supported?
Today: Wolt (60+ countries, full multilingual) and Google Maps (any restaurant). Coming next: UberEats, Bolt Food, DoorDash.
Which countries?
Any country where Wolt operates: Estonia, Latvia, Lithuania, Finland, Sweden, Norway, Denmark, Iceland, Germany, Austria, Croatia, Slovenia, Hungary, Slovakia, Czech Republic, Poland, Greece, Albania, Kosovo, Serbia, North Macedonia, Georgia, Armenia, Azerbaijan, Israel, Kazakhstan, and more. All verified end-to-end.
What about RTL languages?
Full support. Hebrew + Arabic restaurants in Israel return correct text in translations.he and translations.ar. Your UI handles RTL rendering.
Photos archived locally?
Yes — in the full_media tier. Every dish/cover/logo photo is downloaded and packed into the ZIP under photos/. De-duplicated by content hash, so if 5 dishes share the same photo, you store it once.
Are translations always available?
Depends on the restaurant. If Wolt offers menu in en + de + uk, you get all three in translations.{en,de,uk}. autotranslated: true/false tells you which are manual vs machine.
Can I send many URLs at once?
Yes — POST to /v1/jobs/batch with up to 200 URLs per call. Each becomes a separate job_id under one common batch_id. Aggregate progress at /v1/batches/{id}.
What's the API rate limit?
60 requests per minute per API key by default. Need more? Write to support.
How long is the archive available?
48 hours from completion. Signed download URLs include an expires_at timestamp. After 48h the archive is auto-deleted; just re-run the task if you need it again.
API key vs cookie session?
Cookie session = browser, 90-day sliding refresh, automatic after OTP-login. API key (rk_live_*) = for scripts/CI/Apify. Same permissions, same balance. Create unlimited keys, revoke anytime.
Is there an Apify actor?
Coming soon. Thin proxy actor — paste your rk_live_* API key into the input, run the actor, get the archive URL back. Billed via Apify Pay-Per-Event. More details on /about.
Webhook callbacks?
Coming in v2 — set webhook_url in options, we POST {job_id, status, archive_url} when complete. For now: polling.
What about GDPR?
We store: your email, session ID, transaction history. No tracking pixels, no third-party analytics, no Google Analytics. Logout = session revoked. Email-delete request: write to support.
Is this legal?
Publicly accessible restaurant data — same content any browser sees. We respect rate limits, never bypass authentication, and process responsibly. Use the data responsibly on your end. See Terms.
Can I use the data commercially?
Yes. Standard rules apply — don't redistribute Wolt's photos as your own, attribute where appropriate. Restaurant data is factual.
Do you track me?
No analytics. No cookies beyond your session cookie. Server logs (IP, user agent) kept 7 days for security only.
Still have a question?
Send it to support@restoapi.org — we usually reply within a day. For urgent integrations, mention "API integration" in the subject and we'll prioritise.