IRC Documentation · Beginner
INVITE command: invites someone to a channel
INVITE sends an invitation to join a channel. The invited person retains the choice to enter. On invitation-only channels, invitation rights and exceptions depend on the configuration.
Dialova Team · Verified on
Syntax and Parameters #
INVITE <pseudo> <salon>| Parameter | Meaning |
|---|---|
| nickname | Person to invite on the same server. |
| channel | Channel concerned, usually already joined by the sender. |
Commented Example #
C: INVITE Bob #atelier
S: :irc.example 341 Alice Bob #atelier
S: :Alice!alice@cloak.example INVITE Bob :#atelierNicknames, hosts, and text in this exchange are fictional. The client may display responses in a more readable format than the presented frames.
Possible Responses and Errors #
| Response | Understanding |
|---|---|
| 341 | Invitation accepted for transmission by the server. |
| INVITE | Event addressed to the invited person. |
| Error | Typical Cause |
|---|---|
| 401 | Nickname not found. |
| 443 | The person is already in the channel. |
| 442 / 482 | Non-member sender or insufficient privileges. |
Rights, Compatibility, and Precautions #
An invitation does not teleport a user and does not reveal the channel history. It does not guarantee bypassing all restrictions, keys, bans, or limits: consult the network rules.
Some servers offer a list of invitations or additional exceptions. These variants should be documented separately rather than presented as the base syntax.
Frequently Asked Questions #
Should I accept immediately? No. In a client, you can generally ignore the invitation.
Is an unexpected invitation reliable? It is not sufficient to establish trust. Verify the sender and the channel, especially when a link or download follows.
Sources & Verification
Examples use pseudonyms and fictional domains, except for explicitly documented connection points. Network-specific extensions and settings are noted in the text.
- Modern IRC — spécification du protocole client ↗Source Specification · consulted on 2026-10-29
- RFC 2812 — Client Protocol (2000) ↗Source Historical · consulted on 2026-10-29