Article 4 of 8
Who calls whom
Your system calls Watch Certificate™. We write to the owner.
Your system calls the API
Your ERP, your point-of-sale software or your website's server calls the API with your key, server to server. Keep the key on your server: it must never be in a web page or in a mobile app.
Watch Certificate™ does not call your system: there is no notification to your servers today. To know the state of a watch or a passport, you read it, for example with your own reference (GET /certificates/by-external-ref/{ref}).
We write to the owner
When you declare the buyer, Watch Certificate™ sends them an email in their language. They confirm they are the owner and open their passport in the app; an account is created for them if they have none. You have nothing to send them.
The card links to the watch
Each passport is linked to a physical card: a number and a code printed on it, and a QR code that opens the passport's public page. You link the card to the watch through the API, when you hand it over.
In short
| Who | Does what |
|---|---|
| Your system | Creates the watch, sends the photos, links the card, declares the buyer, records the services |
| The Watch Certificate™ API | Checks, creates the passport, answers your reads |
| Watch Certificate™ | Writes to the owner, gives them access to their passport |
| The owner | Confirms, reads, transfers their passport at the resale |