canonical: https://jentic.com/apis/popl.co/popl-api

# Popl API

Popl is a digital business card and lead management platform that replaces physical cards with NFC-enabled devices and QR codes. The Popl API provides programmatic access to lead data captured from card taps and QR scans, team member management, tagging systems, and template link configuration. Sales teams and networkers use Popl to instantly share contact information, social profiles, and portfolio links, while the API enables CRM integration, lead routing, and analytics workflows. When someone taps a Popl card or scans a code, their contact information is captured and made available via the API for immediate follow-up. Enterprise teams use the API to aggregate leads across team members, enrich lead data with custom tags, and sync to Salesforce or HubSpot. The platform supports team-based lead management where admins can retrieve leads captured by any team member and implement custom lead qualification workflows.

## For AI agents

Manage digital business card leads, team members, tags, and template links captured from NFC card taps and QR code scans.

## Scope

Provides lead capture and team management for digital business card interactions. Does not perform contact enrichment, email validation, or CRM operations-use dedicated data enrichment and CRM APIs for those capabilities.

## Capabilities

- Retrieve leads captured from Popl card taps and QR code scans
- Access the most recent lead for individual team members
- Query leads captured across entire teams with aggregation
- Manage tags for organizing and categorizing leads
- Configure template links for digital business card profiles
- Delete leads for compliance and data management
- Access sub-team lead data for hierarchical team structures

## Use cases

### Sales Team Lead Capture and CRM Integration

Sales teams use Popl cards at conferences, trade shows, and client meetings to capture leads instantly via card tap or QR scan. The API enables automated CRM workflows where leads flow from Popl to Salesforce or HubSpot within minutes. Integration services poll the API for new leads, enrich contact data with company information from Clearbit, assign leads to account owners based on territory rules, and create CRM tasks for follow-up. This eliminates manual business card transcription, reduces lead response time, and ensures no networking opportunity is lost.

Example prompt: Poll Popl API every 15 minutes for new leads, enrich lead data with company information, match lead to sales territory, create Salesforce lead record with Popl data, assign to account owner, send Slack notification for immediate follow-up.

### Event Networking and Lead Qualification

Event organizers and attendees use Popl to manage connections made during conferences and networking events. The API enables retrieving all leads captured during a specific event timeframe, tagging them with event name and context, and implementing qualification workflows. Marketers query the API post-event to export attendee contact lists, segment by booth vs. session interactions (using custom tags), and trigger email nurture campaigns. The API's tagging system allows marking hot leads for immediate sales outreach vs. long-term nurture segments.

Example prompt: Retrieve all Popl leads from conference date range, apply event name tag, implement lead scoring based on job title and company size, segment into hot/warm/cold categories, export high-value leads to sales team, add others to marketing nurture campaign.

### Team Performance Analytics and Lead Attribution

Sales leaders use the API to analyze team networking performance, attributing lead generation and meeting outcomes to individual team members. The API enables querying leads by team member, time period, and tag categories to calculate lead volume metrics, conversion rates, and source attribution. Analytics dashboards display leaderboards showing top performers by leads captured, while attribution models connect closed deals back to original Popl interactions. This quantifies networking ROI and informs event attendance and business card distribution strategies.

Example prompt: Query Popl API for all team leads from past month, group by team member, calculate lead counts and tag distributions, match leads to closed deals in CRM, generate performance report showing lead-to-close rates, display team leaderboard.

### Automated Lead Enrichment and Routing

Revenue operations teams build automated workflows that enrich Popl leads with additional data and route them to appropriate sales queues. The API retrieves raw lead contact information which is enriched using Clearbit, ZoomInfo, or Apollo APIs to add company size, revenue, and technology stack. Enriched leads are scored based on ideal customer profile fit, then routed to enterprise AEs vs. SMB reps, or to partners vs. direct sales teams. This maximizes lead value by ensuring qualified leads reach the right seller within minutes of capture.

Example prompt: Fetch new Popl leads via API, enrich with Clearbit company data, score lead based on company size and industry fit, route high-scoring leads to enterprise sales queue, medium scores to inside sales, low scores to marketing, log enrichment and routing in CRM.

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/api/pub/leads/getLastLead` | Get the most recent lead for the authenticated user |
| GET | `/api/pub/leads/getLastLeadTeam` | Get all recent leads for the entire team |
| GET | `/api/pub/leads/getLastLeadSubTeam` | Get recent leads for a sub-team |
| POST | `/api/pub/lead/{leadId}/tags` | Add tags to a specific lead |
| DELETE | `/api/pub/leads/deleteLead` | Delete a lead |

## Key resources

- **Leads** — Contact information captured from card taps and QR scans.
- **Tags** — Organizational labels for categorizing and segmenting leads.
- **Team Members** — Individual and team-level lead access management.
- **Template Links** — Digital business card profile configuration.

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 67 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 93 / 100
  - Developer Experience & Jentic Compatibility: 56 / 100
  - AI-Readiness & Agent Experience: 55 / 100
  - Agent Usability: 94 / 100
  - Security: 50 / 100
  - AI Discoverability: 100 / 100
- **View full report:** https://jentic.com/apis/popl.co/popl-api/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **Setup:** Wiring Popl by hand means learning that its API key travels in the Authorization header and needs Full Team Admin permissions, then attaching it to every lead request yourself. Through Jentic you install once, import Popl from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** Popl puts the lead id in the URL path (`/api/pub/lead/{leadId}/tags`), so a rule can pin your agent to reading and tagging leads: you choose the operations it may call, so destructive ones like deleting a lead are not included unless you add them.
- **Credential handling:** Your Popl API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'retrieve the last lead from a digital business card' or 'tag a lead', and Jentic returns the matching Popl operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Clearbit Enrichment API** — Clearbit enriches contact data with company information, employee count, and technology stack.
- **Apideck Lead API** — A unified CRM and lead-management API from Apideck, offering an alternative to Popl for capturing and syncing contacts across sales tools.

## FAQ

### What authentication does the Popl API use?

The Popl API uses Bearer token authentication. You generate API keys from the Popl Teams dashboard (requires Full Team Admin permissions) and include the token in the Authorization header for all requests.

### How do leads get captured in Popl?

Leads are captured when someone taps your Popl NFC card or device with their phone, or scans your Popl QR code. The contact information they provide is stored and accessible via the API for CRM integration and follow-up workflows.

### Can I retrieve leads for my entire sales team?

Yes, the API provides team-level endpoints like getLastLeadTeam that retrieve leads captured by all team members. This enables team analytics, centralized CRM syncing, and lead routing workflows managed by sales operations.

### How do tags work in the Popl API?

Tags are custom labels you apply to leads for organization and segmentation. The API allows adding tags to leads programmatically, enabling automated workflows like tagging by event, lead source, or qualification status for filtering and routing.

### How do AI agents use the Popl API through Jentic?

Agents search Jentic for tasks like 'sync Popl leads to CRM' and receive Popl operation schemas. Jentic securely stores API keys, handles authentication, and allows agents to retrieve leads, apply tags, and integrate with CRM systems using natural language instructions.

### Can I limit what my agent is allowed to do with the Popl API?

Yes. Because you self-host Jentic One, you decide which Popl operations your agent may call, so you can allow it to read leads with getLastLead and getLastLeadTeam and to add tags to a lead while withholding everything else. Since Popl puts the lead id in the URL path (`/api/pub/lead/{leadId}/tags`), your own rules can pin the agent to reading and tagging leads. Destructive operations such as deleteLead stay off unless you explicitly grant them.