Telstra · Schema

KYC_MatchRequestBody

Payload to validate the customer data.

TelecommunicationsMobileMessagingSMSMMSNetworksAustraliaVerification

Properties

Name Type Description
phoneNumber string A public identifier addressing a telephone subscription. In mobile networks it corresponds to the MSISDN (Mobile Station International Subscriber Directory Number). In order to be globally unique it h
idDocument string **Telstra does not match against this field and the match result will return not_available.** Id number associated to the official identity document in the country. It may contain alphanumeric charact
name string Complete name of the customer, composed of first/given name and last/family/sur- name. Middle name should be omitted.
givenName string First/given name or compound first/given name of the customer.
familyName string Last name, family name, or surname of the customer.
nameKanaHankaku string **Telstra does not match against this field and the match result will return not_available.** Complete name of the customer in Hankaku-Kana format (reading of name) for Japan.
nameKanaZenkaku string **Telstra does not match against this field and the match result will return not_available.** Complete name of the customer in Zenkaku-Kana format (reading of name) for Japan.
middleNames string **Telstra does not match against this field and the match result will return not_available.** Middle name/s of the customer.
familyNameAtBirth string **Telstra does not match against this field and the match result will return not_available.** Last/family/sur- name at birth of the customer.
address string Complete address of the customer. Constructed in the format **houseNumberExtension (excluding type, eg. Unit) + streetNumber + streetName (excluding street type) + locality + region + postalCode**, wi
streetName string Name of the street of the customer's address. It should not include the type of the street.
streetNumber string The street number of the customer's address. Number identifying a specific property on the 'streetName'.
postalCode string Zip code or postal code
region string Region/prefecture of the customer's address
locality string Locality of the customer's address
country string Country of the customer's address. Format ISO 3166-1 alpha-2
houseNumberExtension string Specific identifier of the house needed depending on the property type. For example, number of apartment in an apartment building. This should not include the type (eg. Unit, Apartment, etc).
birthdate string The birthdate of the customer, in ISO 8601 calendar date format (YYYY-MM-DD).
email string Email address of the customer in the RFC specified format (local-part@domain).
gender string **Telstra does not match against this field and the match result will return not_available.** Gender of the customer (Male/Female/Other).
View JSON Schema on GitHub

JSON Schema

telstra-kyc-match-request-body-schema.json Raw ↑
{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "$id": "https://raw.githubusercontent.com/api-evangelist/telstra/main/json-schema/telstra-kyc-match-request-body-schema.json",
  "title": "KYC_MatchRequestBody",
  "description": "Payload to validate the customer data.",
  "x-generated": "2026-10-20",
  "x-method": "derived",
  "x-generator": "derive-json-schema.py",
  "x-source": "openapi/telstra-kyc-match-api-openapi.yml#/components/schemas/KYC_MatchRequestBody",
  "type": "object",
  "properties": {
    "phoneNumber": {
      "type": "string",
      "description": "A public identifier addressing a telephone subscription. In mobile networks it corresponds to the MSISDN (Mobile Station International Subscriber Directory Number). In order to be globally unique it has to be formatted in international format, according to E.164 standard, prefixed with '+'."
    },
    "idDocument": {
      "type": "string",
      "description": "**Telstra does not match against this field and the match result will return not_available.** Id number associated to the official identity document in the country. It may contain alphanumeric characters."
    },
    "name": {
      "type": "string",
      "description": "Complete name of the customer, composed of first/given name and last/family/sur- name. Middle name should be omitted."
    },
    "givenName": {
      "type": "string",
      "description": "First/given name or compound first/given name of the customer."
    },
    "familyName": {
      "type": "string",
      "description": "Last name, family name, or surname of the customer."
    },
    "nameKanaHankaku": {
      "type": "string",
      "description": "**Telstra does not match against this field and the match result will return not_available.** Complete name of the customer in Hankaku-Kana format (reading of name) for Japan."
    },
    "nameKanaZenkaku": {
      "type": "string",
      "description": "**Telstra does not match against this field and the match result will return not_available.** Complete name of the customer in Zenkaku-Kana format (reading of name) for Japan."
    },
    "middleNames": {
      "type": "string",
      "description": "**Telstra does not match against this field and the match result will return not_available.** Middle name/s of the customer."
    },
    "familyNameAtBirth": {
      "type": "string",
      "description": "**Telstra does not match against this field and the match result will return not_available.** Last/family/sur- name at birth of the customer."
    },
    "address": {
      "type": "string",
      "description": "Complete address of the customer. Constructed in the format **houseNumberExtension (excluding type, eg. Unit) + streetNumber + streetName (excluding street type) + locality + region + postalCode**, with a single whitespace delimiter between each address element."
    },
    "streetName": {
      "type": "string",
      "description": "Name of the street of the customer's address. It should not include the type of the street."
    },
    "streetNumber": {
      "type": "string",
      "description": "The street number of the customer's address.  Number identifying a specific property on the 'streetName'."
    },
    "postalCode": {
      "type": "string",
      "description": "Zip code or postal code"
    },
    "region": {
      "type": "string",
      "description": "Region/prefecture of the customer's address"
    },
    "locality": {
      "type": "string",
      "description": "Locality of the customer's address"
    },
    "country": {
      "type": "string",
      "description": "Country of the customer's address. Format ISO 3166-1 alpha-2"
    },
    "houseNumberExtension": {
      "type": "string",
      "description": "Specific identifier of the house needed depending on the property type. For example, number of apartment in an apartment building. This should not include the type (eg. Unit, Apartment, etc)."
    },
    "birthdate": {
      "type": "string",
      "description": "The birthdate of the customer, in ISO 8601 calendar date format (YYYY-MM-DD)."
    },
    "email": {
      "type": "string",
      "description": "Email address of the customer in the RFC specified format (local-part@domain)."
    },
    "gender": {
      "type": "string",
      "description": "**Telstra does not match against this field and the match result will return not_available.** Gender of the customer (Male/Female/Other).",
      "enum": [
        "MALE",
        "FEMALE",
        "OTHER"
      ]
    }
  }
}

Work with this as data

Every JSON Schema here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for schemas

4 MCP tools reach this
  • find_json_schemasBrowse and filter every JSON Schema in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This JSON Schema
curl "https://apis.io/api/v1/json-schemas/telstra-kyc-match-request-body"
All schemas
curl "https://apis.io/api/v1/json-schemas?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.