Start an import
Choose where a file that has been read goes and which of its contacts is you, then start writing it.
Name a vault of the account with vault, or a new vault with vault_name. A file holding several vaults takes neither: each of its vaults arrives as a new vault of its own, and the contact each one marks as you is added to its Me, so me_contact is ignored too.
The contact named by me_contact is added to the Me contact of the vault: its values fill only what Me leaves empty, and its relationships and life events attach to Me. Send null to import every contact as somebody else. The contacts of the file come from GET /imports/{accountImport}/contacts.
The limits of the account are compared with the whole file before anything is written. A file that would take the account past its contacts, its vaults or its storage answers 422, saying which limit, and nothing is written. So does an import that is not waiting for a decision.
An import only adds records. It never changes or removes one the vault already holds. It is written in the background: ask for the import to follow its progress.
Parameters
Sent as JSON. Anything not listed here is ignored.
The id of the import. One belonging to another account answers 404.
A vault of the account to write the file into, named by its slug or its id. A vault of another account answers 404.
The name of a new vault to write the file into, up to 255 characters. Required when vault is left out, unless the file holds several vaults.
The id, in the file, of the contact who is you, or null for none. A contact the file does not hold answers 422.
Returns
The import object, writing.
The import.
Always account_import. It names the kind of record, so a caller holding several kinds can tell them apart without looking at where they came from.
The id of this record, as a string even when it reads as a number. It is what every endpoint naming this record takes.
Everything the record holds.
Where the import stands: reading, refused, read, writing, rolling_back, rolled_back, rollback_failed or completed. rollback_failed means an undo kept failing and what the import wrote is still in place. Nothing is written into a vault before the file is read and you have chosen where it goes.
What the file is: monica_4 for an export of Monica 4, monica for an export of this application. Null while the file is read, and when it was refused as neither.
Why the file cannot be imported, when the status is refused. Null otherwise.
The vaults this same file was completely imported into before. An import only adds, so importing it again into one of them writes every record a second time.
The id of one of those vaults.
How far the writing has gone.
How many records are written.
How many records there are to write, known once the file is read.
The id of the vault the file is written into, or null until one is chosen.
The id, in the file, of the contact who is you, or null for none. Until you choose, it is the contact the file names as its owner.
When the file was received, as a count of seconds since 1970.
When the import completed or finished being undone, as a count of seconds since 1970, or null.
What the file holds, one entry per kind of record, once it is read. Null while it is read.
One kind of record in the file.
The kind of record, as the file names it: contacts, notes, relationships, audit_logs and so on.
How many the file holds.
How many will not come over, because this product keeps nothing of that kind.
What became of the records of the file, one entry per kind, once the import has completed. Null before that, and for an import that was undone, since nothing of it stayed.
Where to find this record.
The absolute address this record is read from.
Rate limit
Sixty requests per minute, per user, shared by every key and device. Every answer carries the budget left in X-RateLimit-Remaining.
Keys act as you, with exactly the access you have. Make one per integration so you can revoke it alone.