How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Plunk Contacts API

Manage contacts and their subscription state.

Plunk Contacts API is one of 7 APIs that Plunk publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Contacts. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 10 operations across 5 paths, and defines 9 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against 2 base URLs: https://next-api.useplunk.com, https://api.useplunk.com/v1.

10 operations 5 paths 9 schemas 2 DELETE3 GET1 PATCH3 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://api.useplunk.com/v1
Authentication
HTTP Bearer, HTTP Bearer
Resource Areas
1

Authentication & Security 2

Plunk Contacts API declares 2 security schemes for authenticating requests. It accepts HTTP bearer tokens (API Key) (ApiKeyAuth). It accepts HTTP bearer tokens (bearerAuth).

  • ApiKeyAuth — API Key authentication. The project is automatically derived from the key. /v1/track requires a public key (pk) — it is the one endpoint intended for client-si…
  • bearerAuth — Plunk API key passed as a Bearer token. Use a secret key (sk) for most endpoints; the /track endpoint additionally accepts a public key (pk).

Paths & Operations 10

Across 5 paths, the API surfaces 10 operations — 2 DELETE, 3 GET, 1 PATCH, 3 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

Contacts 10

Contact management operations

GET
/contacts
List contacts
listContacts 6 params → 200401
POST
/contacts
Create or update contact
createContact body → 200201400401
PUT
/contacts
Update a contact
updateContact body → 200401404
DELETE
/contacts
Delete a contact
deleteContact body → 200401404
GET
/contacts/{id}
Get contact
getContact 1 param → 200401404
PATCH
/contacts/{id}
Update contact
updateContact 1 param body → 200401404409
DELETE
/contacts/{id}
Delete contact
deleteContact 1 param → 204401404
GET
/contacts/count
Count contacts
getContactCount → 200401
POST
/contacts/subscribe
Subscribe a contact
subscribeContact body → 200401404
POST
/contacts/unsubscribe
Unsubscribe a contact
unsubscribeContact body → 200401404

Schemas 9

The contract defines 9 schemas that model the data the API accepts and returns. The most detailed are Contact (6 properties), Contact_2 (6 properties), Error_2 (5 properties), UpdateContactRequest (4 properties). Each schema is shown below with its type and property counts.

Contact
object
6 properties
FieldError
object
4 properties
LegacyError
object
Flat error shape returned by the hand-validated create/update endpoints (POST /contacts, POST /templates, POST /segments) for missing required fields. Unlike t…
1 property
Error
object
3 properties
UpdateContactRequest
object
4 properties 1 required
CreateContactRequest
object
3 properties 1 required
Contact_2
object
6 properties
ContactSubscriptionRequest
object
1 property 1 required
Error_2
object
5 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

plunk-contacts-api-openapi.yml Raw ↑

Other APIs Plunk publishes across the network.

Plunk Campaigns API
Plunk Events API
Plunk Transactional API
Plunk Public API
Plunk Segments API
Plunk Templates API
Where this information came from

This is an independent, third-party profile of Plunk Contacts API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.