specification: API Commons Rate Limits
specificationVersion: '0.1'
schema: https://raw.githubusercontent.com/api-evangelist/interface-research/main/schema/api-commons.yml#/$defs/RateLimits
provider: Ford
providerId: ford
created: '2026-05-04'
modified: '2026-09-10'
generated: '2026-09-10'
method: searched
reconciled: true
tags:
  - Automobiles
  - Connected Vehicle
  - Rate Limiting
description: >-
  Ford publishes no numeric rate limits for its APIs, and no rate-limit response headers were
  observed. Nothing in the Ford Developer Marketplace's own content bundle states a request-per-
  second, per-minute or per-day figure, a burst allowance, a quota, or a minimum polling interval.
  An unauthenticated call to a live FordConnect endpoint returned a bare 401 carrying no
  X-RateLimit-*, RateLimit-* or Retry-After header, so we have no runtime signal to record either.
notes: >-
  Replaces a 2026-05-04 bulk-sweep scaffold that asserted a per-partner throttle and a per-vehicle
  "minimum poll interval enforced to protect TCU/modem". Those rows described what a connected-
  vehicle API typically does, not what Ford publishes; neither was verifiable and both have been
  removed. limit_count: 0 is the honest measurement.
limit_count: 0
headers: {}
responseCodes: {}
sources:
  - https://developer.ford.com/apis
  - https://developer.ford.com/assets/i18n/en.json
probed:
  - url: https://api.vehicle.ford.com/api/fordconnect/vehicleinfo/v3/vehicles
    status: 401
    rate_limit_headers: none
    retry_after: absent
    checked: '2026-09-10'
  - url: https://api.mps.ford.com/api/fordconnect/vehicles/v1
    status: 503
    rate_limit_headers: none
    checked: '2026-09-10'
    note: host returns "no healthy upstream" from Apigee; nothing observable
limits: []
policies: []