MagicDoorAPI
SupportOpen MagicDoor
Application rental history

Resend a landlord verification

Sends the landlord the same verification email again, reusing the existing access code so any link they already have keeps working. Only legal while the entry's verification is pending. Requires the rental_applications:write permission.

POST
https://services.magicdoor.com/leasing/company-portal/rental-applications/{applicationId}/residential-history/{residentialHistoryId}/resend-verification

Authorization

Authorizationstringrequired
Bearer token — Send your API token in the Authorization header as Bearer <token>. Requests without a valid token are rejected with 401 Unauthorized.

Path parameters

applicationIdstringrequired

The rental application to work with. A Snowflake id, sent as a decimal string.

example: 1830472847398404096
residentialHistoryIdstringrequired

The address entry to work with. A Snowflake id, sent as a decimal string.

example: 1832746629384756480

Response

204 · The email was sent again. The response has no body.

400 · The entry's verification is not `pending`, it has no access code on file, or the landlord email address is missing or not valid.

401 · The access token is missing, expired, or not valid.

403 · The caller is authenticated but does not hold the `rental_applications:write` permission.

404 · No address entry with this id exists on this rental application, or the rental application itself was not found.

Allowed in every application status

This is not gated on the application's status — it works on a draft, on a submitted application, and on a retracted one. Only the applicant-facing portal locks an application once it is submitted.