Skip to main content
POST
/
datasource
/
im
/
person
/
try-link
Attempt IM person linking
curl --request POST \
  --url 'https://api.flashcat.cloud/datasource/im/person/try-link?app_key=' \
  --header 'Content-Type: application/json' \
  --data '
{
  "integration_id": 6113996590131
}
'
{
  "request_id": "01HK8XQE3Z7JM2NTFQ5YJ8P9R4",
  "data": {
    "new_linked_person_ids": [
      5348648172131
    ]
  }
}

​
Restrictions

AspectValue
Rate limits1,000 requests/minute; 50 requests/second per account
PermissionsIntegrations Manage (on-call)

​
Usage

  • The server uses member email and phone values to find matching users in DingTalk, Feishu, or WeCom.
  • If no member can be linked, the response contains an empty new_linked_person_ids array.

Authorizations

​
app_key
string
query
required

App key issued from the Flashduty console under Account → APP Keys. Required on every public API call. Keep it secret — it grants the same access as the owning account.

Body

application/json

Parameters for attempting automatic IM account linking.

​
integration_id
integer<int64>
required

IM integration ID.

Response

Success

Success response envelope. On every 2xx response, request_id identifies the call (also mirrored in the Flashcat-Request-Id header) and data holds the endpoint-specific payload. Failure responses use a different shape — see ErrorResponse.

​
request_id
string
required

Unique ID for this request. Mirrored in the Flashcat-Request-Id response header. Include it when reporting issues.

Example:

"01HK8XQE3Z7JM2NTFQ5YJ8P9R4"

​
data
object
required

People linked by this attempt.