Infobip · Schema

CamaraKycMatchRequestDto

Camara Know Your Customer Match request object

TelecommunicationsCroatiaCPaaSMessagingSMSVoiceRCSWhatsAppEmailNetwork APIsCAMARAOpen GatewayIdentity VerificationSIM SwapNumber VerificationOmnichannelAggregatorCustomer EngagementCommunications

Properties

Name Type Description
phoneNumber string Mobile phone number (MSISDN) to verify. The number must be in international format.
idDocument string Id number associated to the official identity document in the country.
name string Complete name of the customer, usually composed of first/given name and last/family/sur-name in a country.
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 Complete name of the customer in Hankaku-Kana format (reading of name) for Japan.
nameKanaZenkaku string Complete name of the customer in Zenkaku-Kana format (reading of name) for Japan.
middleNames string Middle name/s of the customer.
familyNameAtBirth string Last/family/sur-name at birth of the customer.
address string Complete address of the customer.
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.
birthdate string The birthdate of the customer, in RFC 3339 / 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 Gender of the customer.
View JSON Schema on GitHub

JSON Schema

infobip-c4fb96364cd87b1d1d15720880c5153ef26f58342e4ec03b9d5896f2251f17ae-camara-kyc-match-request-dto-schema.json Raw ↑ 
{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "$id": "https://raw.githubusercontent.com/api-evangelist/infobip/main/json-schema/infobip-c4fb96364cd87b1d1d15720880c5153ef26f58342e4ec03b9d5896f2251f17ae-camara-kyc-match-request-dto-schema.json",
  "title": "CamaraKycMatchRequestDto",
  "description": "Camara Know Your Customer Match request object",
  "x-generated": "2026-10-04",
  "x-method": "derived",
  "x-generator": "derive-json-schema.py",
  "x-source": "openapi/infobip-connectivity-api-openapi.yml#/components/schemas/c4fb96364cd87b1d1d15720880c5153ef26f58342e4ec03b9d5896f2251f17ae.CamaraKycMatchRequestDto",
  "type": "object",
  "properties": {
    "phoneNumber": {
      "type": "string",
      "description": "Mobile phone number (MSISDN) to verify. The number must be in international format."
    },
    "idDocument": {
      "type": "string",
      "description": "Id number associated to the official identity document in the country."
    },
    "name": {
      "type": "string",
      "description": "Complete name of the customer, usually composed of first/given name and last/family/sur-name in a country."
    },
    "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": "Complete name of the customer in Hankaku-Kana format (reading of name) for Japan."
    },
    "nameKanaZenkaku": {
      "type": "string",
      "description": "Complete name of the customer in Zenkaku-Kana format (reading of name) for Japan."
    },
    "middleNames": {
      "type": "string",
      "description": "Middle name/s of the customer."
    },
    "familyNameAtBirth": {
      "type": "string",
      "description": "Last/family/sur-name at birth of the customer."
    },
    "address": {
      "type": "string",
      "description": "Complete address of the customer."
    },
    "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."
    },
    "birthdate": {
      "type": "string",
      "format": "date",
      "description": "The birthdate of the customer, in RFC 3339 / ISO 8601 calendar date format (YYYY-MM-DD)."
    },
    "email": {
      "type": "string",
      "format": "email",
      "description": "Email address of the customer in the RFC specified format (local-part@domain)."
    },
    "gender": {
      "type": "string",
      "description": "Gender of the customer.",
      "enum": [
        "MALE",
        "FEMALE",
        "OTHER"
      ]
    }
  },
  "required": [
    "phoneNumber"
  ]
}

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/infobip-c4fb96364cd87b1d1d15720880c5153ef26f58342e4ec03b9d5896f2251f17ae-camara-kyc-match-request-dto"
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.

GitHub Google LinkedIn

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