Create Customer

Bridge page for reviewed identity-customer creation and compatibility customer overlays

POST /api/v1/identity/customers

Create Customer

cURL

curl --request POST \
  --url https://api.usezentra.com/api/v1/identity/customers \
  --header 'Authorization: Bearer <token>'

import requests

url = "https://api.usezentra.com/api/v1/identity/customers"

headers = {"Authorization": "Bearer <token>"}

response = requests.post(url, headers=headers)

print(response.text)

const options = {method: 'POST', headers: {Authorization: 'Bearer <token>'}};

fetch('https://api.usezentra.com/api/v1/identity/customers', options)
  .then(res => res.json())
  .then(res => console.log(res))
  .catch(err => console.error(err));

<?php

$curl = curl_init();

curl_setopt_array($curl, [
  CURLOPT_URL => "https://api.usezentra.com/api/v1/identity/customers",
  CURLOPT_RETURNTRANSFER => true,
  CURLOPT_ENCODING => "",
  CURLOPT_MAXREDIRS => 10,
  CURLOPT_TIMEOUT => 30,
  CURLOPT_HTTP_VERSION => CURL_HTTP_VERSION_1_1,
  CURLOPT_CUSTOMREQUEST => "POST",
  CURLOPT_HTTPHEADER => [
    "Authorization: Bearer <token>"
  ],
]);

$response = curl_exec($curl);
$err = curl_error($curl);

curl_close($curl);

if ($err) {
  echo "cURL Error #:" . $err;
} else {
  echo $response;
}

package main

import (
	"fmt"
	"net/http"
	"io"
)

func main() {

	url := "https://api.usezentra.com/api/v1/identity/customers"

	req, _ := http.NewRequest("POST", url, nil)

	req.Header.Add("Authorization", "Bearer <token>")

	res, _ := http.DefaultClient.Do(req)

	defer res.Body.Close()
	body, _ := io.ReadAll(res.Body)

	fmt.Println(string(body))

}

HttpResponse<String> response = Unirest.post("https://api.usezentra.com/api/v1/identity/customers")
  .header("Authorization", "Bearer <token>")
  .asString();

require 'uri'
require 'net/http'

url = URI("https://api.usezentra.com/api/v1/identity/customers")

http = Net::HTTP.new(url.host, url.port)
http.use_ssl = true

request = Net::HTTP::Post.new(url)
request["Authorization"] = 'Bearer <token>'

response = http.request(request)
puts response.read_body

For new integrations on the reviewed public gateway, create customer records through the tenant-gated identity surface:

POST /api/v1/identity/customers

The older customer-overlay create route is not part of the reviewed public API contract. Use it only if Zentra has issued your tenant a compatibility-layer customer contract.

Reviewed Public Status

• POST /api/v1/identity/customers is the reviewed create route when the identity-customer surface is enabled for your tenant
• the exact payload and downstream KYC behavior remain tenant-gated
• you should not assume every environment exposes the same identity provider mix or response details

Common Request Inputs

The reviewed OpenAPI models this route with a generic request envelope, so the exact accepted fields depend on your enabled identity program. Common fields usually include:

• stable customer reference or external identifier
• legal name fields
• contact fields such as email or phone
• country or locale information when required
• metadata for your own reconciliation

Integration Guidance

• keep retries idempotent with a stable business identifier
• avoid storing more PII than you need in your own systems
• treat identity customer creation as a tenant-gated onboarding step, not a universal primitive for every product flow

Example Request

curl -X POST https://api.usezentra.com/api/v1/identity/customers \
  -H "Authorization: Bearer YOUR_SECRET_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "external_reference": "cust_123",
    "first_name": "John",
    "last_name": "Doe",
    "email": "[e-mail]",
    "phone": "[phone]",
    "metadata": {
      "source": "mobile_app"
    }
  }'

Confirm the exact identity-customer schema enabled for your tenant before shipping to live. The goal of this page is to point new integrations at the right reviewed route family, not to freeze a one-size-fits-all payload.

Next Steps

Identity Overview

Review the tenant-gated identity surface

Verify BVN

Continue into the reviewed verification flow

Virtual Accounts

Create a receiving account after onboarding

Support

Confirm your enabled identity-customer contract