> ## Documentation Index
> Fetch the complete documentation index at: https://docs.keette.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Resolve Swift Code

> Looks up a SWIFT/BIC (no bank code required) in the global public
registry and returns bank name, country, and address when known.
Same helper the dashboard uses when creating wire beneficiaries.
`found=false` is not an error — the customer can still type details.




## OpenAPI

````yaml /openapi.yaml get /banks/bic/{bic}
openapi: 3.1.0
info:
  title: Keette API
  version: 1.0.0
  description: |
    Public HTTP API for Keette workspaces. One base URL — live vs sandbox is
    selected by your API key (`sk_live_…` / `sk_test_…`).

    Endpoints are added as each implementation phase ships.
  contact:
    name: Keette Support
    email: talk@keette.com
servers:
  - url: https://1178-41-90-137-132.ngrok-free.app/v1
    description: Local tunnel (ngrok → core :8080)
  - url: https://api.keette.com/v1
    description: Production
security:
  - bearerAuth: []
tags:
  - name: Account
    description: Identity for the authenticating API key
  - name: Utilities
    description: |
      Lookup helpers for building beneficiaries and payouts — corridors
      (schemes + routing field keys), bank directory codes, account resolve,
      and SWIFT/BIC lookup.
  - name: Balances
    description: Wallet books
  - name: Beneficiaries
    description: Payout recipients
  - name: Transactions
    description: Unified transaction index
  - name: FX
    description: Indicative rates and firm quotes
  - name: Payouts
    description: Send money to a beneficiary
  - name: Payins
    description: Collect money into your books
  - name: Swaps
    description: FX between your own books
  - name: Webhooks
    description: Durable event log, ping, and webhook delivery helpers
paths:
  /banks/bic/{bic}:
    get:
      tags:
        - Utilities
      summary: Resolve Swift Code
      description: |
        Looks up a SWIFT/BIC (no bank code required) in the global public
        registry and returns bank name, country, and address when known.
        Same helper the dashboard uses when creating wire beneficiaries.
        `found=false` is not an error — the customer can still type details.
      operationId: getBankBic
      parameters:
        - name: bic
          in: path
          required: true
          description: 8 or 11 character SWIFT / BIC (any country).
          schema:
            type: string
            example: NWBKGB2L
      responses:
        '200':
          description: BIC lookup
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/BankBic'
              examples:
                found:
                  value:
                    object: bank_bic
                    bic: NWBKGB2L
                    country: GB
                    found: true
                    bank_name: NATIONAL WESTMINSTER BANK PUBLIC LIMITED COMPANY
                    address:
                      city: LONDON
                      country: GB
        '401':
          $ref: '#/components/responses/Unauthorized'
components:
  schemas:
    BankBic:
      type: object
      properties:
        object:
          type: string
          enum:
            - bank_bic
        bic:
          type: string
        country:
          type: string
        found:
          type: boolean
        bank_name:
          type: string
        branch:
          type: string
        address:
          type: object
          additionalProperties:
            type: string
    Error:
      type: object
      required:
        - error
      properties:
        error:
          type: object
          required:
            - type
            - code
            - message
          properties:
            type:
              type: string
              description: Broad error class for client handling.
              enum:
                - invalid_request
                - authentication_error
                - permission_error
                - rate_limit
                - api_error
            code:
              type: string
              description: Stable machine-readable code (e.g. `parameter_invalid`).
            message:
              type: string
              description: Human-readable explanation safe to show developers.
            param:
              type: string
              description: Request field that failed validation, when applicable.
            doc_url:
              type: string
              format: uri
              description: Optional link to docs for this error.
  responses:
    Unauthorized:
      description: Missing or invalid API key
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
          example:
            error:
              type: authentication_error
              code: invalid_api_key
              message: Invalid API key provided.
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer
      bearerFormat: API key
      description: |
        Secret API key from **Settings → Developers → API keys**.
        Example: `Authorization: Bearer sk_test_…`

````

This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.