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

# Australia - DVS – Marriage Certificate

> Verifies input data against the Document Verification Service (DVS). Authoritative real-time identity lookup for Australia. Real-time lookup, pay-per-call.

<div hidden data-didit-db-validation-defaults="{&#x22;issuing_state&#x22;:&#x22;AUS&#x22;,&#x22;services&#x22;:&#x22;aus_marriage_certificate&#x22;,&#x22;consent&#x22;:&#x22;true&#x22;,&#x22;first_name&#x22;:&#x22;John&#x22;,&#x22;last_name&#x22;:&#x22;Doe&#x22;,&#x22;first_partner_name&#x22;:&#x22;Jamie&#x22;,&#x22;last_partner_name&#x22;:&#x22;Example&#x22;,&#x22;marriage_certificate_number&#x22;:&#x22;SAMPLE-MARRIAGE-12345&#x22;,&#x22;birth_registration_number&#x22;:&#x22;SAMPLE-BIRTH-12345&#x22;,&#x22;birth_registration_state&#x22;:&#x22;Sample State&#x22;,&#x22;birth_registration_date&#x22;:&#x22;1990-01-01&#x22;,&#x22;vendor_data&#x22;:&#x22;user-1234&#x22;}" />

Verifies input data against the Document Verification Service (DVS). Didit exposes this service through `POST /v3/database-validation/` so you can verify the submitted data against the authoritative source and receive normalized match results.

## Coverage

* **Coverage:** 100%\*
* **Country:** Australia
* **Service ID:** `aus_marriage_certificate`
* **Data domain:** Identity
* **Category:** CivilRegistry

## Inputs

| Field | Required | Example |
| - | -: | - |
| `first_name` | Yes | `John` |
| `last_name` | Yes | `Doe` |
| `first_partner_name` | Yes | `Jamie` |
| `last_partner_name` | Yes | `Example` |
| `marriage_certificate_number` | Yes | `SAMPLE-MARRIAGE-12345` |
| `birth_registration_number` | Yes | `SAMPLE-BIRTH-12345` |
| `birth_registration_state` | Yes | `Sample State` |
| `birth_registration_date` | Yes | `1990-01-01` |
| `vendor_data` | No | `user-1234` |

* **Required inputs:** `first_name`, `last_name`, `first_partner_name`, `last_partner_name`, `marriage_certificate_number`, `birth_registration_number`, `birth_registration_state`, `birth_registration_date`
* **Optional inputs:** `vendor_data`
* **Consent:** Required
* **Workflow availability:** Available in workflow with field mapping
* **Coverage:** 100%\*
* **Price:** \$0.45 per successful query

In a workflow, `first_partner_name`, `last_partner_name`, `birth_registration_state` and `birth_registration_date` are not printed on an identity document, so no step produces them on their own. Collect them from a Questionnaire answer, a Document AI extraction field, or a value you send when you create the session, and map each one on the Database Validation step. Until they are mapped the workflow editor shows this service disabled and names the missing input; at run time a missing input means the check is skipped before any query, so you are never billed for a database that could not be asked.

## Body parameters

<ParamField body="issuing_state" type="string" required default="AUS" placeholder="AUS">
  ISO 3166-1 alpha-3 country code for this database service.

  Example: `AUS`
</ParamField>

<ParamField body="services" type="string" required default="aus_marriage_certificate" placeholder="aus_marriage_certificate">
  Array containing this service ID. Pinning the service keeps the request scoped to this exact database.

  Example: `aus_marriage_certificate`
</ParamField>

<ParamField body="consent" type="boolean" required default="true" placeholder="true">
  Explicit end-user consent for this service.

  Example: `true`
</ParamField>

<ParamField body="first_name" type="string" required default="John" placeholder="John">
  Given name to validate.

  Example: `John`
</ParamField>

<ParamField body="last_name" type="string" required default="Doe" placeholder="Doe">
  Family name to validate.

  Example: `Doe`
</ParamField>

<ParamField body="first_partner_name" type="string" required default="Jamie" placeholder="Jamie">
  `first_partner_name` value required by this database service.

  Example: `Jamie`
</ParamField>

<ParamField body="last_partner_name" type="string" required default="Example" placeholder="Example">
  `last_partner_name` value required by this database service.

  Example: `Example`
</ParamField>

<ParamField body="marriage_certificate_number" type="string" required default="SAMPLE-MARRIAGE-12345" placeholder="SAMPLE-MARRIAGE-12345">
  `marriage_certificate_number` value required by this database service.

  Example: `SAMPLE-MARRIAGE-12345`
</ParamField>

<ParamField body="birth_registration_number" type="string" required default="SAMPLE-BIRTH-12345" placeholder="SAMPLE-BIRTH-12345">
  `birth_registration_number` value required by this database service.

  Example: `SAMPLE-BIRTH-12345`
</ParamField>

<ParamField body="birth_registration_state" type="string" required default="Sample State" placeholder="Sample State">
  `birth_registration_state` value required by this database service.

  Example: `Sample State`
