admin.users.invite

Invite a user to a workspace.

Facts

Method URL: https://slack.com/api/admin.users.invite

Preferred HTTP method: POST

Accepted content types: application/x-www-form-urlencoded, application/json

Rate limiting: Tier 2

Works with:

Token type	Required scope(s)
user	`admin.users:write`

This Admin API invites a user to a workspace.

This API method for admins may only be used on Enterprise Grid.

Arguments

tokenRequired

Authentication token bearing required scopes.

Examplexxxx-xxxxxxxxx-xxxx

channel_idsRequired

A comma-separated list of channel_ids for this user to join. At least one channel is required.

ExampleC1A2B3C4D,C26Z25Y24

emailRequired

The email address of the person to invite.

Examplejoe@email.com

team_idRequired

The ID (T1234) of the workspace.

custom_messageOptional

An optional message to send to the user in the invite email.

ExampleCome and join our team!

guest_expiration_tsOptional

Timestamp when guest account should be disabled. Only include this timestamp if you are inviting a guest user and you want their account to expire on a certain date.

Example0123456789.012345

is_restrictedOptional

Is this user a multi-channel guest user? (default: false)

Exampletrue

is_ultra_restrictedOptional

Is this user a single channel guest user? (default: false)

Exampletrue

real_nameOptional

Full name of the user.

Example{"full_name":"Joe Smith"}

resendOptional

Allow this invite to be resent in the future if a user has not signed up yet. (default: false)

Exampletrue

This method supports application/json via HTTP POST. Present your token in your request's Authorization header. Learn more.

Response

Typical success response

{
    "ok": true
}

Errors

This table lists the expected errors that this method could return. However, other errors can be returned in the case where the service is down or other unexpected factors affect processing. Callers should always check the value of the ok params in the response.

Error	Description
`team_not_found`	`team_id` was not found.
`feature_not_enabled`	The Admin APIs feature is not enabled for this team.
`invalid_email`	Email address was not valid.
`already_in_team`	The user is already on the team.
`user_disabled`	The user is disabled.
`already_in_team_invited_user`	The user has already been invited to the team.
`failed_looking_up_user`	We couldn't find the requested user.
`failed_to_validate_caller`	The token calling this method doesn't have permission to invite a user.
`failed_to_validate_team`	The team calling this method was invalid.
`failed_to_validate_channels`	`channel_ids` was invalid.
`failed_to_validate_expiration`	`expiration_ts` was invalid.
`failed_to_validate_custom_message`	`extra_message` was invalid.
`failed_to_send_invite`	The invite failed to send.
`not_authed`	No authentication token provided.
`invalid_auth`	Some aspect of authentication cannot be validated. Either the provided token is invalid or the request originates from an IP address disallowed from making the request.
`account_inactive`	Authentication token is for a deleted user or workspace.
`token_revoked`	Authentication token is for a deleted user or workspace or the app has been removed.
`no_permission`	The workspace token used in this request does not have the permissions necessary to complete the request. Make sure your app is a member of the conversation it's attempting to post a message to.
`org_login_required`	The workspace is undergoing an enterprise migration and will not be available until migration is complete.
`ekm_access_denied`	Administrators have suspended the ability to post a message.
`missing_scope`	The token used is not granted the specific scope permissions required to complete this request.
`is_bot`	This method cannot be called by a bot user.
`invalid_arguments`	The method was called with invalid arguments.
`invalid_arg_name`	The method was passed an argument whose name falls outside the bounds of accepted or expected values. This includes very long names and names with non-alphanumeric characters other than `_`. If you get this error, it is typically an indication that you have made a very malformed API call.
`invalid_charset`	The method was called via a `POST` request, but the `charset` specified in the `Content-Type` header was invalid. Valid charset names are: `utf-8` `iso-8859-1`.
`invalid_form_data`	The method was called via a `POST` request with `Content-Type` `application/x-www-form-urlencoded` or `multipart/form-data`, but the form data was either missing or syntactically invalid.
`invalid_post_type`	The method was called via a `POST` request, but the specified `Content-Type` was invalid. Valid types are: `application/json` `application/x-www-form-urlencoded` `multipart/form-data` `text/plain`.
`missing_post_type`	The method was called via a `POST` request and included a data payload, but the request did not include a `Content-Type` header.
`team_added_to_org`	The workspace associated with your request is currently undergoing migration to an Enterprise Organization. Web API and other platform operations will be intermittently unavailable until the transition is complete.
`request_timeout`	The method was called via a `POST` request, but the `POST` data was either missing or truncated.
`fatal_error`	The server could not complete your operation(s) without encountering a catastrophic error. It's possible some aspect of the operation succeeded before the error was raised.
`internal_error`	The server could not complete your operation(s) without encountering an error, likely due to a transient issue on our end. It's possible some aspect of the operation succeeded before the error was raised.

Warnings

This table lists the expected warnings that this method will return. However, other warnings can be returned in the case where the service is experiencing unexpected trouble.

Warning	Description
`missing_charset`	The method was called via a `POST` request, and recommended practice for the specified `Content-Type` is to include a `charset` parameter. However, no `charset` was present. Specifically, non-form-data content types (e.g. `text/plain`) are the ones for which `charset` is recommended.
`superfluous_charset`	The method was called via a `POST` request, and the specified `Content-Type` is not defined to understand the `charset` parameter. However, `charset` was in fact present. Specifically, form-data content types (e.g. `multipart/form-data`) are the ones for which `charset` is superfluous.