This API operation adds blocked senders to the blocked senders list of the authenticated user.
POST
/v1/Email/BlockedSendersAdd
Property | Type | Description |
---|---|---|
OtherUserID |
integer | The UserID of the user you wish to block. Note: This is required when Nickname is not supplied. |
Nickname |
string | The nickname of the user you wish to block. Note: This is required when OtherUserID is not supplied. |
BlockBookings |
boolean | If all emails should be blocked when creating a Escort, Webcam and Phone Chat booking set this to true . |
BlockSales |
boolean | If all emails should be blocked when Sales and Auction purchase has been made set this to true . |
BlockDirectChat |
boolean | If all emails should be blocked when a DirectChat call is made set this to true . |
Reason |
string | The reason of the block. |
Parameters can be passed to this operation using the HTTP POST method with serialized JSON in the request body.
The REST API uses HTTP request headers to determine what data type is returned or to authenticate the developer's API key. More information can be found in the overview section.
An Authorization header is required with every request and must contain the access_token of the user. More information can be found in the Access tokens page.
This endpoint requires the following scope:
Scope |
---|
account_communications |
Property | Type | Description |
---|---|---|
This will return no model just a 200 OK HTTP Status code. |
The following example shows a sample returned by the API.