GuidesDiscussions
Discussions

Discussions

Ask a Question
Back to all

Importer: /api/v1/property/ coverage, leads, and callback

2 days ago by Gus Mahfoud

Hello. We are integrating our management system with the Property Importer (POST /property_importer/), and we have a few questions before running the first import.

  1. LISTING COVERAGE. We understand the import file is treated as the complete inventory, and that properties we don't want touched can be included as stubs with only reference_code + an updated_at earlier than the one registered. To build those stubs we need to enumerate ALL properties in the account. Does /api/v1/property/ with the company API key return every property regardless of status (reserved, not available, display_on_web = false, unpublished)? Or only publishable ones? If it filters, which endpoint or parameter gives us the complete inventory with each property's reference_code?

  2. REFERENCE_CODE MATCHING. Is the reference_code returned by the read API exactly the same value the importer matches on (same casing/format)? We want to confirm there is no separate internal code.

  3. EMPTY FILE. What happens if the import file is an empty array ([])? Is it accepted (deactivating everything), or rejected?

  4. CALLBACK_URL. Is callback_url mandatory on the trigger POST, or can it be omitted? If our webhook is temporarily down, is the report retried?

  5. READING LEADS. Portal inquiries land inside the Tokko account. Is there any API endpoint, webhook, or export to read those inquiries/leads programmatically? We want to sync them into our own CRM.

  6. LOCATION FOR ECUADOR. We send geo_lat/geo_long and no location id. Does location resolution from coordinates work for Ecuador (Quito, Guayaquil, etc.)? If resolution fails, does the property really default to location 51400 (Capital Federal, Argentina) even for an Ecuadorian company, and how should we avoid that?

  7. PRODUCER_USER. If we send producer_user emails that don't exist in the account, the importer creates those users. Does an auto-created user consume a paid seat or have billing implications? And do leads for that property route to the producer inside Tokko?

  8. TRIGGER FREQUENCY. Is there a rate limit on POST /property_importer/? If several imports are triggered in a short window, are they queued and processed in order?

Thank you!