Get a key
The account owner opens Settings, finds API access and makes a key. The key is shown once, so copy it then. You can have up to 10 active keys and revoke any of them at any time. A key can only read; it cannot add, change or delete anything.
Make a request
Send the key in an Authorization header. Every request is a GET to drlandlord.app.
curl https://drlandlord.app/api/v1/properties \ -H "Authorization: Bearer dl_live_your_key_here"
Answers are JSON in this shape: { "data": [...], "total": 12, "limit": 50, "offset": 0 }. Use limit (1 to 200, default 50) and offset to page through. Money is in cents. Dates look like 2026-10-31.
What you can read
GET /api/v1/properties lists properties: name, address, units, rent, type and status. Add include_archived=1 to include archived ones.
GET /api/v1/tenants lists tenants: name, unit, email, phone, lease end, rent due day, monthly rent, deposit and status. Filter with property_id; add include_archived=1 for past tenants.
GET /api/v1/payments lists payments, newest first: amount, status, date, method, fees, and any refund. Filter with tenant_id, from, to (dates) and status (good, warn or critical).
Limits and errors
Each key can make 120 requests a minute. Past that you get a 429 with a Retry-After header. A missing or wrong key gets a 401. A key stops working the moment you revoke it. Errors come back as { "error": "..." }.
Keep it safe
Anyone with a key can read your tenants’ names, emails and phone numbers. Do not paste a key into a shared document or a public repository. If one leaks, revoke it in Settings and make a new one.