Add User to Suppression List
Changed onAdd a user to the suppression list for a given channel.
Note: If both distinct_id and destination are provided, distinct_id takes precedence, and destination is ignored.
Example request:
POST {{API_URL}}/v1/{{WSID}}/suppressions
Request
- Base URLhttps://api.fyno.io/v1
- URLhttps://api.fyno.io/v1/{WSID}/suppressions
- AuthHTTP bearer
Path parameters
Enter your workspace ID. You can obtain this value from the API Keys page within your Fyno account.
Request body
Example request
{
"distinct_id": "XXXXXXXX",
"channel": "email",
"event_type": [
"marketing",
"transactional",
"otp"
],
"description": "DND",
"expiry_ts": "2025-08-15T16:25:16.302+05:30"
}Response
Suppression list updated. _message reflects whether a new suppression record was created ("User has been added to the suppression!", with _id returned) or an existing record for that distinct_id/destination and channel was updated ("User record has been updated!", _id omitted).
Example response
{
"status": "ok",
"_message": "User has been added to the suppression!"
}Changes
- breaking
the request's body type changed from
objectto no type - warning
removed the request property
- warning
removed the request property
- warning
removed the request property
- warning
removed the request property
- warning
removed the request property
- warning
removed the request property
- info
added
subschema #1subschema #2to the request bodyoneOflist
- breaking
- breaking
added the new required request property
- breaking
removed
subschema #1subschema #2from the request bodyoneOflist - breaking
the request's body type changed from no type to
object - warning
removed the optional property
from the response with the status - info
added the new optional request property
- info
added the new optional request property
- info
added the new optional request property
- info
added the new optional request property
- info
added the new optional request property
- breaking