Go to Dark mode
Go to Light mode

Webhook Documentation - V1.0.0


Why use webhooks

Webhooks are a great way to get updates and events that occur on your Unlimited3D account, or on user accounts connected to your app. Using webhook, you will get notified about events happening and can run actions on your backend based on these events.

After registering your webhook endpoint Unlimited3D will push real time notifications to it when events happen in associated accounts. These notifications are sent over HTTPS using JSON as payload, and have signature assigned to them, generated using the secret you get after creating a webhook endpoint, so you can validate that the event was indeed sent by Unlimited3D.

Getting Started

Create webhook endpoint

Process for creating webhook endpoints differs for users and applications.

For users, go to Account -> Webhooks and create a webhook endpoint with a URL to your backend service. If creation is successful you will get a webhook secret. Please save this secret, as you will not be able to see or change it later.

For apps, when contacting our support, please specify that you will want to have a webhook endpoint associated with your app. After the app is created, you will receive webhook secrets alongside app information. Whenever a new user authorizes your app, your webhook endpoint will be registered for that user as well.

Payload format

Payload sent to your webhook endpoint will always be JSON. This JSON payload will always be in following format:

Name Type Description
id string Id of the webhook event, generated by Unlimited3D.
version string API version that indicates the Unlimited3D version used, as well as event format.
time timestamp Time at which event was emited.
type string Type of webhook event. How you will process the event is based on this parameter. Event data will differ based on the event type.
data object Data of the event, containing information necessary to perform actions related to the event. Structure of data depends on the event type.
    "id": "123456",
 	"version": "v10",
 	"time": 1632124827,
	"type": "job.finished",
 	"data": {
 		 "res": {}

Receive webhook events

Unlimited3D will send webhook events to your endpoint using the POST method.

Validate signature

First thing your code should do is verify that the event was sent by Unlimited3D by checking the signature that is sent in the payload.

Signature is included in the header of the webhook request. Hash-based message authentication code (HMAC) with SHA-256 is used to generate the signature. In order to validate the signature, you should generate it on your end, using the following process.

Concatenate time (as a string), the ; character and the JSON payload, then compute the HMAC with the SHA256 hash function using this above generated string that and webhook secret as key and compare it to the received signature.

Node.js example code:

const data = req.body;
const headers = req.headers;

const hmac = crypto.createHmac('sha256', YOUR_WEBHOOK_SECRET);
const signature = hmac.update(`${data.time};NULL`).digest('hex');

// You can now compare generated signature
// with the one received in request header
signature === headers['u3d-signature']

If signatures do not match, do not proceed, as you can not be sure that the event was sent by Unlimited3D. If signatures match, you can proceed with your logic related to that event.

Validate time

We also recommend that you compare time in the request with your server's current time to validate if the difference is within your tolerance.

Return a 2xx status code

To mark an event received your endpoint must return a 2xx HTTP status code to Unlimited3D. All other response codes outside this range including 3xx will indicate that you did not receive the webhook event.

Error handling and event resending

If your endpoint can not be contacted, or return non 2xx HTPP status code, Unlimited3D will automatically start the retry process. Basically Unlmited3D will keep sending the event to your endpoint in predefined periods and up to 7 times, until the event is confirmed to be successfully received.

We call this event lifecycle and it is as following:

  • First webhook event sent
  • 5 mins after 1st sent&fail
  • 1 hour after 2nd sent&fail
  • 24 hours after 3td sent&fail
  • 24 hours after 4th sent&fail
  • 24 hours after 5th sent&fail
  • 24 hours after 6th sent&fail
  • After 7th sent&fail we will stop sending webhook event

Event Types


Event types specify what happened on the user's account and what action your application should perform. Event’s data is different based on the event type and corresponds to data presented in this section.

This section lists all currently available event types. This document will be updated with all new event types as they are added.

Job Finished

Job finished is sent when the job queued using third party API finishes processing.

Name Type Description
id string Id of the job
status string Indicates the status of the job. Can be either finished or in_progress.
type string Type of the job. Currently supported types are: AddModelToSolution, PublishSolution, ConvertModel and UploadOptimizeModel.
result object Result of the job. Schema depends on the job type.
errors array Array of errors connected to the job. Empty array indicates that there were no errors while processing the job.
warnings array Array of warnings connected to the job. Empty array indicates that there were no warnings while processing the job.

Data schema for this event is as following:

   "id": "14456",
   "status": "finished",
   "type": "AddModelToSolution",
   "result": {},
   "errors": [],
   "warnings": []



Result of the job. Schema depends on the job type.


Returns ID and URL of the solution to which the model was added.



Contains information about the newly created distribution of the solution.

	"id": "5540",
	"status": "live",
	"note": "",
	"link": "https://dist.unlimited3d.com/dists/project-name/test-auto/12932/5540",
	"script_link": "https://cdn.unlimited3d.com/pres/v/2.0.0-b1/unlimited3d.min.js",
	"solution3d_id": "12932",
	"slug_solution3d_name": "test-auto",
	"slug_project_name": "project-name",
	"distribution_version": "2.0.0-b1",
	"stop_after_date": null,
	"pause_date_views": null,
	"created_at": "2021-10-20T12:24:04.000000Z",
	"updated_at": "2021-10-20T12:24:06.000000Z"


Contains URL of the converted model.



Contains the information about exported optimized model.

     "tags":["first", "second"],