What the address agreed to
GET
/v1/addresses/{address}/consent
const url = 'https://api.proxymail.qa/v1/addresses/k7f2x9ab12cd%40mailclub.dev/consent';const options = {method: 'GET', headers: {Authorization: 'Bearer <token>'}};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request GET \ --url https://api.proxymail.qa/v1/addresses/k7f2x9ab12cd%40mailclub.dev/consent \ --header 'Authorization: Bearer <token>'In Labs: answers 403 until the key’s creator switches on Marketing and offer emails in Account settings → Labs.
Authorizations
Section titled “Authorizations”Parameters
Section titled “Parameters”Path Parameters
Section titled “Path Parameters”address
required
string format: email
The test address, URL-encoded. A variant also works: capitals, or a +tag (k7f2x9ab12cd+o’brien@mailclub.dev). It acts on the plain address; waiting on a +tag variant, or listing its messages, only finds mail sent to that variant.
Example
k7f2x9ab12cd@mailclub.devResponses
Section titled “Responses”Its consent
Media typeapplication/json
object
address
string
marketing
string | null
prechecked
boolean | null
at
string | null format: date-time
double_opt_in
string | null
double_opt_in_at
string | null format: date-time
via
string | null
country
The persona’s country, which decides the rules.
string | null
Example
{ "marketing": "opted_in", "double_opt_in": "confirmed", "via": "form"}An error
Media typeapplication/json
object
error
string
message
string
Example generated
{ "error": "example", "message": "example"}