Contact Management

Every interaction with your PingRep profile can become a saved contact. Whether someone scans your QR code at a conference, visits your profile on the web, or discovers you through an MCP-connected AI tool, the Contacts API lets you capture and manage those connections programmatically.

Check Contact Limits

Before saving contacts, check your plan's limits.

GET

/api/v1/contacts/limits

API Key

Get contact saving limits for the authenticated user.

Save a Contact

Save a new contact from any of the three supported sources: QR scan, web visit, or MCP interaction.

POST

/api/v1/contacts

API Key

Save a new contact to your contact list.

Request Body

profileIdstring (uuid)Required

The profile ID of the person you want to save as a contact.

sourcestringRequired

How this contact was captured. One of: qr_scan, web, or mcp.

Response

idstringRequired

Unique identifier for this saved contact.

profileIdstring (uuid)Required

The profile ID of the saved contact.

namestringRequired

Full name of the contact.

titlestringRequired

Professional title or role.

companystringRequired

Company or organization name.

locationstringRequired

Geographic location.

photoUrlstringRequired

URL to the contact's profile photo.

savedAtstring (ISO 8601)Required

Timestamp when the contact was saved.

List Saved Contacts

Retrieve all contacts you have saved.

GET

/api/v1/contacts

API Key

List all saved contacts for the authenticated user.

Delete a Contact

Remove a contact from your saved list.

DELETE

/api/v1/contacts/{contact_id}

API Key

Delete a saved contact by its ID.

Record a Profile Scan

Track when someone scans or views a profile. This feeds into your analytics.

POST

/api/v1/contacts/scans

API Key

Record a profile scan event.

Get Recent Scans

Retrieve recent scan events for your profile.

GET

/api/v1/contacts/scans

API Key

Get recent profile scan events.

Contact Sources

Use the source field to distinguish how contacts were captured. This helps you measure which channels drive the most connections: qr_scan for in-person events, web for online discovery, and mcp for AI-assisted interactions.