> ## Documentation Index > Fetch the complete documentation index at: https://www.dynamic.xyz/docs/llms.txt > Use this file to discover all available pages before exploring further. # Get the organization's prior KYB submission and any flagged reasons > Returns the business data submitted with the org's basic-tier verification session (vendor-shaped, mapped to the same shape submitKybVerification accepts) plus any vendor-reported reasons the last decision wasn't APPROVED. Used to prefill a failed/reopened wizard so the customer only fixes the flagged fields. Not gated on the stored row's status — submitKybVerification's own duplicate-application guard already restricts resubmission to fixable states. ## OpenAPI ````yaml https://app.dynamic.xyz/api-docs/public-api.yaml get /organizations/{organizationId}/kyb/submission openapi: 3.0.1 info: title: Dashboard API description: Dashboard API documentation version: 1.0.0 servers: - url: https://app.dynamicauth.com/api/v0 - url: https://app.dynamic.xyz/api/v0 - url: http://localhost:3333/api/v0 security: [] tags: - name: Analytics description: Query usage analytics and event counts for your environment. - name: SDK description: SDK-facing endpoints consumed by embedded Dynamic clients. - name: Server description: Server-side SDK endpoints authenticated by environment API tokens. - name: Organizations description: >- Manage organizations — the top-level container for all environments and projects. - name: Projects description: Manage projects that group related environments under an organization. - name: Environments description: >- Manage environments (live and sandbox) where your authentication configuration lives. - name: Users description: List, search, and manage authenticated users within an environment. - name: Invites description: >- Manage invitation links that grant specific external users access to your environment. - name: Tokens description: >- Create and manage API tokens used to authenticate requests to the Dynamic API. - name: Origins description: >- Configure allowed origins (CORS) for SDK and API access to your environment. - name: Allowlists description: >- Manage allowlists to control which wallet addresses or email addresses can access your environment. - name: Wallets description: View and manage wallets linked to users in your environment. - name: Members description: Manage team members and their roles within an organization. - name: Sessions description: View and revoke active user sessions within an environment. - name: Settings description: Read and update environment-level configuration settings. - name: Exchanges description: >- Configure exchange integrations (Coinbase, Binance, etc.) for fiat on-ramp within your environment. - name: Yield description: List yield vaults registered for your environment. - name: Providers description: >- List, enable, disable, and configure authentication providers (OAuth, email, wallet, SMS, etc.) for your environment. - name: Captcha description: >- Configure captcha verification (provider, site key, secret key) for your environment. - name: Gates description: >- Define access gates that restrict environment entry to users who meet specific criteria. - name: Chains description: >- Manage the blockchain networks available for wallet connection in your environment. - name: Exports description: Export user and wallet data from your environment as downloadable files. - name: Events description: Browse the event log of actions performed within your environment. - name: Webhooks description: >- Create and manage webhooks to receive real-time events (user.created, wallet.linked, etc.) at your endpoint. - name: Custom Fields description: >- Define and manage custom metadata fields collected from users at sign-up or login. - name: MfaSettings description: >- Configure multi-factor authentication (MFA) policies for your organization. - name: Mfa description: Manage MFA enrollment and verification for individual users. - name: CustomHostnames description: >- Configure custom hostnames for white-labeling the Dynamic authentication experience. - name: TestAccount description: >- Manage test accounts used for automated testing and QA within an environment. - name: NameServices description: >- Configure name service integrations (ENS, Unstoppable Domains, etc.) for human-readable wallet addresses. - name: GlobalWallets description: >- Manage global wallets shared across multiple environments in an organization. - name: GlobalWalletConnections description: Configure which environments can access and use global wallets. - name: GlobalWalletAccessControl description: Control which users and roles can access and operate global wallets. - name: UserApiTokens description: >- Create and manage user-scoped API tokens for programmatic access on behalf of a user. - name: Waas description: Wallet-as-a-Service endpoints for creating and managing embedded wallets. - name: WalletConnect description: Configure WalletConnect integration settings for your environment. - name: Checkout description: >- Accept crypto payments and deposits from any wallet. Settle in any token you choose. - name: Flow description: >- Accept crypto payments, deposits, and withdrawals. Amount and destination are fixed server-side at create; the post-create lifecycle is driven with a capability session token. - name: FlowAnalytics description: >- Query aggregated analytics and paginated transaction lists for the Flow product. - name: Gasless description: >- Query billing summaries and paginated transaction lists for sponsored (gasless) transactions. - name: Custom Networks description: >- Add and manage custom EVM-compatible networks beyond the built-in chain list. - name: Chainalysis description: >- Configure Chainalysis integration for blockchain address screening and risk assessment. - name: Visits description: Track and query user visit activity within your environment. - name: ExternalJwt description: >- Configure external JWT providers so existing auth tokens can be used with Dynamic. - name: SDK Views description: >- Manage SDK view configurations that customize the appearance of Dynamic modals and flows. - name: DeeplinkUrls description: Configure deep link URLs for mobile app integration with the Dynamic SDK. - name: OrganizationSettings description: >- Read and update organization-level settings such as approval workflow configuration. - name: AdminActions description: >- Manage admin action requests that require approval from another administrator. - name: ClientGrant description: | OAuth 2.0 Device Authorization Grant flow (RFC 8628) used by first-party Dynamic clients (CLI, MCP server, demo apps, IDE plugins) to obtain a revocable, 30-day client JWT without ever seeing the user's dashboard session token. - name: AuthorizedClients description: | Manage first-party clients (CLI / MCP / demo / IDE plugins) authorized to act as a dashboard user. Surfaced under Profile → Authorized Clients. - name: Kyb description: >- Verify a business's identity via AI Prise passthrough and check KYB tier status. paths: /organizations/{organizationId}/kyb/submission: get: tags: - Kyb summary: Get the organization's prior KYB submission and any flagged reasons description: | Returns the business data submitted with the org's basic-tier verification session (vendor-shaped, mapped to the same shape submitKybVerification accepts) plus any vendor-reported reasons the last decision wasn't APPROVED. Used to prefill a failed/reopened wizard so the customer only fixes the flagged fields. Not gated on the stored row's status — submitKybVerification's own duplicate-application guard already restricts resubmission to fixable states. operationId: getKybSubmission parameters: - $ref: '#/components/parameters/organizationId' responses: '200': description: The organization's prior KYB submission. content: application/json: schema: $ref: '#/components/schemas/KybSubmissionResponse' '401': $ref: '#/components/responses/Unauthorized' '403': $ref: '#/components/responses/Forbidden' '404': $ref: '#/components/responses/NotFound' '429': $ref: '#/components/responses/TooManyRequests' '502': $ref: '#/components/responses/BadGateway' security: - bearerAuth: [] components: parameters: organizationId: in: path name: organizationId required: true description: ID of organization schema: $ref: '#/components/schemas/uuid' schemas: KybSubmissionResponse: type: object required: - businessData - statusReasons - verificationResult properties: businessData: $ref: '#/components/schemas/KybSubmissionBusinessData' statusReasons: type: array items: $ref: '#/components/schemas/KybStatusReason' vendorQuestions: type: array description: > Empty for most profiles — only populated when a reviewer has configured a business question group on the AI Prise template. items: $ref: '#/components/schemas/KybVendorQuestion' verificationResult: $ref: '#/components/schemas/KybVerificationResultEnum' uuid: type: string pattern: ^[0-9a-f]{8}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{12}$ minLength: 36 maxLength: 36 example: 95b11417-f18f-457f-8804-68e361f9164f KybSubmissionBusinessData: type: object description: >- Same shape KybVerifyRequest's businessData accepts — lets the wizard feed a prior submission straight back into a resubmission. properties: name: type: string countryCode: type: string stateCode: type: string businessEntityId: type: string entityType: type: string description: >- Never populated today — AI Prise's get_business_data_from_request response has no field to read the SOLE_PROPRIETORSHIP flag back from. Kept for symmetry with KybVerifyRequest. enum: - SOLE_PROPRIETORSHIP emailAddresses: type: array items: type: string formationDate: type: string phoneNumbers: type: array items: type: string taxIdentificationNumber: type: string website: type: string addresses: type: array items: $ref: '#/components/schemas/KybSubmissionAddress' KybStatusReason: type: object required: - code - message properties: code: type: string message: type: string description: >- Vendor-authored text describing what needs correction; shown verbatim to the customer. KybVendorQuestion: type: object description: > One answered question from a question group a reviewer configured on the AI Prise template. Read-only: no AI Prise write endpoint accepts `questions_response`, so these are never submitted by us — they are captured in AI Prise's own hosted flow and surfaced here for reconciliation. required: - questionId - question - answer properties: questionId: type: string description: Vendor question key (Q01, Q02, ...). question: type: string description: Vendor-authored question text; shown verbatim to the customer. answer: type: string description: The recorded answer. Empty string when the question is unanswered. KybVerificationResultEnum: type: string enum: - APPROVED - DECLINED - DRAFT - REVIEW - PENDING - REOPENED - UNKNOWN Unauthorized: type: object properties: error: description: Human-readable error message describing the authentication failure type: string example: No jwt provided! Forbidden: type: object properties: error: description: Human-readable error message type: string example: Access Forbidden NotFound: type: object required: - error - code properties: error: description: Human-readable error message type: string example: Not Found code: description: Machine-readable error code type: string example: not_found TooManyRequests: type: object properties: error: description: Human-readable error message indicating rate limit exceeded type: string example: Too Many Requests BadGateway: type: object properties: error: description: Human-readable error message type: string example: Error from Snowflake service required: - error KybSubmissionAddress: type: object properties: addressStreet1: type: string addressStreet2: type: string nullable: true addressCity: type: string addressState: type: string addressZipCode: type: string addressCountry: type: string responses: Unauthorized: description: Unauthorized content: application/json: schema: $ref: '#/components/schemas/Unauthorized' Forbidden: description: Forbidden content: application/json: schema: $ref: '#/components/schemas/Forbidden' NotFound: description: Not Found content: application/json: schema: $ref: '#/components/schemas/NotFound' TooManyRequests: description: Too Many Requests content: application/json: schema: $ref: '#/components/schemas/TooManyRequests' BadGateway: description: Bad Gateway content: application/json: schema: $ref: '#/components/schemas/BadGateway' securitySchemes: bearerAuth: type: http scheme: bearer bearerFormat: JWT ````