Automation — API & webhooks

A single call for the whole way from customer photo to engraving file.

POST /v1/prepare

Takes an image, prepares it with your recipe and returns the laser-ready file.

Authentication

Customer key in the request header; without a valid key the endpoint answers 401.

Scope

Every key carries its purpose; if it does not cover the call, the endpoint answers 403.

Limits

Image size and output area are capped so a single call cannot block production.

Your system learns the outcome without asking.

job.completed

Reports the finished job to your endpoint.

job.failed

Reports the failure — more valuable than the success, because an unusable image has to reach you before your customer does.

Signature

Every delivery is signed so you can verify it really came from Vextrify.

Address check

Targets inside private networks are refused, so delivery cannot be turned into a tool against your own network.

In your account under Developer.

Create key

Issues a key with purpose and expiry; the value is shown once.

Revoke key

Takes one access path out of service without touching the others.

Delivery attempts

Shows whether and when a webhook arrived — the first place to look when something is missing.

The same endpoint, driven by an automation service.

Zapier, Make, n8n

Call the endpoint and pass the result on — to a spreadsheet, shop, CRM, storage or a notification.

Your own scripts

Any language that speaks HTTP is enough; no Vextrify library required.

• One key per purpose: if one leaks, you close only that door.
• Build the recipe in Photo Studio first, then automate — the API uses the same recipe.
• Always verify the signature, otherwise anyone can push something into your system.