</ParamField>

<ParamField body="birth_registration_date" type="string" required default="1990-01-01" placeholder="1990-01-01">
  `birth_registration_date` value required by this database service.

  Example: `1990-01-01`
</ParamField>

<ParamField body="vendor_data" type="string" default="user-1234" placeholder="user-1234">
  Your stable user reference for this person, such as your internal user ID. Didit uses it to link standalone checks to the same end user and reduce duplicate-detection noise.

  Example: `user-1234`
</ParamField>

## Input rules & validation notes

* Send the fields listed above exactly as captured from the user or document.
* Didit validates required fields before calling the database. Requests rejected before source lookup are not charged.

## How to call it

<RequestExample>
  ```bash cURL theme={null}
  curl -X POST "https://verification.didit.me/v3/database-validation/" \
    -H "x-api-key: YOUR_API_KEY" \
    -F "issuing_state=AUS" \
    -F "services=aus_marriage_certificate" \
    -F "vendor_data=user-1234" \
    -F "consent=true" \
    -F "first_name=John" \
    -F "last_name=Doe" \
    -F "first_partner_name=Jamie" \
    -F "last_partner_name=Example" \
    -F "marriage_certificate_number=SAMPLE-MARRIAGE-12345" \
    -F "birth_registration_number=SAMPLE-BIRTH-12345" \
    -F "birth_registration_state=Sample State" \
    -F "birth_registration_date=1990-01-01"
  ```
</RequestExample>

<ResponseExample>
  Every successful call returns HTTP `200`. The **`outcome_code`** field tells you what actually happened — distinguishing, for example, a real biometric mismatch (`BIOMETRIC_NO_MATCH`) from a selfie that could not be read (`BIOMETRIC_IMAGE_UNUSABLE`). The `status` shown is the default feature status; your configured [Partial Match / No Match actions](/core-technology/database-validation/database-validation-warnings) can override it.

  **`MATCH`** — The registry confirmed the identity and every checked field matched.

  ```json 200 OK — MATCH theme={null}
  {
    "request_id": "req_01H…",
    "status": "Approved",
    "issuing_state": "AUS",
    "match_type": "full_match",
    "validations": [
      {
        "outcome_code": "MATCH",
        "service_id": "aus_marriage_certificate",
        "service_name": "Australia - DVS – Marriage Certificate",
        "source_data": {
          "first_name": "John",
          "identification_number": "SAMPLE-ID-12345",
          "last_name": "Doe"
        },
        "validation": {
          "full_name": "full_match",
          "identification_number": "full_match"
        }
      }
    ]
  }
  ```

  **`PARTIAL_MATCH`** — The identification number was found but one or more personal fields (usually name or date of birth) did not fully match.

  ```json 200 OK — PARTIAL_MATCH theme={null}
  {
    "request_id": "req_01H…",
    "status": "In Review",
    "issuing_state": "AUS",
    "match_type": "partial_match",
    "validations": [
      {
        "outcome_code": "PARTIAL_MATCH",
        "service_id": "aus_marriage_certificate",
        "service_name": "Australia - DVS – Marriage Certificate",
        "source_data": {
          "first_name": "John",
          "identification_number": "SAMPLE-ID-12345",
          "last_name": "Doe"
        },
        "validation": {
          "full_name": "no_match",
          "identification_number": "full_match"
        }
      }
    ]
  }
  ```

  **`NO_MATCH`** — The registry returned no match for the submitted data.

  ```json 200 OK — NO_MATCH theme={null}
  {
    "request_id": "req_01H…",
    "status": "Declined",
    "issuing_state": "AUS",
    "match_type": "no_match",
    "validations": [
      {
        "outcome_code": "NO_MATCH",
        "service_id": "aus_marriage_certificate",
        "service_name": "Australia - DVS – Marriage Certificate",
        "source_data": {
          "full_name": "NO_MATCH",
          "identification_number": "NO_MATCH"
        },
        "validation": {
          "full_name": "no_match",
          "identification_number": "no_match"
        }
      }
    ]
  }
  ```
</ResponseExample>

## Returned data

The exact fields surfaced in `source_data` depend on what the registry returns. The generated example for `aus_marriage_certificate` currently documents this normalized shape:

* `first_name`
* `identification_number`
* `last_name`

## Pricing & SLAs

Australia - DVS – Marriage Certificate queries are billed only when Didit receives a conclusive result from the validation source.

* **Per-call price:** \$0.45 USD.
* **Billing:** per successful query. You are not charged when the registry is unreachable, when required fields are missing, or when the request is rejected before reaching the source.
* **Latency:** typical p95 \< 2 s.
* **Availability:** 99.9% per quarter on Didit's side; downstream source availability varies by country and dataset.

## Continue reading

* [Australia Database Validation overview](/api-reference/database-validation/australia)
* [Database Validation overview](/core-technology/database-validation/overview)
* [Outcome Codes](/core-technology/database-validation/database-validation-outcome-codes)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.