Complete attachment upload

Purpose

This call is used to confirm that a file has been uploaded. It is the last of the three calls described in Attachments.

TomTom checks the uploaded file against the file type and size you declared when you started the upload. If everything matches, the attachment is added to the feedback and its status becomes ACTIVE.

How to request data

HTTP method: POST

• Constants and parameters enclosed in curly brackets { } must be replaced with their values.
• Please see the following Request parameters section with the required and optional parameters tables for these values. The generic URL format is as follows.

URL request format

1
https://{baseURL}/maps/orbis/feedback/{feedbackId}/attachments/{attachmentId}/complete?key={API-key}&apiVersion={version}

This call has no request body.

Request parameters

The following table describes the parameters that can be used in a request.

• Required parameters must be used or the call will fail.

Response data

The response describes the attachment. Its status tells you the outcome:

• ACTIVE - the file was accepted and is now part of the feedback.
• FAILED - the file could not be accepted. This happens when nothing was uploaded to the link, when the link expired before the upload, or when the uploaded file does not match the type or size you declared. Start again with a new Initiate attachment upload call.

Repeating this call for an attachment that is already ACTIVE is safe and simply returns the same result.

Response codes

1
{
2
  "attachment": {
3
    "attachmentId": "6b48dd3c-6d0c-4b0a-9a6e-1f1c0e2a51f4",
4
    "feedbackId": "7049aa04-91bd-4ad3-8085-bd8bec318905",
5
    "status": "ACTIVE",
6
    "displayFilename": "missing-road-sign.png",
7
    "contentType": "image/png",
8
    "sizeBytes": 20480,
9
    "createdAt": "2026-09-23T10:07:41.114166"
10
  }
11
}

1
{
2
  "errorText": "Validation failed",
3
  "detailedError": {
4
    "code": "BAD_REQUEST",
5
    "message": "attachmentId: must be 1-64 letters, digits or hyphens"
6
  },
7
  "httpStatusCode": 400
8
}

1
{
2
  "detailedError": {
3
    "code": "Forbidden",
4
    "message": "You are not allowed to access this endpoint"
5
  }
6
}

1
{
2
  "errorText": "Attachment '6b48dd3c-6d0c-4b0a-9a6e-1f1c0e2a51f4' not found for feedback '7049aa04-91bd-4ad3-8085-bd8bec318905'",
3
  "detailedError": {
4
    "code": "NOT_FOUND",
5
    "message": "Attachment '6b48dd3c-6d0c-4b0a-9a6e-1f1c0e2a51f4' not found for feedback '7049aa04-91bd-4ad3-8085-bd8bec318905'"
6
  },
7
  "httpStatusCode": 404
8
}

1
{
2
  "errorText": "An unexpected error has occurred. Please try again later.",
3
  "detailedError": {
4
    "code": "INTERNAL_SERVER_ERROR",
5
    "message": "An unexpected error has occurred. Please try again later."
6
  },
7
  "httpStatusCode": 500
8
}