Properties
| Name | Type | Description |
|---|---|---|
| address_type_id | string | The Propexo unique identifier for the address type. This is required when updating the address |
| first_name | string | The first name associated with the lead |
| last_name | string | The last name associated with the lead |
| email_1 | string | The primary email address associated with the lead |
| address_1 | string | The first address line associated with the lead |
| address_2 | string | The second address line associated with the lead |
| city | string | The city associated with the lead |
| state | string | The state associated with the lead |
| zip | string | The zip code associated with the lead |
| target_move_in_date | object | The target move in date for the lead |
| desired_num_bedrooms | string | The desired number of bedrooms |
| desired_num_bathrooms | string | The desired number of bathrooms |
| desired_lease_term_in_months | string | The desired lease term in months of the lead |
| number_of_occupants | string | The number of occupants for the lead |
| notes | string | Notes associated with the lead |
| phone_1 | string | Primary phone number associated with the lead |
| phone_1_type | string | Type of the primary phone number |
| phone_2 | string | Secondary phone number associated with the lead |
| phone_2_type | string | Type of the secondary phone number |
| applicant_status | string | The status of the lead. This is optional and defaults to ACTIVE. |
JSON Schema
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"$id": "https://raw.githubusercontent.com/api-evangelist/propexo/main/json-schema/propexo-put-v1-leads-mri-leadid-request-schema.json",
"title": "PutV1LeadsMriLeadidRequest",
"x-generated": "2026-10-18",
"x-method": "derived",
"x-generator": "derive-json-schema.py",
"x-source": "openapi/_ae-authored/propexo-openapi-generated.yml#/components/schemas/PutV1LeadsMriLeadidRequest",
"type": "object",
"properties": {
"address_type_id": {
"type": "string",
"description": "The Propexo unique identifier for the address type. This is required when updating the address"
},
"first_name": {
"type": "string",
"description": "The first name associated with the lead"
},
"last_name": {
"type": "string",
"description": "The last name associated with the lead"
},
"email_1": {
"type": "string",
"description": "The primary email address associated with the lead"
},
"address_1": {
"type": "string",
"description": "The first address line associated with the lead"
},
"address_2": {
"type": "string",
"description": "The second address line associated with the lead"
},
"city": {
"type": "string",
"description": "The city associated with the lead"
},
"state": {
"type": "string",
"description": "The state associated with the lead"
},
"zip": {
"type": "string",
"description": "The zip code associated with the lead"
},
"target_move_in_date": {
"type": "object",
"description": "The target move in date for the lead"
},
"desired_num_bedrooms": {
"type": "string",
"description": "The desired number of bedrooms"
},
"desired_num_bathrooms": {
"type": "string",
"description": "The desired number of bathrooms"
},
"desired_lease_term_in_months": {
"type": "string",
"description": "The desired lease term in months of the lead"
},
"number_of_occupants": {
"type": "string",
"description": "The number of occupants for the lead"
},
"notes": {
"type": "string",
"description": "Notes associated with the lead"
},
"phone_1": {
"type": "string",
"description": "Primary phone number associated with the lead"
},
"phone_1_type": {
"type": "string",
"description": "Type of the primary phone number"
},
"phone_2": {
"type": "string",
"description": "Secondary phone number associated with the lead"
},
"phone_2_type": {
"type": "string",
"description": "Type of the secondary phone number"
},
"applicant_status": {
"type": "string",
"description": "The status of the lead. This is optional and defaults to ACTIVE."
}
}
}
Work with this as data
Every JSON Schema here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for schemas
4 MCP tools reach this
find_json_schemasBrowse and filter every JSON Schema in the catalog.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
This JSON Schema
curl "https://apis.io/api/v1/json-schemas/propexo-put-v1-leads-mri-leadid-request"
All schemas
curl "https://apis.io/api/v1/json-schemas?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.