---
title: "Submit a message for an excise movement."
method: POST
path: "/customs/excise/movements/{movementId}/messages"
tags: ["Movements"]
---

# Submit a message for an excise movement.

`POST /customs/excise/movements/{movementId}/messages`

Submit a message for a specific excise movement. </br></br>

**Note:** The consignor ID or consignee ID in the message must match an excise reference number (ERN) in the bearer token that you use for API authentication. If it does not, a 403 Forbidden error will be thrown.

## Path parameters

- `movementId` string, uuid, required

## Headers

- `Accept` 'application/vnd.hmrc.1.0+json', required
- `Content-Type` 'application/vnd.hmrc.1.0+xml' | 'application/xml', required

## Response `202`

Accepted

## Other responses

- `400` — The submitted message has failed validation
- `401` — Authorisation errors, e.g. consignor or consignee not authorised, authorisation expired, invalid enrolment parameter.
- `403` — Consignor ID or consignee ID is not in authorisation bearer token
- `404` — Movement doesn't exist or downstream connection issues
- `422` — The message has failed validation
- `500` — Internal server error
- `503` — Downstream service is Unavailable

---

[API](https://skmtc.dev/hmrc/apis/excise-movement-control-system-api.md) · [All operations](https://skmtc.dev/hmrc/apis/excise-movement-control-system-api/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/hmrc/excise-movement-control-system-api/revisions/219deb5ade71/schema)