app.bsky.contact.importContacts
Import contacts for securely matching with other users. This follows the protocol explained in https://docs.bsky.app/blog/contact-import-rfc. Requires authentication.
Details · procedure
| Kind | procedure |
|---|---|
| Authority | contact.bsky.app |
| Indexed |
Procedure
procedure · POSTInput
application/jsonList of phone numbers in global E.164 format (e.g., '+12125550123'). Phone numbers that cannot be normalized into a valid phone number will be discarded. Should not repeat the 'phone' input used in `app.bsky.contact.verifyPhone`.
minLength: 1maxLength: 1000
JWT to authenticate the call. Use the JWT received as a response to the call to `app.bsky.contact.verifyPhone`.
Output
application/jsonThe users that matched during import and their indexes on the input contacts, so the client can correlate with its local list.
Errors
InvalidDid
No description in schema.
InvalidContacts
No description in schema.
TooManyContacts
No description in schema.
InvalidToken
No description in schema.
InternalError
No description in schema.
Similar lexicons
semantic matchLexicons whose schemas describe something close to this one. Check them before publishing a new one that overlaps.
-
Import contacts for securely matching with other users. This follows the protocol explained in https://docs.bsky.app/blog/contact-import-rfc. Requires authentication.
-
app.bsky.contact.verifyPhone
procedureVerifies control over a phone number with a code received via SMS and starts a contact import session. Requires authentication.
-
Verifies control over a phone number with a code received via SMS and starts a contact import session. Requires authentication.
-
Associates a profile with the positional index of the contact import input in the call to `app.bsky.contact.importContacts`, so clients can know which phone caused a particular match.