Reject Connection

Reject the connection request for the requesting user.

post

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.

Header parameters

sessionTokenstringRequired

Session authentication token.

Body

application/json

Request body for the Connection APIs

userIdinteger · int64Optional

user id

Example: 769658112378

Responses

200

Success

application/json

400

Client error, see response body for further details.

application/json

401

Unauthorized: Invalid session token.

application/json

403

Forbidden: Caller lacks necessary entitlement.

application/json

404

Not Found: Connection cannot be found.

application/json

500

Server error, see response body for further details.

application/json

post

/v1/connection/reject

HTTPcURLJavaScriptPython

POST /pod/v1/connection/reject HTTP/1.1
Host: yourpodURL.symphony.com
sessionToken: text
Content-Type: application/json
Accept: */*
Content-Length: 23

{
  "userId": 769658112378
}

{
  "userId": 769658112378,
  "status": "ACCEPTED",
  "firstRequestedAt": 1470018073812,
  "updatedAt": 1471018076255,
  "requestCounter": 1
}

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