FIPE (Brazilian Vehicle Prices) API

Free FIPE API with no key: official Brazilian reference prices for cars, motorcycles and trucks by brand, model and year. Tested curl example and live response.

No API key requiredCORS enabledHTTPSFree tier

Endpoint tested and returned HTTP 200 on 2026-08-21

What is the FIPE (Brazilian Vehicle Prices) API?

The FIPE API is a free, key-free REST wrapper around the Fundação Instituto de Pesquisas Econômicas vehicle price table — the official reference used across Brazil for vehicle valuation. It exposes brands, models, model years and the current reference price for cars, motorcycles and trucks.

The FIPE table is the standard price reference for vehicles in Brazil. Insurers use it to set cover, banks use it for loan collateral, buyers and sellers use it to anchor negotiations, and tax authorities reference it. FIPE publishes the table monthly but not as a developer-friendly API, so this open-source wrapper exists to fill that gap.

The interface is a strict four-step drill-down and you cannot skip a level: vehicle type, then brand (`marcas`), then model (`modelos`), then model year (`anos`), and only then the price. Each step returns codes you feed into the next, so a price lookup is four sequential requests. Cache the brand and model lists — they change only when FIPE publishes a new table — and you reduce a live lookup to a single call.

Quick facts

Base URL: https://parallelum.com.br/fipe/api/v1
Authentication: No API key or account. This is an unofficial community wrapper around FIPE's published data, not a FIPE-operated service.
Rate limit: No published limit; the maintainer asks for reasonable use. Cache the reference lists rather than re-fetching them.
Pricing: Free and open source.
CORS: Enabled — callable directly from browser JavaScript
Official docs: Read the docs

How to use the FIPE (Brazilian Vehicle Prices) API

Every request below was executed against the live API on 2026-08-21, and the response shown is the real body it returned — not an illustration.

1. List every car brand in the FIPE table

GET https://parallelum.com.br/fipe/api/v1/carros/marcas

curl

curl 'https://parallelum.com.br/fipe/api/v1/carros/marcas'

JavaScript (fetch)

const res = await fetch("https://parallelum.com.br/fipe/api/v1/carros/marcas");
if (!res.ok) throw new Error(`Request failed: ${res.status}`);
const data = await res.json();
console.log(data);

Python (requests)

import requests

res = requests.get("https://parallelum.com.br/fipe/api/v1/carros/marcas", timeout=20)
res.raise_for_status()
print(res.json())

Response — HTTP 200 (truncated)

