> ## Documentation Index
> Fetch the complete documentation index at: https://docs.idmetagroup.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Introduction to Australia DVS

> Overview of the Australia DVS APIs and how to interpret their results.

## Overview

The Australian Government's Document Verification Service (DVS) verifies key government-issued documents. As an approved Gateway Service Provider (GSP), IDmeta gives you access to DVS through the standard IDmeta API.

Australia DVS endpoints are part of the [Stateless Verification API](/stateless-verification-api/introduction). They verify document details against the issuing agency's records without a `trustFlowId` or `trustValidationId` — you submit the document fields in the request body and receive the result in the same response. There is no separate processing step to poll.

## Authentication

Use the same **Bearer token** authentication as all other v3 endpoints in the `Authorization` header. See [Introduction to the API](/api-reference/introduction#authentication) for how to create an API token.

## How it works

1. **Submit the document details** for the relevant document type (for example, `familyName`, `dob`, and `travelDocumentNumber` for a passport) as the JSON request body.
2. **DVS checks the submitted details** against the issuing agency's records.
3. **The response tells you whether the document is valid** — the result is returned in the same request/response cycle.

## Reading the response

Check `data.isValid` to determine whether the submitted details match the issuer's records. The overall outcome is also reflected in `verificationStatus` and `verificationStatusCode`:

| `verificationStatus` | `verificationStatusCode` | Meaning                                                                                        |
| -------------------- | ------------------------ | ---------------------------------------------------------------------------------------------- |
| `VERIFIED`           | `3`                      | The submitted details match the issuing agency's records.                                      |
| `REJECTED`           | `1`                      | The submitted details did not match.                                                           |
| `FAILED`             | `6`                      | The request could not be completed (for example, an internal error or DVS source unavailable). |

A document that fails verification still returns HTTP `200` with `success: true` — check `data.isValid` and `verificationStatus` to interpret the outcome. When `data.isValid` is `false`, `data.errors` identifies which request fields did not match, using the same camelCase field names as the request payload.

Optional `metadata` in the request is echoed back in the response, so you can attach your own reference (for example, an order or case ID) for correlation.

See [Passport](/stateless-verification-api/australia-dvs/passport) for a full request and response reference.