| 12 | |
| 13 | // From https://vercel.com/docs/rest-api/endpoints#get-a-project-domain |
| 14 | export interface DomainResponse { |
| 15 | name: string; |
| 16 | apexName: string; |
| 17 | projectId: string; |
| 18 | redirect?: string | null; |
| 19 | redirectStatusCode?: (307 | 301 | 302 | 308) | null; |
| 20 | gitBranch?: string | null; |
| 21 | updatedAt?: number; |
| 22 | createdAt?: number; |
| 23 | /** `true` if the domain is verified for use with the project. If `false` it will not be used as an alias on this project until the challenge in `verification` is completed. */ |
| 24 | verified: boolean; |
| 25 | /** A list of verification challenges, one of which must be completed to verify the domain for use on the project. After the challenge is complete `POST /projects/:idOrName/domains/:domain/verify` to verify the domain. Possible challenges: - If `verification.type = TXT` the `verification.domain` will be checked for a TXT record matching `verification.value`. */ |
| 26 | verification: { |
| 27 | type: string; |
| 28 | domain: string; |
| 29 | value: string; |
| 30 | reason: string; |
| 31 | }[]; |
| 32 | } |
| 33 | export type VercelDomainVerificationResponse = DomainResponse & { |
| 34 | error: { code: string; message: string }; |
| 35 | }; |
nothing calls this directly
no outgoing calls
no test coverage detected