> For the complete documentation index, see [llms.txt](https://amast-einvoice.gitbook.io/amast-einvoice-sass/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://amast-einvoice.gitbook.io/amast-einvoice-sass/api/list-of-api/submission-status-api.md).

# Submission Status API

Returns the latest stored status for a batch. Each of this API response is based on updated status stored in our database after fetching from LHDN system periodically.

```http
GET /api/v1/saas/submissions/{submissionBatchId}/status
```

## Path parameter

| Name                | Description               |
| ------------------- | ------------------------- |
| `submissionBatchId` | UUID from submit response |

{% hint style="info" %}
Always use the provided internal submission batch id from this Platform, not external LHDN Submission ID.
{% endhint %}

## Response 200 

Sample is a batch submission with 2 document with Valid and Invalid end status respectively.

{% code overflow="wrap" %}

```json
{
  "submissionBatchId": "1b13d67a-5919-4a5d-8bb9-d230c27d57b7",
  "status": "Submitted",
  "lastUpdatedAt": "2026-06-03T03:38:02.298Z",
  "documents": [
    
    {
      "transactionId": "40699963-4267-466d-82e4-5990cfa03851",
      "documentId": "cbd3bf63-cf1d-4285-a37d-2520be66f5a6",
      "documentType": "invoice",
      "referenceId": "INV03062026-SANDBOXTEST-006",
      "lhdnStatus": "Valid",
      "lhdnSubmissionID": "KEMME586AC59EDM985EYR5TK10",
      "lhdnUUID": "N3FE0K0TS5RXDDJ285EYR5TK10",
      "createdAt": "2026-06-03T03:37:57.646Z",
      "updatedAt": "2026-06-03T03:38:02.206Z"
    },
    {
      "transactionId": "38bfdc90-6b01-4b68-8402-bfc4e53623aa",
      "documentId": "54f5d4c8-b578-457c-9f52-9e9eb8f26ef8",
      "documentType": "invoice",
      "referenceId": "INV03062026-SANDBOXTEST-007",
      "lhdnStatus": "Invalid",
      "lhdnSubmissionID": "KEMME586AC59EDM985EYR5TK10",
      "lhdnUUID": "N3FE0K0TS5RXDDJ285EYR5TK10",
      "createdAt": "2026-06-03T03:37:57.723Z",
      "updatedAt": "2026-06-03T03:38:02.298Z",
      "lhdnMessage": {
        "status": "Invalid",
        "validationSteps": [
          {
            "status": "Valid",
            "name": "Step03-Duplicated Submission Validator"
          },
          {
            "status": "Valid",
            "name": "Step04-Code Field Validator"
          },
          {
            "status": "Invalid",
            "error": {
              "propertyName": null,
              "propertyPath": null,
              "errorCode": "Error05",
              "error": "Step05-Invalid Taxpayer Profile Validator",
              "errorMs": "Step05-Pengesah Profil Pembayar Cukai Tidak Sah",
              "innerError": [
                {
                  "propertyName": "CustomerTin",
                  "propertyPath": "document.Invoice.AccountingCustomerParty.Party.PartyIdentification.ID",
                  "errorCode": "ERR406",
                  "error": "Buyer TIN is invalid. Kindly use the Search TIN function to get the correct TIN",
                  "errorMs": "TIN pembeli tidak sah. Sila gunakan fungsi Carian TIN untuk mendapatkan TIN yang betul",
                  "innerError": null
                },
                {
                  "propertyName": "CustomerIdentity",
                  "propertyPath": "document.Invoice.AccountingCustomerParty.Party.PartyIdentification.ID",
                  "errorCode": "ERR206",
                  "error": "NRIC/ARMY mismatch or not exist in HITS",
                  "errorMs": "NRIC/ARMY tidak sepadan atau tidak wujud dalam HITS",
                  "innerError": null
                }
              ]
            },
            "name": "Step05-Taxpayer Profile Validator"
          },
          {
            "status": "Valid",
            "name": "Step06-Document References Validator"
          },
          {
            "status": "Valid",
            "name": "Step07-Document Currency Validator"
          }
        ]
      }
    }
  ]
}
```

{% endcode %}

#### Per-document fields

| Field        | Dimension         | Typical values                                                                    |
| ------------ | ----------------- | --------------------------------------------------------------------------------- |
| `status`     | Internal pipeline | `Queued` → `Processing` → `Submitted` \| `SubmitFailed`                           |
| `lhdnStatus` | LHDN              | `null` until known, then `Submitted`, `Valid`, `Rejected`, `Invalid`, `Cancelled` |

Read both together. See [Status model](/amast-einvoice-sass/status-model.md).

## Example

```bash
curl -X GET "https://teinvoice.amastsales-sandbox.com/api/v1/saas/submissions/YOUR_SUBMISSION_BATCH_ID/status" \
  -H "X-API-Key: YOUR_API_KEY"
```

## Errors

| HTTP  | Meaning                         |
| ----- | ------------------------------- |
| `404` | Batch not found for your tenant |
| `401` | Invalid API key                 |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://amast-einvoice.gitbook.io/amast-einvoice-sass/api/list-of-api/submission-status-api.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.