Skip to main content
POST
Create a public person

Authorizations

Authorization
string
header
required

Send the API key as Authorization: Bearer <api_key>.

Body

application/json

Requires person name and canonical contact name, phone and email. For age below 18, contact_person_relationship and is_guardian_verified:true are required. The API key supplies source. Unknown fields are rejected.

first_name
string
required

Trimmed and normalized person first name.

Minimum string length: 2
last_name
string
required

Trimmed and normalized person last name.

Minimum string length: 2
contact_person_first_name
string
required
Minimum string length: 2
contact_person_phone
string
required

One valid phone number; accepted national or international input is stored as E.164.

Minimum string length: 1
contact_person_email
string<email>
required
document_type
enum<string> | null
Available options:
cedula,
passport,
birth_certificate,
other
document_id
string | null

Document identifier; blank text is normalized to null.

birth_date

YYYY-MM-DD; surrounding whitespace is trimmed and blank text is normalized to null.

age
integer | null
Required range: 0 <= x <= 120
gender
enum<string> | null
Available options:
female,
male,
other
location
string | null
Minimum string length: 1
description
string | null
Minimum string length: 1
shelter
enum<string> | null
Available options:
campo_de_golf_caribe,
centro_acopio_caraballeda,
polideportivo_la_guaira
shelter_status
enum<string> | null
Available options:
present,
departed
source_id
string | null
Minimum string length: 1
source_notes
string | null
Minimum string length: 1
contact_person_last_name
string | null
Minimum string length: 1
contact_person_relationship
enum<string> | null
Available options:
mother,
father,
sibling,
grandparent,
aunt_uncle,
cousin,
friend,
legal_guardian
is_guardian_verified
boolean

Must be true when age is supplied and below 18.

Response

Created person.

data
object
required

Minimized default person response. Child records and public contact fields are protected by default; sensitive access requires a separately approved persons:sensitive:read permission. With that permission, person responses may include the full national ID, precise details, reporter contact fields, finder phone, hospital data, sources, and community-information sender phones.