Submit a DIR's references
Submit the two business references and one financial reference for a DIR.
The DIR's authorizer email must be verified first (see the email-verification endpoint). Until it is, this returns 409 and no references are stored.
The request body carries exactly two business references plus one financial reference. The first submission stores them and returns 201. Resubmitting returns 200: identical values are simply confirmed and nothing is written, while changed values replace those references.
Replacing a reference is allowed only while the DIR itself is still editable, the same window in which a single reference may be updated; once the DIR has been submitted for vetting this returns 400. A replaced reference's pending verification call is cancelled and its dial-in code stops working, and the replacement contact is emailed fresh scheduling details. References whose details did not change keep their existing call, code, and the notice already sent to them.
The response always echoes the stored references in the same shape as the GET.
Who qualifies: the two business references confirm the company's reputation and operations. Each should be a senior contact at an organization the business works with, such as a vendor, partner, or client: a C-suite executive (CEO, CFO, CTO, COO), an owner or founder as reflected in the company's corporate records, or a senior manager, director, or executive. The financial reference confirms the company pays its bills and should be a licensed certified public accountant (CPA) the company uses, a contact at a bank or financial institution that has a relationship with the company, or a reasonable alternative banking or financial reference.
Path parameters
The DIR id. Lowercase UUID.
Request body
Example request
{
"business_references": [
{
"email": "dana.reyes@example.com",
"full_name": "Dana Reyes",
"job_title": "VP of Operations",
"organization": "Acme Logistics",
"phone_e164": "+14155550123",
"relationship_to_registrant": "Supplier",
"timezone": "America/New_York"
}
],
"financial_reference": {
"email": "dana.reyes@example.com",
"full_name": "Dana Reyes",
"job_title": "VP of Operations",
"organization": "Acme Logistics",
"phone_e164": "+14155550123",
"relationship_to_registrant": "Supplier",
"timezone": "America/New_York"
}
}Response
Resubmit accepted. Identical values were confirmed unchanged, or changed values replaced those references.
Example response
{
"data": [
{
"email": "dana.reyes@example.com",
"full_name": "Dana Reyes",
"job_title": "VP of Operations",
"organization": "Acme Logistics",
"phone_e164": "+14155550123",
"record_type": "dir_reference",
"ref_type": "business",
"relationship_to_registrant": "Supplier",
"slot": 1,
"timezone": "America/New_York"
}
]
}Changes
Changed in 2 of the 61 revisions of this API.372
- ▲
added
ReferenceInputto thefinancial_referencerequest propertyallOflistrequest-property-all-of-added
- ▲
the
financial_referencerequest property type/format changed fromobject/to/request-property-type-changed
- ●
removed the request property
financial_reference/emailrequest-property-removed
- ●
removed the request property
financial_reference/full_namerequest-property-removed
- ●
removed the request property
financial_reference/job_titlerequest-property-removed
- ●
removed the request property
financial_reference/organizationrequest-property-removed
- ●
removed the request property
financial_reference/phone_e164request-property-removed
- ●
removed the request property
financial_reference/relationship_to_registrantrequest-property-removed
- ●
removed the request property
financial_reference/timezonerequest-property-removed
- ▲
- ▲
the
data/items/slotresponse property's max was increased from1.00to2.00for the response status201response-property-max-increased
- ○
added the non-success response with the status
400response-non-success-status-added
- ○
added the success response with the status
200response-success-status-added
- ▲