Note: You will likely not face any rate limits unless you are on the Enterprise plan or have any of the Unlimited Endpoints. You'll more so be restricted by your monthly property record allotment given by the plans.

Our endpoints are designed to deliver data fast and in bulk when needed as long as within plan limits for total credits used (+overage if selected during signup)

If you need a higher throughput of request for any reason, contact us at [email protected] & we can help!

Rate Limiting Errors

• if you exceed our rate limits you'll see an error such as:

{
  statusCode: 429,
  error: "Too Many Requests",
  message: "You have reached your daily credit limit for this endpoint, please try again later."
}

Property Search & Detail Daily Rate Limits

*doesn't include "count" or "ids_only" calls

For example, one Property Search API request can bring back up to 250 property record addresses per request. To get to 1,000,000 credits this would take 4,000 requests at the max size. At a "size" of 10 (typical for end user interactive sites), it would be 100,000 requests.

{
  statusCode: 429,
  error: "Too Many Requests",
  message: "You have reached your daily credit limit for this endpoint, please try again later."
}

SkipTrace APIs Rate Limits

Address Verification API Rate Limits

Address Verification can be used to validate huge lists of addresses, but you'll need to batch your requests to RealEstateAPI to avoid getting 429 Too Many Requests errors.

Every Address Verification API call can contain up to 100 addresses per call.

By x-api-key: 10 requests / second (up to 1,000 addresses / second )

By x-user-id: 3 requests / second (up to 300 addresses / second per x-user-id, if specified)

const axios = require('axios');

let url = 'https://api.realestateapi.com/v2/AddressVerification";

let addressVerifyBatches = [
  {
    addresses: [
      { 
        "key": 0,
        "street": "2505 NW 28th Street",
        "city": "Oklahoma City",
        "state": "OK",
        "zip": "73107"
      },
      ...99 more
    ]
	},
  {
    addresses: [
      { 
        "key": 101,
        "street": "2504 NW 28th Street",
        "city": "Oklahoma City",
        "state": "OK",
        "zip": "7310"
      },
      ...99 more
    ] 
  },
  ...998 more (for a total of 1000 batches of 100 addresses)
]

let headers = {
  'x-api-key': "<<Your-API-Key>>",
  //'x-user-id': "testUserId" (only rate limited by if specified)
}


let counter = 0;



setInterval( async () => {
  
  for (let i = 0; i<10; i++) {
    let body = { 
      addresses: addressVerifyBatches[counter].addresses
    }
  
  	let runVerify = await axios.post(url, body, {headers});
    
  	counter++;
  }
  
}, 1000)//in milliseconds 1000ms = 1 second

Without observing the rate limits, your batch jobs will start getting response codes such as below. You will get intermittent 429s until your rate window gets clogged up, and then you will receive only 429s.