PUT
/
v1
/
contacts
curl --request PUT \
  --url https://api.useplunk.com/v1/contacts \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: <content-type>' \
  --data '{
  "id": "<string>",
  "email": "<string>",
  "subscribed": true,
  "data": {}
}'

In most cases, it is recommended to use the track endpoint to update the metadata of a contact. When a new contact tracks an event Plunk will automatically create the contact instead of throwing a HTTP 404.l

​
Body

Either the id or email is required.

​
id
string

The ID of the contact you want to update

​
email
string

The email of the contact you want to update

​
subscribed
boolean

Whether the contact is subscribed or not

​
data
object

The metadata to update with the contact

​
Headers

​
Content-Type
string
required

application/json

PUT
/
v1
/
contacts
curl --request PUT \
  --url https://api.useplunk.com/v1/contacts \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: <content-type>' \
  --data '{
  "id": "<string>",
  "email": "<string>",
  "subscribed": true,
  "data": {}
}'

In most cases, it is recommended to use the track endpoint to update the metadata of a contact. When a new contact tracks an event Plunk will automatically create the contact instead of throwing a HTTP 404.l

​
Body

Either the id or email is required.

​
id
string

The ID of the contact you want to update

​
email
string

The email of the contact you want to update

​
subscribed
boolean

Whether the contact is subscribed or not

​
data
object

The metadata to update with the contact

​
Headers

​
Content-Type
string
required

application/json