🏖️ Overview

In Livble's sandbox API,
some parts of the system may be mocked for a tenant upon the first /portal_info request made for their external_id.

In this guide we will go over those parts and explain how they get mocked.

📘

Are You Doing Manual QA in Sandbox?

This page is only relevant when doing manual QA that includes the Livble Widget and Experience in sandbox.

⏩ For all other purposes, this page can be skipped.

⚖️ Underwriting in Sandbox

The default behavior for sandbox is that all tenants will pass underwriting:white_check_mark:

This behavior can be overridden for individual tenants by their external_id.
📖 Refer to the this endpoint for more info.

⌛ Time Mocking in Sandbox

When making the first call to /portal_info for a tenant (by external_id),
the system's time may be mocked for that tenant.

📘

The Rent Window

Time is mocked in sandbox to ensure that tenants are always within the "Rent Window."
This is because Livble allows tenants to push rent only within the Rent Window.

📖 Learn more about the Rent Window

📌 Time Mocking Rules (Sandbox)

Time is mocked relative to when the first /portal_info call was made (in UTC).
It is mocked

• If the call was made after the 5th of the month → Time is mocked to the 1st of the next month.
• If the call was made between the 1st and 5th → Time remains unchanged.

ℹ️

Time is mocked per tenant

This means that each tenant has an independent system time. (by external_id)

ℹ️

Mocking applies only to the first/portal_info call.

Subsequent requests for the same external_id will not affect the system time for the tenant.

📋 Time Mocking Examples

The table below shows how time will be mocked when making a /portal_info request to the sandbox API.