Veribl logo

Connect Veribl to the systems you already run.

A REST API for products, passports, help articles, spare parts, registrations and contacts, and webhooks that tell your other tools the moment something happens. For your ops, IT and e-commerce teams and their developers.

What the API covers

Read and change your product content, passports and owner data from your own systems.

Products

Create, update and archive products with their GTIN, model, warranty, materials and certifications. Each new product gets its product page and QR code.

Passports

Fill passport data, read the checklist of what each EU rule still needs, publish a new version and read the version history. Battery data per serial number.

Help articles and translations

Create the articles on each product page, group them into categories, and save each one in every language you publish in.

Manuals and files

Upload PDFs and images, attach manuals to products, and read a manual's text back out.

Spare parts and accessories

Add spare parts, accessories and consumables with part numbers and repair details. Spare parts also show on the passport.

Registrations and contacts

Read every registered unit with its owner, and one row per owner with their marketing consent. Read-only, so customer data can't be changed from outside.

REST API

Plain JSON, one key per system.

Send a key with each request and get JSON back. Lists are paged, dates are ISO 8601, and errors come with a code your system can act on.

  • Access per area

    Give each key no access, read, or read and write for products, passports, articles, registrations and contacts.

  • Rotate without downtime

    A rotated key keeps working for 7 days, so you can swap it in your systems without breaking anything.

  • See every call

    API activity in Settings shows each key's calls and errors for the last 14 days.

Webhooks

Know the moment something happens.

Add an HTTPS URL in Settings › Webhooks and Veribl sends it a JSON request for each event you pick: a registration, a claim, a product change.

  • Signed

    Every delivery is signed with your endpoint's secret, so your server can check it came from Veribl.

  • Retries automatically

    If your endpoint is down or returns an error, Veribl tries the delivery again.

  • Test and inspect

    Send a test event, then read the delivery log: each event, its payload and how your endpoint answered.

15 events you can subscribe to

Send all of them to one URL, or choose the events each endpoint receives.

Owners and registrations

  • consumer.registered

    A customer registers a product

  • consumer.scanned

    A customer scans a product QR code

  • consumer.feedback_submitted

    A customer sends feedback

  • consumer.unsubscribed

    A customer unsubscribes from emails

  • consumer.health_changed

    An owner moves to Happy, Neutral or At risk

Support and claims

  • consumer.chat_completed

    An AI support chat ends

  • consumer.chat_escalated

    The AI hands a chat to your team

  • consumer.conversation_created

    A new helpdesk conversation starts

  • consumer.conversation_replied

    A customer replies in a conversation

  • consumer.claim_submitted

    A customer submits a warranty claim

  • consumer.claim_updated

    A warranty claim changes status

Products

  • product.created

    A product is created

  • product.updated

    A product is changed

  • product.status_changed

    A product goes live, back to draft or is archived

  • product.deleted

    A product is deleted

What teams connect

Common ways brands wire Veribl into the tools they already use.

New registration to your CRM

When an owner registers, a webhook sends them to your CRM or email tool, for example HubSpot or Klaviyo, with their product and consent.

Products from your PIM or ERP

Keep product names, GTINs, materials and certifications in one system and sync them to Veribl through the API.

Claims into your helpdesk

When a customer submits a warranty claim or the AI hands a chat to your team, a webhook opens a ticket where your team already works.

Passports from your PLM

When a product's data changes in your PLM, fill the passport fields and publish a new version, with a note for the history.

Alert the account team

When an owner moves to At risk, a webhook posts it to the team that can step in before a return or a bad review.

No code? Connect Claude

Give Claude your PDF manuals and it writes the product pages through the same access, without a developer.

See Connect Claude

For IT teams

Only the access each system needs.

Keys belong to your company, not to the person who made them, and every change a key makes is in the audit log.

  • Customer data stays scoped

    Registrations and contacts are read-only. Each contact carries its marketing consent, and a key only sees your company's data.

  • Revoke in one click

    A leaked key stops working the moment you revoke it.

  • Single sign-on

    Your team signs in to Veribl with your identity provider through SAML single sign-on, on Growth and Enterprise.

Get started

From a new key to your first call or event.

  1. Step 1

    Create a key

    In Settings › API keys, name the key after the system that uses it and choose its access per area.

  2. Step 2

    Make a call or add a webhook

    Call https://app.veribl.com/api/v1 with the key, or add your URL in Settings › Webhooks and pick events.

  3. Step 3

    Test and watch

    Send a test event and follow your calls and deliveries in the activity and delivery logs.

Frequently asked questions

Turn every product into your best channel.

Start free in minutes, or book a personalized walkthrough with our team.