Skip to main content
Autocerto is a Brazilian management system for vehicle dealerships: stock, publishing to classifieds sites (such as Webmotors, OLX and iCarros) and leads. This connector reads your account through the Autocerto integration API and brings the vehicles in stock (with photos and optional items), the stores your user can access, the status and custom info of each vehicle’s ads on the classifieds sites, the classifieds plans of each store, the lead media list and Autocerto’s reference tables.
The connector only reads data. It never creates, changes, publishes or deletes anything in Autocerto.

​
Configuring Autocerto as a Source

In the Sources tab, click on the “Add source” button located on the top right of your screen. Then, select the Autocerto option from the list of connectors. Click Next and you’ll be prompted to add your access.

​
1. Add account access

The Autocerto API uses a user name and password: the API (integration) user of your store, the same one used at integracao.autocerto.com. It is not necessarily the login you use in the Autocerto system.
  • Username: user name of the Autocerto API access.
  • Password: its password.
If your store does not have an API user yet, ask Autocerto support to create one. The connector reads every store that this user can access.
Once you’re done, click Next.

​
2. Select streams

Choose which data streams you want to sync. For faster extractions, select only the streams that are relevant to your analysis. You can select entire groups of streams or pick specific ones.
Tip: The stream can be found more easily by typing its name.
Select the streams and click Next.

​
3. Configure data streams

Customize how you want your data to appear in your catalog. Select the desired layer where the data will be placed, a folder to organize it inside the layer, a name for each table (which will effectively contain the fetched data) and the type of sync.
  • Layer: choose between the existing layers on your catalog. This is where you will find your new extracted tables as the extraction runs successfully.
  • Folder: a folder can be created inside the selected layer to group all tables being created from this new data source.
  • Table name: we suggest a name, but feel free to customize it. You have the option to add a prefix to all tables at once and make this process faster!
  • Sync Type: every Autocerto stream is Full table. The Autocerto API has no filter by date, so each sync reads the current state of your account and replaces the table with it.
Once you are done configuring, click Next.

​
4. Configure data source

Describe your data source for easy identification within your organization, not exceeding 140 characters. To define your Trigger, consider how often you want data to be extracted from this source. Stock and ad status change during the day, so a sync every few hours (or daily, if you only need a daily picture) is usually a good fit. Optionally, you can configure Delta Log Retention and determine for how long we should store old states of this table as it gets updated. Read more about this resource here. Since every stream is Full table, an Additional Full Sync is not needed. Once you are ready, click Next to finalize the setup.

​
5. Check your new source

You can view your new source on the Sources page. If needed, manually trigger the source extraction by clicking on the arrow button. Once executed, your data will appear in your Catalog.
For you to be able to see it on your Catalog, you need at least one successful source run.

​
Streams and Fields

​
Available streams

The table below lists every stream, its slug (the exact identifier to pass when creating the source via API) and a short description. All streams are Full table.

​
Fields by stream

Stores (units) the API user can access. The stock and the classifieds plans are read store by store.Table: unidades · Primary key: codigo · Sync: Full table
Vehicles in stock right now, in every store. A vehicle that is sold or removed in Autocerto leaves this table on the next sync (see Data Quality Considerations).Table: estoque · Primary key: codigo · Sync: Full table
One row per photo of each vehicle in stock. Comes with the stock: no extra request.Table: estoque_fotos · Primary key: codigo_veiculo, codigo · Sync: Full table
One row per optional item of each vehicle in stock. Comes with the stock: no extra request.Table: estoque_opcionais · Primary key: codigo_veiculo, codigo · Sync: Full table
Status of the ad of each vehicle in stock on each classifieds site. The connector asks Autocerto once per vehicle in stock.Table: anuncios_status · Primary key: codigo_veiculo, codigo_classificado · Sync: Full table
Custom price and text set for a vehicle on a specific classifieds site. Vehicles without custom info have no rows. The connector asks Autocerto once per vehicle in stock.Table: anuncios_informacoes_personalizadas · Primary key: codigo_veiculo, codigo_classificado · Sync: Full table
Classifieds sites integrated with each store, with the ad plan of each one.Table: planos_classificados · Primary key: codigo_unidade, codigo_midia · Sync: Full table
Media (channels) a lead can come from, such as a classifieds site or the store website. Use it to decode lead media codes in other systems.Table: midias_lead · Primary key: codigo · Sync: Full table
Autocerto keeps one list per vehicle type. The connector reads every type: brands for cars and motorcycles, body types for cars, motorcycles and trucks. The same code can appear under more than one type.Tables: marcas, carrocerias · Primary key: tipo, codigo · Sync: Full table
Fuel types, colors, transmissions and optional items, as Autocerto lists them. All four tables have the same fields.Tables: combustiveis, cores, cambios, opcionais · Primary key: codigo · Sync: Full table

​
Implementation Notes

​
Data Quality Considerations

  • Every table is a snapshot. Each sync replaces the tables with what Autocerto returns at that moment. A sold or removed vehicle disappears from Stock, Stock Photos, Stock Optional Items, Ad Status and Ad Custom Info on the next sync. To keep a history of the stock (for example, when each vehicle was sold), track the Stock table with a History or save daily snapshots with a Query.
  • A table is never half updated. The connector reads all the data of a table before writing any of it. If Autocerto fails or refuses part of a table (for example, the stock of one store), that table keeps its previous content and the sync shows it as failed.
  • A table that suddenly comes back empty is not emptied. If Autocerto returns no rows for Stores, Classifieds Plans, Ad Status, Ad Custom Info, Lead Media or a reference table that had rows in the previous sync, the sync fails for that table instead of emptying it. If Autocerto returns no vehicles in stock at all after a sync that had vehicles, every table built from the stock (Stock, Stock Photos, Stock Optional Items, Ad Status and Ad Custom Info) fails and keeps its previous content, even when Stock itself is not selected. If the data really was removed, run a full sync of the source to accept the empty tables.
  • Vehicles without ad data. Ad Status and Ad Custom Info are read vehicle by vehicle after the stock. When Autocerto finds no data for a vehicle (usually a vehicle that is not advertised), that vehicle has no rows, and the sync log says how many vehicles were in that situation. If Autocerto finds no data for any vehicle while the table had rows in the previous sync, the table keeps its previous content and the sync shows it as failed (see above).
  • A store whose stock empties. If one store that had vehicles in the previous sync comes back with none while the other stores still have vehicles, the sync loads the stock without it and the sync log names the store, since a store can legitimately empty its stock.
  • Vehicles sold during the sync. A few vehicles that leave the stock between the stock read and their own read are skipped, and the sync log says how many. If many vehicles fail this way, the table is not updated.
  • Dates are loaded as Autocerto returns them, without a time zone (Brasília local time in practice).
  • Leads are not available. The Autocerto API can create leads but has no way to read them, so there is no leads table.
  • Brands are not split into models and versions. Autocerto’s model and version catalog is not extracted (it would take thousands of requests); each vehicle in Stock already carries its brand, model and version.

​
Permissions

The connector checks, before reading any data, which parts of the API the user can read. If the user cannot read one part, the tables that need it are skipped (the sync shows them as failed) and the other tables are loaded:

​
API Limits & Performance

  • Autocerto does not publish a request limit. When Autocerto asks the connector to slow down, it waits as long as Autocerto says.
  • Besides one request per list and one stock request per store, Ad Status and Ad Custom Info make one request each per vehicle in stock, so their sync time grows with the size of the stock. Deselect those two tables if you do not need them.

​
Troubleshooting

​
Skills for agents

Download Autocerto skills file

Autocerto connector documentation as plain markdown, for use in AI agent contexts.