2 vim:set ts=4 sw=4 tw=82 noet:
10 signal-cli - A commandline and dbus interface for the Signal messenger
14 *signal-cli* [--config CONFIG] [-h | -v | -a ACCOUNT | --dbus | --dbus-system] command [command-options]
18 signal-cli is a commandline interface for libsignal-service-java.
19 It supports registering, verifying, sending and receiving messages.
20 For registering you need a phone number where you can receive SMS or incoming calls.
21 signal-cli was primarily developed to be used on servers to notify admins of important events.
22 For this use-case, it has a dbus interface, that can be used to send messages from any programming language that has dbus bindings.
24 For some functionality the Signal protocol requires that all messages have been received from the server.
25 The `receive` command should be regularly executed. In daemon mode messages are continuously received.
30 Show help message and quit.
33 Print the version and quit.
36 Raise log level and include lib signal logs.
39 Set the path, where to store the config.
40 Make sure you have full read/write access to the given directory.
41 (Default: `$XDG_DATA_HOME/signal-cli` (`$HOME/.local/share/signal-cli`))
43 *-a* ACCOUNT, *--account* ACCOUNT::
44 Specify your phone number, that will be your identifier.
45 The phone number must include the country calling code, i.e. the number must start with a "+" sign.
47 This flag must not be given for the `link` command.
48 It is optional for the `daemon` command.
49 For all other commands it is only optional if there is exactly one local user in the
53 Make request via user dbus.
56 Make request via system dbus.
58 *-o* OUTPUT-MODE, *--output* OUTPUT-MODE::
59 Specify if you want commands to output in either "plain-text" mode or in "json". Defaults to "plain-text"
61 *--trust-new-identities* TRUST-MODE::
62 Choose when to trust new identities:
63 - `on-first-use` (default): Trust the first seen identity key from new users,
64 changed keys must be verified manually
65 - `always`: Trust any new identity key without verification
66 - `never`: Don't trust any unknown identity key, every key must be verified manually
72 Register a phone number with SMS or voice verification.
73 Use the verify command to complete the verification.
76 The verification should be done over voice, not SMS.
79 The captcha token, required if registration failed with a captcha required error.
80 To get the token, go to https://signalcaptchas.org/registration/generate.html
81 Check the developer tools for a redirect starting with signalcaptcha://
82 Everything after signalcaptcha:// is the captcha token.
86 Verify the number using the code received via SMS or voice.
89 The verification code.
91 *-p* PIN, *--pin* PIN::
92 The registration lock PIN, that was set by the user.
93 Only required if a PIN was set.
97 Disable push support for this device, i.e. this device won't receive any more messages.
98 If this is the master device, other users can't send messages to this number anymore.
99 Use "updateAccount" to undo this.
100 To remove a linked device, use "removeDevice" from the master device.
103 Delete account completely from server. Cannot be undone without loss. You will
104 have to be readded to each group.
106 CAUTION: Only delete your account if you won't use this number again!
110 Update the account attributes on the signal server.
111 Can fix problems with receiving messages.
113 *-n* NAME, *--device-name* NAME::
114 Set a new device name for the main or linked device
116 === updateConfiguration
118 Update signal configs and sync them to linked devices.
119 This command only works on the main devices.
121 *--read-receipts* {true,false}::
122 Indicates if Signal should send read receipts.
124 *--unidentified-delivery-indicators* {true,false}::
125 Indicates if Signal should show unidentified delivery indicators.
127 *--typing-indicators* {true,false}::
128 Indicates if Signal should send/show typing indicators.
130 *--link-previews* {true,false}::
131 Indicates if Signal should generate link previews.
135 Set a registration lock pin, to prevent others from registering this number.
137 REGISTRATION_LOCK_PIN::
138 The registration lock PIN, that will be required for new registrations (resets after 7 days of inactivity)
142 Remove the registration lock pin.
146 Link to an existing device, instead of registering a new number.
147 This shows a "sgnl://linkdevice?uuid=..." URI. If you want to connect to another signal-cli instance, you can just use this URI.
148 If you want to link to an Android/iOS device, create a QR code with the URI (e.g. with qrencode) and scan that in the Signal app.
150 *-n* NAME, *--name* NAME::
151 Optionally specify a name to describe this new device.
152 By default "cli" will be used.
156 Link another device to this device.
157 Only works, if this is the master device.
160 Specify the uri contained in the QR code shown by the new device.
161 You will need the full URI such as "sgnl://linkdevice?uuid=..." (formerly "tsdevice:/?uuid=...")
162 Make sure to enclose it in quotation marks for shells.
166 Show a list of linked devices.
170 Remove a linked device.
171 Only works, if this is the master device.
173 *-d* DEVICE_ID, *--device-id* DEVICE_ID::
174 Specify the device you want to remove.
175 Use listDevices to see the deviceIds.
179 Uses a list of phone numbers to determine the statuses of those users.
180 Shows if they are registered on the Signal Servers or not.
181 In json mode this is outputted as a list of objects.
183 [NUMBER [NUMBER ...]]::
184 One or more numbers to check.
188 Send a message to another user or group.
191 Specify the recipients’ phone number.
193 *-g* GROUP, *--group-id* GROUP::
194 Specify the recipient group ID in base64 encoding.
196 *-m* MESSAGE, *--message* MESSAGE::
197 Specify the message, if missing, standard input is used.
199 *-a* [ATTACHMENT [ATTACHMENT ...]], *--attachment* [ATTACHMENT [ATTACHMENT ...]]::
200 Add one or more files as attachment.
203 Send the message to self without notification.
205 *-e*, *--end-session*::
206 Clear session state and send end session message.
210 Send reaction to a previously received or sent message.
213 Specify the recipients’ phone number.
215 *-g* GROUP, *--group-id* GROUP::
216 Specify the recipient group ID in base64 encoding.
218 *-e* EMOJI, *--emoji* EMOJI::
219 Specify the emoji, should be a single unicode grapheme cluster.
221 *-a* NUMBER, *--target-author* NUMBER::
222 Specify the number of the author of the message to which to react.
224 *-t* TIMESTAMP, *--target-timestamp* TIMESTAMP::
225 Specify the timestamp of the message to which to react.
232 Send a read or viewed receipt to a previously received message.
235 Specify the sender’s phone number.
237 *-t* TIMESTAMP, *--target-timestamp* TIMESTAMP::
238 Specify the timestamp of the message to which to react.
241 Specify the receipt type, either `read` (the default) or `viewed`.
245 Send typing message to trigger a typing indicator for the recipient.
246 Indicator will be shown for 15seconds unless a typing STOP message is sent first.
249 Specify the recipients’ phone number.
251 *-g* GROUP, *--group-id* GROUP::
252 Specify the recipient group ID in base64 encoding.
255 Send a typing STOP message.
259 Remotely delete a previously sent message.
262 Specify the recipients’ phone number.
264 *-g* GROUP, *--group-id* GROUP::
265 Specify the recipient group ID in base64 encoding.
267 *-t* TIMESTAMP, *--target-timestamp* TIMESTAMP::
268 Specify the timestamp of the message to delete.
272 Query the server for new messages.
273 New messages are printed on standard output and attachments are downloaded to the config directory.
274 In json mode this is outputted as one json object per line.
276 *-t* TIMEOUT, *--timeout* TIMEOUT::
277 Number of seconds to wait for new messages (negative values disable timeout).
278 Default is 5 seconds.
279 *--ignore-attachments*::
280 Don’t download attachments of received messages.
284 Join a group via an invitation link.
287 The invitation link URI (starts with `https://signal.group/#`)
291 Create or update a group.
292 If the user is a pending member, this command will accept the group invitation.
294 *-g* GROUP, *--group-id* GROUP::
295 Specify the recipient group ID in base64 encoding.
296 If not specified, a new group with a new random ID is generated.
298 *-n* NAME, *--name* NAME::
299 Specify the new group name.
301 *-d* DESCRIPTION, *--description* DESCRIPTION::
302 Specify the new group description.
304 *-a* AVATAR, *--avatar* AVATAR::
305 Specify a new group avatar image file.
307 *-m* [MEMBER [MEMBER ...]], *--member* [MEMBER [MEMBER ...]]::
308 Specify one or more members to add to the group.
310 *-r* [MEMBER [MEMBER ...]], *--remove-member* [MEMBER [MEMBER ...]]::
311 Specify one or more members to remove from the group
313 *--admin* [MEMBER [MEMBER ...]]::
314 Specify one or more members to make a group admin
316 *--remove-admin* [MEMBER [MEMBER ...]]::
317 Specify one or more members to remove group admin privileges
320 Reset group link and create new link password
322 *--link* LINK_STATE::
323 Set group link state: `enabled`, `enabled-with-approval`, `disabled`
325 *--set-permission-add-member* PERMISSION::
326 Set permission to add new group members: `every-member`, `only-admins`
328 *--set-permission-edit-details* PERMISSION::
329 Set permission to edit group details: `every-member`, `only-admins`
331 *--set-permission-send-messages* PERMISSION::
332 Set permission to send messages in group: `every-member`, `only-admins`
333 Groups where only admins can send messages are also called announcement groups
335 *-e* EXPIRATION_SECONDS, *--expiration* EXPIRATION_SECONDS::
336 Set expiration time of messages (seconds).
337 To disable expiration set expiration time to 0.
341 Send a quit group message to all group members and remove self from member list.
342 If the user is a pending member, this command will decline the group invitation.
344 *-g* GROUP, *--group-id* GROUP::
345 Specify the recipient group ID in base64 encoding.
348 Delete local group data completely after quitting group.
352 Show a list of known groups and related information.
353 In json mode this is outputted as an list of objects and is always in detailed mode.
356 Include the list of members of each group and the group invite link.
360 Show a list of known contacts with names.
364 List all known identity keys and their trust status, fingerprint and safety number.
366 *-n* NUMBER, *--number* NUMBER::
367 Only show identity keys for the given phone number.
371 Set the trust level of a given number.
372 The first time a key for a number is seen, it is trusted by default (TOFU).
373 If the key changes, the new key must be trusted manually.
376 Specify the phone number, for which to set the trust.
378 *-a*, *--trust-all-known-keys*::
379 Trust all known keys of this user, only use this for testing.
381 *-v* VERIFIED_SAFETY_NUMBER, *--verified-safety-number* VERIFIED_SAFETY_NUMBER::
382 Specify the safety number of the key, only use this option if you have verified the safety number.
383 Can be either the plain text numbers shown in the app or the bytes from the QR-code,
388 Update the profile information shown to message recipients.
389 The profile is stored encrypted on the Signal servers.
390 The decryption key is sent with every outgoing messages to contacts and included
393 *--given-name* NAME, *--name* NAME::
396 *--family-name* FAMILY_NAME::
399 *--about* ABOUT_TEXT::
400 New profile status text.
402 *--about-emoji* EMOJI::
403 New profile status emoji.
405 *--avatar* AVATAR_FILE::
406 Path to the new avatar image file.
413 Update the info associated to a number on our contact list.
414 This change is only local but can be synchronized to other devices by using `sendContacts` (see below).
415 If the contact doesn't exist yet, it will be added.
418 Specify the contact phone number.
421 Specify the new name for this contact.
423 *-e*, *--expiration* EXPIRATION_SECONDS::
424 Set expiration time of messages (seconds).
425 To disable expiration set expiration time to 0.
429 Block the given contacts or groups (no messages will be received).
430 This change is only local but can be synchronized to other devices by using `sendContacts` (see below).
432 [CONTACT [CONTACT ...]]::
433 Specify the phone numbers of contacts that should be blocked.
435 *-g* [GROUP [GROUP ...]], *--group-id* [GROUP [GROUP ...]]::
436 Specify the group IDs that should be blocked in base64 encoding.
440 Unblock the given contacts or groups (messages will be received again).
441 This change is only local but can be synchronized to other devices by using `sendContacts` (see below).
443 [CONTACT [CONTACT ...]]::
444 Specify the phone numbers of contacts that should be unblocked.
446 *-g* [GROUP [GROUP ...]], *--group-id* [GROUP [GROUP ...]]::
447 Specify the group IDs that should be unblocked in base64 encoding.
451 Send a synchronization message with the local contacts list to all linked devices.
452 This command should only be used if this is the master device.
456 Send a synchronization request message to the master device (for group, contacts, ...).
457 The master device will respond with synchronization messages with full contact and
460 === uploadStickerPack
462 Upload a new sticker pack, consisting of a manifest file and the sticker images.
463 Images must conform to the following specification: (see https://support.signal.org/hc/en-us/articles/360031836512-Stickers#sticker_reqs )
464 - Static stickers in PNG or WebP format
465 - Animated stickers in APNG format,
466 - Maximum file size for a sticker file is 300KiB
467 - Image resolution of 512 x 512 px
469 The required manifest.json has the following format:
474 "title": "<STICKER_PACK_TITLE>",
475 "author": "<STICKER_PACK_AUTHOR>",
476 "cover": { // Optional cover, by default the first sticker is used as cover
477 "file": "<name of image file, mandatory>",
478 "contentType": "<optional>",
479 "emoji": "<optional>"
483 "file": "<name of image file, mandatory>",
484 "contentType": "<optional>",
485 "emoji": "<optional>"
493 The path of the manifest.json or a zip file containing the sticker pack you wish to upload.
497 signal-cli can run in daemon mode and provides an experimental dbus interface.
498 If no `-a` account is given, all local accounts will be exported as separate dbus
499 objects under the same bus name.
502 Use DBus system bus instead of user bus.
503 *--ignore-attachments*::
504 Don’t download attachments of received messages.
508 Register a number (with SMS verification)::
509 signal-cli -a ACCOUNT register
511 Verify the number using the code received via SMS or voice::
512 signal-cli -a ACCOUNT verify CODE
514 Send a message to one or more recipients::
515 signal-cli -a ACCOUNT send -m "This is a message" [RECIPIENT [RECIPIENT ...]] [-a [ATTACHMENT [ATTACHMENT ...]]]
517 Pipe the message content from another process::
518 uname -a | signal-cli -a ACCOUNT send [RECIPIENT [RECIPIENT ...]]
521 signal-cli -a ACCOUNT updateGroup -n "Group name" -m [MEMBER [MEMBER ...]]
523 Add member to a group::
524 signal-cli -a ACCOUNT updateGroup -g GROUP_ID -m "NEW_MEMBER"
526 Accept a group invitation::
527 signal-cli -a ACCOUNT updateGroup -g GROUP_ID
530 signal-cli -a ACCOUNT quitGroup -g GROUP_ID
532 Send a message to a group::
533 signal-cli -a ACCOUNT send -m "This is a message" -g GROUP_ID
535 Trust new key, after having verified it::
536 signal-cli -a ACCOUNT trust -v SAFETY_NUMBER NUMBER
538 Trust new key, without having verified it. Only use this if you don't care about security::
539 signal-cli -a ACCOUNT trust -a NUMBER
542 * *1*: Error is probably caused and fixable by the user
543 * *2*: Some unexpected error
544 * *3*: Server or IO error
545 * *4*: Sending failed due to untrusted key
549 The password and cryptographic keys are created when registering and stored in the current users home directory, the directory can be changed with *--config*:
551 `$XDG_DATA_HOME/signal-cli/` (`$HOME/.local/share/signal-cli/`)
555 Maintained by AsamK <asamk@gmx.de>, who is assisted by other open source contributors.
556 For more information about signal-cli development, see
557 <https://github.com/AsamK/signal-cli>.