[
  {
    "codigo": "1",
    "nome": "Acura"
  },
  {
    "codigo": "2",
    "nome": "Agrale"
  },
  {
    "codigo": "3",
    "nome": "Alfa Romeo"
  },
  {
    "codigo": "4",
    "nome": "AM Gen"
  },
  {
    "codigo": "5",
    "nome": "Asia Motors"
  },
  {
    "codigo": "189",
    "nome": "ASTON MARTIN"
  },
  {
    "codigo": "6",
    "nome": "Audi"
  },
  {
    "codigo": "207",
    "nome": "Baby"
  },
  {
    "codigo": "7",
    "nome": "BMW"
  },
  {
    "codigo": "8",
    "nome": "BRM"
  },
  {
    "codigo": "123",
    "nome": "Bugre"
  },
  {
    "codigo": "238",
    "nome": "BYD"
  },
  {
    "codigo": "236",
    "nome": "CAB Motors"
  },
  {
    "codigo": "10",
    "nome": "Cadillac"
  },
  {
    "codigo": "265",
    "nome": "Caoa Changan"
  },
  {
    "codigo": "245",
    "nome": "Caoa Chery"
  },
  {
    "codigo": "161",
    "nome": "Caoa Chery/Chery"
  },
  {
    "codigo": "11",
    "nome": "CBT Jipe"
  },
  {
    "codigo": "136",
    "nome": "CHANA"
  },
  {
    "codigo": "182",
    "nome": "CHANGAN"
  },
  {
    "codigo": "12",
    "nome": "Chrysler"
  },
  {
    "codigo": "13",
    "nome": "Citroën"
  },
  {
    "codigo": "14",
    "nome": "Cross Lander"
  },
  {
    "codigo": "241",
    "nome": "D2D Motors"
  },
  {
    "codigo": "15",
    "nome": "Daewoo"
  },
  {
    "codigo": "16",
    "nome": "Daihatsu"
  },
  {
    "codigo": "263",
    "nome": "Denza"
  },
  {
    "codigo": "246",
    "nome": "DFSK"
  },
  {
    "codigo": "17",
    "nome": "Dodge"
  },
  {
    "codigo": "147",
    "nome": "EFFA"
  },
  {
    "codigo": "18",
    "nome": "Engesa"
  },
  {

Parameters

Parameter	Type	Required	Description
`tipo`	path segment	Required	Vehicle type: `carros`, `motos` or `caminhoes`. `carros`
`marcas`	path segment	Required	Literal segment that lists brands. Each result carries the `codigo` you need next. `marcas`
`codigoMarca`	path segment	Optional	Brand code, followed by `/modelos` to list that brand's models. `21`
`codigoModelo`	path segment	Optional	Model code, followed by `/anos` to list available model years. `4828`
`codigoAno`	path segment	Optional	Year code. The final segment, which returns the price record. `2014-3`

Response fields

codigostring: The identifier to pass into the next level of the drill-down. Returned as a string even though it looks numeric.
nomestring: Human-readable brand, model or year label. Note the inconsistent casing in the source data — "Alfa Romeo" sits next to "ASTON MARTIN".
Valorstring: On the final price record: the reference price formatted as Brazilian currency, for example "R$ 45.000,00". It is a display string, not a number.
MesReferenciastring: Which monthly FIPE table the price comes from — essential context, since prices are only revised monthly.
Combustivelstring: Fuel type: Gasolina, Álcool, Diesel or Flex.
CodigoFipestring: The official FIPE code for the vehicle, which is the identifier used on paperwork.

What you can build with the FIPE (Brazilian Vehicle Prices) API

Value a used vehicle for a Brazilian marketplace listing
Support insurance quoting or loan collateral assessment
Build a vehicle brand and model picker with real data
Track how a model's reference price moves month to month

Common errors and how to fix them

404

A code from a previous step was wrong or belongs to a different vehicle type.

Fix: The drill-down is strict — a car brand code is meaningless under `motos`. Always walk the levels in order.

Price is a formatted string

Not an error — `Valor` is display-formatted Brazilian currency.

Fix: Strip "R$", then remember Brazilian formatting uses `.` for thousands and `,` for decimals before parsing to a number.

Slow responses

The wrapper proxies FIPE's own systems.

Fix: Cache brand and model lists aggressively; they only change when FIPE publishes a new monthly table.

FIPE (Brazilian Vehicle Prices) API — frequently asked questions

Is the FIPE API free?

Yes, free with no API key. It is an unofficial open-source wrapper around FIPE's published price table rather than a service operated by FIPE itself.

How do I look up a vehicle price?

Walk the drill-down in order: vehicle type, then brand, then model, then model year. Each response carries the `codigo` needed for the next step, so a price lookup takes four sequential requests — cache the earlier lists to avoid repeating them.

Why is the price returned as text?

`Valor` is display-formatted Brazilian currency, like "R$ 45.000,00". Strip the currency symbol and remember that Brazilian formatting uses dots for thousands and a comma for the decimal separator — the reverse of English convention.

How often do FIPE prices update?

Monthly. The `MesReferencia` field on every price record tells you which table the figure comes from, which is important context when a price is used in a quote or a contract.

Tools that pair with this API

Percentage Change Calculator

Work out the percentage increase or decrease between an old and a new value. See the absolute change and whether it went up or down, instantly and privately.

JSON to CSV Converter

Convert a JSON array of objects to CSV online. Automatic column headers from the union of all keys, delimiter choice and proper quoting — all in-browser.

Unit Converter

Convert between units of length, weight, temperature, area, volume, speed, time and data storage instantly, with a swap button and common conversion tables.

FIPE (Brazilian Vehicle Prices) is an independent third-party service and is not affiliated with ByteTools or ByteVancer. Details on this page were verified on 2026-08-21; always check the official documentation before relying on this API in production, as terms and limits can change.