Products
Create, update and archive products with their GTIN, model, warranty, materials and certifications. Each new product gets its product page and QR code.
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.
Read and change your product content, passports and owner data from your own systems.
Create, update and archive products with their GTIN, model, warranty, materials and certifications. Each new product gets its product page and QR code.
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.
Create the articles on each product page, group them into categories, and save each one in every language you publish in.
Upload PDFs and images, attach manuals to products, and read a manual's text back out.
Add spare parts, accessories and consumables with part numbers and repair details. Spare parts also show on the passport.
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
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.
Give each key no access, read, or read and write for products, passports, articles, registrations and contacts.
A rotated key keeps working for 7 days, so you can swap it in your systems without breaking anything.
API activity in Settings shows each key's calls and errors for the last 14 days.
Webhooks
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.
Every delivery is signed with your endpoint's secret, so your server can check it came from Veribl.
If your endpoint is down or returns an error, Veribl tries the delivery again.
Send a test event, then read the delivery log: each event, its payload and how your endpoint answered.
Send all of them to one URL, or choose the events each endpoint receives.
consumer.registeredA customer registers a product
consumer.scannedA customer scans a product QR code
consumer.feedback_submittedA customer sends feedback
consumer.unsubscribedA customer unsubscribes from emails
consumer.health_changedAn owner moves to Happy, Neutral or At risk
consumer.chat_completedAn AI support chat ends
consumer.chat_escalatedThe AI hands a chat to your team
consumer.conversation_createdA new helpdesk conversation starts
consumer.conversation_repliedA customer replies in a conversation
consumer.claim_submittedA customer submits a warranty claim
consumer.claim_updatedA warranty claim changes status
product.createdA product is created
product.updatedA product is changed
product.status_changedA product goes live, back to draft or is archived
product.deletedA product is deleted
Common ways brands wire Veribl into the tools they already use.
When an owner registers, a webhook sends them to your CRM or email tool, for example HubSpot or Klaviyo, with their product and consent.
Keep product names, GTINs, materials and certifications in one system and sync them to Veribl through the API.
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.
When a product's data changes in your PLM, fill the passport fields and publish a new version, with a note for the history.
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.
Give Claude your PDF manuals and it writes the product pages through the same access, without a developer.
See Connect ClaudeFor IT teams
Keys belong to your company, not to the person who made them, and every change a key makes is in the audit log.
Registrations and contacts are read-only. Each contact carries its marketing consent, and a key only sees your company's data.
A leaked key stops working the moment you revoke it.
Your team signs in to Veribl with your identity provider through SAML single sign-on, on Growth and Enterprise.
From a new key to your first call or event.
In Settings › API keys, name the key after the system that uses it and choose its access per area.
Call https://app.veribl.com/api/v1 with the key, or add your URL in Settings › Webhooks and pick events.
Send a test event and follow your calls and deliveries in the activity and delivery logs.
Start free in minutes, or book a personalized walkthrough with our team.