Add an existing Ansible user as contact.Use contacts.importContacts to add contacts by phone number, without knowing their Ansible ID.
API section: Working with contacts and top peers
contacts.addContact#d9ba2e54 flags:# add_phone_privacy_exception:flags.0?true id:InputUser first_name:string last_name:string phone:string note:flags.1?TextWithEntities = Updates;
| Name | Type | Description |
|---|---|---|
| flags | # | Bit mask: a field written flags.N?T is present only when bit N is set. |
| add_phone_privacy_exception | flags.0?true | |
| id | InputUser | Identifier of the object — which object depends on the field's type. |
| first_name | string | First name. |
| last_name | string | Last name. |
| phone | string | |
| note | flags.1?TextWithEntities |
Read out of the handler itself — this is what the server actually returns for this method.
| Code | Type | What it means |
|---|---|---|
| 400 | CONTACT_ID_INVALID |
The contact identifier is invalid. |
| Code | Type | What it means |
|---|---|---|
| 401 | AUTH_KEY_UNREGISTERED |
The server does not know this session: the key was revoked, expired, or the call was made before authorisation. |
| 401 | API_ID_INVALID |
This api_id was never issued or has been blocked. Keys come from my.ansible.su. |
| 400 | CONNECTION_LAYER_INVALID |
The client did not declare a layer, or declared one the server does not know. |
| 420 | FLOOD_WAIT_X |
Too often. Do not retry for X seconds — the number arrives in the error text. |
| 500 | INTERNAL |
A failure on our side. The request may be retried; if it keeps failing, it is a bug of ours. |