Detail names and consent purposes in use
GET /v1/contacts/fields
GET
/v1/contacts/fields
What the filters can pick from: each detail name with how many people have it, how many distinct values, and its most common values; each consent purpose with how many people granted and withdrew it, built-ins marked built_in: true. Read it before recording a new name, so the same thing is not recorded under two.
Auth: Secret key only.
Authorizations
Section titled “Authorizations ”Responses
Section titled “ Responses ”{ details: [{ key, contacts, distinct_values, top_values }], consents: [{ purpose, granted, withdrawn, built_in }] }
Error envelope. See error.code for the discriminator.
object
data
required
null
error
required
object
code
required
string
message
required
string
remediation
required
string
doc_url
string format: uri
param
string
request_id
string
meta
object
key
additional properties
Error envelope. See error.code for the discriminator.
object
data
required
null
error
required
object
code
required
string
message
required
string
remediation
required
string
doc_url
string format: uri
param
string
request_id
string
meta
object
key
additional properties