--- title: "Submit a DIR's references" method: POST path: "/dir/{dir_id}/references" tags: ["DIR References"] --- # Submit a DIR's references `POST /dir/{dir_id}/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 - `dir_id` string, uuid, required ## Request body - ReferenceSubmissionRequest — Exactly two business references plus one financial reference. The DIR's authorizer email must be verified before this is accepted. - `business_references` ReferenceInput[], required — Exactly two business references. Array order determines each one's slot: the first entry becomes slot 1 and the second becomes slot 2. Those slots are what you pass when updating a single reference later. Each should be a senior contact who can speak to your company's reputation and operations: a C-suite executive (CEO, CFO, CTO, COO), an owner or founder as reflected in your corporate records, or a senior manager, director, or executive at an organization you work with, such as a vendor, partner, or client. - `email` string, email, required — Reference contact email address. Required: the reference is emailed scheduling and dial-in notices. - `full_name` string, required — Full name of the reference contact. - `job_title` string, nullable — Job title of the reference contact. - `organization` string, nullable — Organization the reference contact belongs to. - `phone_e164` string, required — Reference phone number in E.164 format, e.g. +14155550123. - `relationship_to_registrant` string, nullable — How the reference contact is related to the registering business. - `timezone` string, required — IANA timezone id for the reference (e.g. America/New_York). Required: calls are only placed within the reference's local 8am-9pm window. - `financial_reference` ReferenceInput, required — One reference supplied at submit. The reference type is implied by the field that carries it (business_references vs financial_reference). - `email` string, email, required — Reference contact email address. Required: the reference is emailed scheduling and dial-in notices. - `full_name` string, required — Full name of the reference contact. - `job_title` string, nullable — Job title of the reference contact. - `organization` string, nullable — Organization the reference contact belongs to. - `phone_e164` string, required — Reference phone number in E.164 format, e.g. +14155550123. - `relationship_to_registrant` string, nullable — How the reference contact is related to the registering business. - `timezone` string, required — IANA timezone id for the reference (e.g. America/New_York). Required: calls are only placed within the reference's local 8am-9pm window. ## Response `200` Resubmit accepted. Identical values were confirmed unchanged, or changed values replaced those references. - ReferenceList - `data` Reference[], required - `email` string, email, nullable — Reference contact email address. - `full_name` string, required — Full name of the reference contact. - `job_title` string, nullable — Job title of the reference contact. - `organization` string, nullable — Organization the reference contact belongs to. - `phone_e164` string, required — Reference phone number in E.164 format. - `record_type` 'dir_reference', required — Always `dir_reference`. - `ref_type` 'business' | 'financial', required — Whether this is a business reference or the financial reference. - `relationship_to_registrant` string, nullable — How the reference contact is related to the registering business. - `slot` integer, required — Position within the reference type, counting from 1. Business references occupy slots 1 and 2, in the order they were sent in the `business_references` array; the financial reference occupies slot 1. Use this value together with `ref_type` to address the reference when updating it. - `timezone` string, required — IANA timezone id for the reference. Calls are only placed within the reference's local 8am-9pm window. ## Other responses - `201` — The stored references. - `400` — An error occurred. The response carries the standard Telnyx error envelope. - `404` — An error occurred. The response carries the standard Telnyx error envelope. - `409` — An error occurred. The response carries the standard Telnyx error envelope. --- [API](https://skmtc.net/team-telnyx/apis/telnyx-api-2.md) · [All operations](https://skmtc.net/team-telnyx/apis/telnyx-api-2/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/team-telnyx/telnyx-api-2/revisions/ec31f78cf002/schema)