Data import formats

Avensa has two distinct bulk-import flows: a contacts CSV/Excel import (manual column mapping in the UI) and a property units Excel/CSV import (auto-detected headers, used when adding units to a building). Both run client-side in the app; there is no /api/v1 upload endpoint for either today — use POST /api/v1/contacts / unit creation per-row if you need a programmatic path, or the /api/v1/imports endpoints to track import jobs created some other way.

Contacts import

Where: Contacts → Import (CSV or Excel). Limit: 500 rows per import.

You map each source column to one of these fields yourself in the wizard (nothing is auto-guessed except by matching your header text to the field label):

A few more fields are accepted by the underlying schema even though the wizard doesn't map them by default: secondary_email, secondary_phone, budget_currency, budget_type, contact_types, gdpr_consent, marketing_opt_in.

Boolean-like cells (gdpr_consent, marketing_opt_in) accept true/false, yes/no, 1/0, and their Bulgarian equivalents (да/не). List cells (tags, contact_types) split on comma, semicolon, or pipe. An unrecognized or empty cell leaves the field unset rather than failing the row.

Download the in-app sample template for a working example — its header row auto-maps on re-import:

First Name, Last Name, Email, Phone, Company, Legal Name, Job Title, City,
Budget Min, Budget Max, Lead Source, Lifecycle Stage, Lead Rating, Tags,
Owner Email, Notes

Property units import (Excel/CSV)

Where: Properties → New building → Import units. Limit: 500 rows, 10 MB file size.

Unlike contacts, headers are auto-detected — you don't map columns by hand. The parser scans for a header row (skipping title/caption rows above it), matching header text case- and accent-insensitively against known variants in both English and Bulgarian. unit_number and price are the two required columns; import fails with a clear message naming the missing column and its accepted header variants if either is absent.

Notes:

• Currency is always EUR.
• Cyrillic headers and values are supported; CSVs may use ; as the separator (common for Bulgarian Excel exports) and are read as Windows-1251 when needed so Cyrillic isn't mangled.
• Numbers accept either , or . as the decimal separator (localized formats like 1 250,50 are parsed correctly).
• Blank rows are ignored.

Importing programmatically (headless)

POST /api/v1/imports is a separate, headless entry point into the same import pipeline the in-app wizards use — it creates an import_jobs row and starts processing immediately, auto-detecting field mappings when you don't supply them.

POST /api/v1/imports

Track a job and its per-row results:

GET /api/v1/imports
GET /api/v1/imports/{id}
GET /api/v1/imports/{id}/items