Create a Channel Canvas for a channel.
POSThttps://slack.com/api/conversations.canvases.createapplication/x-www-form-urlencodedapplication/jsontokenAuthentication token bearing required scopes. Tokens should be passed as an HTTP Authorization header or alternatively, as a POST parameter.
xxxx-xxxxxxxxx-xxxxThis method is used to create a new channel canvas for the channel. Channel canvases can act as a resource hub, providing users with information highlights and channel-specific details. Once a channel canvas has been created with document_content, you will see the canvas icon in the upper right of the channel switch to indicate that a channel canvas now exists. This method returns an ok: true response with the canvas ID.
A canvas will be created empty if no content is provided, but will not result in an icon change.
The following formatting elements are supported in the document_content object:
Calling conversations.canvases.create when a channel canvas already exists will result in a channel_canvas_already_exists response. You can find the ID of the canvas in the channel.properties.canvas section in the response of a conversations.info request.
In order for your app to create a channel canvas, it must have the proper permissions to do so. The channel must be public, or if it is private the app/user must be invited to the channel. Unlike the need to share a standalone canvas, there are no access implications nor is it necessary to share a channel canavs to grant access. Access is tied to channel access.
If you are looking to create a standalone canvas not associated with a particular channel, use the canvases.create method instead.
Typical success response
{
"ok": true,
"canvas_id": "F1234ABCD"
}Typical error response when the channel canvas has already been created for the channel
{
"ok": false,
"error": "channel_canvas_already_exists"
} 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 |
|---|---|
canvas_disabled_user_team | Canvas is disabled on user's team |
restricted_action | User does not have permission to perform this action. |
channel_canvas_creation_failed | Channel canvas was unable to be created. |
channel_canvas_already_exists | Channel canvas for the specified channel already exists. |
access_denied | Access to a resource specified in the request is denied. |
account_inactive | Authentication token is for a deleted user or workspace when using a |
deprecated_endpoint | The endpoint has been deprecated. |
ekm_access_denied | Administrators have suspended the ability to post a message. |
enterprise_is_restricted | The method cannot be called from an Enterprise. |
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. |
is_bot | This method cannot be called by a legacy bot. |
method_deprecated | The method has been deprecated. |
missing_scope | The token used is not granted the specific scope permissions required to complete this request. |
not_allowed_token_type | The token type used in this request is not allowed. |
not_authed | No authentication token provided. |
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. |
token_expired | Authentication token has expired |
token_revoked | Authentication token is for a deleted user or workspace or the app has been removed when using a |
two_factor_setup_required | Two factor setup is required. |
team_access_not_granted | The token used is not granted the specific workspace access required to complete this request. |
accesslimited | Access to this method is limited on the current network |
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. |
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 |
invalid_arguments | The method was either called with invalid arguments or some detail about the arguments passed is invalid, which is more likely when using complex arguments like blocks or attachments. |
invalid_array_arg | The method was passed an array as an argument. Please only input valid strings. |
invalid_charset | The method was called via a |
invalid_form_data | The method was called via a |
invalid_post_type | The method was called via a |
missing_post_type | The method was called via a |
ratelimited | The request has been ratelimited. Refer to the |
request_timeout | The method was called via a |
service_unavailable | The service is temporarily unavailable |
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. |
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 |
superfluous_charset | The method was called via a |