Repliers Help Center
Go to website
Back
Articles on:Optimization
Optimize API queries for performance.

Categories

  • Pricing
  • Getting Started
  • Data Normalization
  • Image Insights
  • Coding with AI Tools
  • Model Context Protocol (MCP)
  • Extra Questions
  • General
  • Developer Portal
  • Property Search & Filtering
  • Property Photos
  • Property History
  • Market Reports & Analytics
  • Webhooks
  • Data Security
  • Favorites & Saved Listings
  • Saved Searches
  • Property Estimates
  • Messaging & Alerts
  • Display Considerations
  • Optimization
  • Data Access
  • Compliance
  • Optimizing API Requests with the "fields" Parameter
    Explains how the fields parameter limits listing responses to the comma-separated properties an application actually uses, reducing payload size, parsing work, bandwidth and latency, and encourages different field sets for search cards, map views and detail pages rather than repeatedly downloading the full listing model; Related terms include “fields parameter,” “return only selected properties,” “smaller JSON response,” “reduce bandwidth,” “improve latency,” “search-card fields,” “map-view fields,” and “detail-page fields”; Its focus is response projection and payload optimization, not filtering which listings match.Few readers
  • Client-Side API Keys Developer Guide
    Details how to create client-side API keys for direct browser or mobile requests through the dedicated client endpoint, restrict them to approved domains and supported endpoints, combine them with firewall protection and forwarded user IPs, monitor their exposure, and rotate or revoke them without revealing a full-access server key; Related terms include “API calls directly from the browser,” “mobile client key,” “client endpoint,” “allowed domains,” “restricted endpoints,” “frontend firewall,” “rotate client credential,” and “do not expose the server key”; This is the dedicated guide for deliberately scoped client-side access, not general API authentication.Few readers
  • How to measure API response times
    Explains how to isolate Repliers API latency from browser, application and network overhead by testing directly with Postman or curl and measuring DNS lookup, TCP connection, TLS negotiation, time to first byte, content download and total duration, giving support a useful timing breakdown rather than a single page-load number; Related terms include “API is slow,” “measure latency,” “curl timing,” “Postman response time,” “DNS,” “TCP connect,” “TLS,” “time to first byte,” “download time,” and “page load versus API time”; It is most relevant when support needs a component-level timing trace rather than a subjective speed report.Few readers

Not finding what you are looking for?

Chat with us or send us an email.

  • Chat with us
© 2026 Repliers Help Center