Ignore an email bounce
/reports/email-bounces/{bounce_id}Marks an email bounce as ignored so the user's address can receive email from the account again. Requires the email_bounces.ignore permission.
The only accepted value is ignored: true. This change cannot be reverted through the API.
To make the update conditional, send the bounce's current revision in the If-Match header. If the bounce has changed since that revision, the update is rejected.
Autonomous mode: the API credential secret, sent as a bearer token. Credential secrets are identified by a fixed prefix.
In: header
Path Parameters
Request Body
application/json
TypeScript Definitions
Use the request body type in TypeScript.
Response Body
application/json
application/json
application/json
application/json
application/json
application/json
curl -X PATCH "https://example.com/reports/email-bounces/string" \ -H "Content-Type: application/json" \ -d '{ "ignored": true }'{ "data": { "email": "string", "id": "string", "ignored": true, "kind": "bounced", "last_bounce_at": "2019-08-24T14:15:22Z", "object": "email_bounce", "revision": "string", "user_id": "string" }}List email bounces GET
Returns user email addresses that bounced, were dropped, were reported as spam, or were deferred. By default, only email bounces that have not been ignored are returned. Set `ignored=true` to list ignored email bounces instead. The `email` field is included only when the credentials also have the `users.read_personal` permission.
List exam performance GET
Returns aggregate performance metrics for each exam. Use `product_id` to limit the report to a single product. This report does not include individual answers or user names.