Create Card
POST
/web/v1/slash/connections/{connectionBizId}/cards JWTCreates a new card under the specified Slash connection. The request body is passed through to the Slash platform.
Required Headers
| Header | Example Value | Description |
|---|---|---|
| Content-Type | application/json | Request content type |
| Accept | application/json | Expected response type |
| X-Client-Hash | Client device fingerprint | |
| Accept-Language | en, zh, zh-Hant, ja, vi | Response language (default: en) |
| Authorization | Bearer | JWT access token |
| X-Workspace-Id | Target workspace ID |
Request Parameters
| Name | Type | Required | In | Description |
|---|---|---|---|---|
connectionBizId | String | Required | path | Slash connection business ID. Path parameter |
request | Object | Required | body | Card creation payload. Structure depends on the Slash platform API. Request body (JSON) |
Success Response
Unauthorized 401
{
"code": "4010",
"message": "Invalid or expired JWT token"
}Error Responses
| HTTP Status | Code | Description |
|---|---|---|
| 401 | 4010 | Invalid or expired JWT token |
| 404 | 4040 | Connection not found |
| 400 | 4000 | Invalid request body |
Notes
- Returns HTTP 201 on success.
- The request body is forwarded to the Slash platform as-is. Refer to Slash API documentation for the expected payload structure.