Reject Connection

Accept the connection request from a requesting user.
post
https://yourpodURL.symphony.com/pod
/v1/connection/reject
Reject the connection request for the requesting user.

Reject the connection between the requesting user and request sender. If both users are in the same private pod, an error will be returned because both users have an implicit connection which cannot be rejected.

Parameters
Header
sessionToken*
string
Session authentication token.
Body
userId
integer
user id
Body
Example
Schema
{
"userId": 769658112378
}
Responses
200: OK
Success
400: Bad Request
Client error, see response body for further details.
401: Unauthorized
Unauthorized: Invalid session token.
403: Forbidden
Forbidden: Caller lacks necessary entitlement.
404: Not Found
Not Found: Connection cannot be found.
500: Internal Server Error
Server error, see response body for further details.
This endpoint allows the user to reject a specific connection request. To define which connection request is to be rejected, the userId of the user who initiated the connection request must be included in the body.
Pods from all users involved need to have crossPod enabled between them.

📘 Rejected Connections

Reject the connection between the requesting user and request sender. If both users are in the same private pod, an error will be returned because both users have an implicit connection which cannot be rejected.

Connection Behaviour

Currently, there are four possible connection status:
  • PENDING_INCOMING: The specified user requested to connect with the calling user.
  • PENDING_OUTGOING: The calling user requested to connect with the specified user.
  • ACCEPTED: The two users are connected.
  • REJECTED: The two users are not connected.
The following table shows the connection current behaviors:
Initial Connection Status
Request Action
New Connection Status
None (connection did not exist)
Connect
PENDING_OUTGOING
PENDING_INCOMING
Accept
ACCEPTED
PENDING_INCOMING
Reject
REJECTED
Last modified 2mo ago