Integration limits

What is an API rate limit and why does it matter to a dealership?

An API rate limit is a cap on how many requests a system will accept in a period. It matters because it determines how current your data is. A connection described as real time can be limited to a few synchronisations an hour, which is the difference between accurate inventory and a customer arriving for a vehicle that sold yesterday.

Direct answerSeptember 1, 2026 reviewedNeutral evaluation
Direct answer

What is an API rate limit and why does it matter to a dealership?

An API rate limit is a cap on how many requests a system will accept in a period. It matters because it determines how current your data is.

A connection described as real time can be limited to a few synchronisations an hour, which is the difference between accurate inventory and a customer arriving for a vehicle that sold yesterday. Replace 'real time' with a figure: how many requests, over what period, and what happens when the limit is reached: queued, dropped or failed.

Translate the limit into store terms. If inventory synchronises four times an hour, the exposure is a fifteen-minute window of stale listings and pricing.

What is an API rate limit and why does it matter to a dealership? at a glance
Search intentIntegration limits
Related categories2
Related guides0
01

Ask for the number, not the adjective

Replace 'real time' with a figure: how many requests, over what period, and what happens when the limit is reached: queued, dropped or failed.

02

Understand the business consequence

Translate the limit into store terms. If inventory synchronises four times an hour, the exposure is a fifteen-minute window of stale listings and pricing. Decide whether that is acceptable rather than discovering it later.

03

Check who bears the cost of exceeding it

Some agreements charge for volume above a threshold. Establish the unit, the price and whether a marketing campaign or a large data load can trigger it.

04

Test at your volume

Limits that are invisible at demo volume become visible at group volume. Ask for a reference operating at your scale.

05

Where limits show up in daily work

Rate limits appear as delays: inventory changes that take a while to reach the website, leads that reach the CRM late, or a bulk update that stops partway. Staff may describe these as the system being slow or flaky. Ask the vendor to log requests and any rejected ones so that the cause can be identified rather than guessed.

06

Designing around limits

A well-designed integration sends only changes, groups requests sensibly and retries failures without duplicating records. Ask how the vendor handles a burst, such as an overnight import or a large campaign response, and how it notifies you when the limit is reached. Schedule heavy jobs at quiet hours where possible.

07

Common mistakes about limits

Accepting the words real time without a number, forgetting limits when more rooftops are added, assuming both sides have the same limit and not checking whether limits differ by plan or fee tier are the typical errors. Record the agreed limits in the integration record with the date, and re-check them at each renewal.

08

Questions to ask both vendors

What are the limits for requests per minute and per day? Do they differ by connection type?

What is returned when the limit is reached? Are requests queued?

Who notifies us? Is there a charge for higher limits?

Confirm the answers from both sides, since one vendor's limit can determine how the whole connection behaves.

Decision checklist

What to verify

Open procurement templates →
□

Replace 'real time' with a number of requests per period

□

Translate the limit into a stale-data window in store terms

□

Confirm who pays when the limit is exceeded

□

Ask for a reference operating at your volume

Related market maps

Continue the research

People also research

Related dealership technology questions

All questions →