For a firm: Connect step 2, and the settings table afterwards: bind the system's employees to members
One line per employee, a member or nobody. A member bound to two employees is a 409: one employee of the practice system is one person here. A connector waiting on its team (pending_mapping) becomes connected; any other status, and its last_error, is left as it is. Where the firm's first read is done (the sync a client sends after the connect ran it while the connector waited on this step) the read made here is by change and quick; where it never ran it is made here, whole; and a read that is running already is not waited for, the summary being answered with what is in so far. The sync runs inline and the summary is the answer. The same route edits the table afterwards, where a new employee the sync found appears unbound. 404 for a kind whose identity is a per-user sign-in: nobody is shown a table there, and each person's own authorisation fills their row (D-166). A firm connected to a system this service carries no adapter for answers the not-available 422.
Operator mount: an operator acting for the firm named in the path, as its oldest active admin, else its oldest active billing member; X-Six-Minute-Acting-As names them. 404 for no such firm, 409 urn:six-minute:problem:no-acting-member for one with neither.
Request
- Base URLhttps://api.sixminute.ai (the document declares no server; this is the origin it was published from)
- AuthHTTP bearer
Path parameters
Request body
Response
The connector after the confirmation and the first sync.
Changes
No recorded changes to this operation across all 2 revisions of this API.