Build on Top of PinsCorner: REST API, GraphQL and Webhooks

A digital business card is only as powerful as the systems it talks to. When someone scans your card and fills in their details, that lead should land in your CRM instantly — not sit in a CSV you remember to export once a month. PinsCorner is built on Payload CMS, which means the entire data layer is exposed through a native REST and GraphQL API out of the box, plus a dedicated webhook system for real-time event delivery.

Whether you run a solo consulting practice, manage a sales team, or build products for clients, the API and webhook layer turns PinsCorner from a card-sharing tool into an active node in your business infrastructure.

REST and GraphQL: Two Ways to Query Your Data

PinsCorner gives you both REST and GraphQL access, authenticated with API keys you generate from your account settings. REST suits scripts, integrations and backend services that already follow a conventional request-response pattern. GraphQL suits front-end applications and situations where you want to fetch exactly the fields you need — no over-fetching, no multiple round trips.

Through the API you can read and write cards, contacts, leads, team members and more. This means you can build internal dashboards that display card analytics alongside your other business metrics, sync card data into a data warehouse for deeper reporting, or pre-populate cards programmatically when onboarding new team members at scale.

• Generate API keys per user or per integration, with scope control
• Query any collection — cards, leads, contacts, teams — via REST or GraphQL
• Write back to PinsCorner: create or update cards and contacts from external systems
• Use GraphQL to request only the fields your client needs, reducing payload size
• Access the Payload-native schema documentation directly from your dashboard

Signed Webhooks: React to Events the Moment They Happen

Polling an API is fine for batch jobs. For anything time-sensitive — a new lead, a card view, a contact save — you want a push. PinsCorner fires signed HMAC webhooks to any endpoint you configure, so your backend is notified the instant something happens rather than discovering it later.

HMAC signing means every webhook payload carries a signature computed from a shared secret. Your server verifies the signature before processing the event, which guarantees the request genuinely came from PinsCorner and has not been tampered with in transit. This is the same pattern used by Stripe, GitHub and other serious platforms — a simple but robust way to trust incoming data without opening up your endpoint to the public.

• Lead captured: fires when a visitor submits the lead-capture form on any card
• Card events: fires on card views, contact saves and QR scans
• Configure one or multiple endpoint URLs per event type
• Verify the HMAC signature in your handler before acting on the payload
• Retry logic built in for failed deliveries

Who Benefits Most

The API and webhook layer is genuinely useful across a wide range of teams. Sales teams can route every captured lead directly into their CRM — HubSpot, Salesforce, Pipedrive — without a human in the middle. Marketing teams can trigger automated email sequences the moment someone saves a card. Developers building white-label products for clients can manage hundreds of cards programmatically, keeping their own system of record in sync with PinsCorner.

Agencies and SaaS builders benefit from the Payload-native schema: because PinsCorner is built on Payload CMS, the API is not a thin wrapper bolted on after the fact. It is the same layer the admin panel uses, which means it is complete, documented and stable.

The best integrations are the ones you never have to think about: data flows automatically, leads arrive where they should, and your team spends time on conversations — not on copy-pasting contact details.

Getting Started

To connect an external system, generate an API key from your PinsCorner account settings, browse the auto-generated REST or GraphQL schema docs, and configure a webhook endpoint for the events you care about. Most integrations take under an hour to wire up. No-code tools like Make or Zapier can consume the webhooks too, so you do not need a developer to benefit from real-time lead routing.

If you are ready to plug PinsCorner into your stack, the API documentation is available inside your dashboard. Start with a free account and upgrade to a Pro or Team plan when you need higher API rate limits and full webhook history.