Sandbox

The sandbox is a separate copy of the platform where you build and test your integration without touching real listings. It runs the same code as production, so the rules, error codes, moderation, and webhooks behave the same.

​

Different keys for each environment

Accounts, keys, listings, and webhooks are separate between the two environments. A key hsr_test_ does not work in production and vice versa. When switching to production, create a new key from your account on housera.ro and reconfigure your webhooks there.

​

What you can test

• Field mapping: send listings of all types you have in the system to POST /listings/validate and fix what you receive in errors[] and warnings[].
• Full flow: creation, photos, editing, pause, reactivation, sold, deletion.
• Webhooks: the “Send a test” button in Settings → API sends a signed webhook.test event to check your endpoint and signature.
• Recovery: stop your endpoint for a while, then recover lost events from GET /events.
• Conflicts: edit a listing in the sandbox portal, then send an edit via API with old If-Match and check the fact that you receive 412.

​

Test data

• Use fictitious data: real addresses and coordinates of the city are fine, but without names, phone numbers, or emails of real persons.
• For photos, use images you have the right to use, served from a public HTTPS URL or uploaded directly.
• The emails that the sandbox would send (confirmations, moderation notifications) do not reach real recipients.

​

Moderation in the sandbox

New listings enter moderation here as well, with status pending, just like in production. They remain in this state until they are approved or rejected. Your integration should handle a listing pending as a normal state that may last.