Western Alliance Bancorporation Intrabank Search API

openapi: 3.2.0
info:
  title: Western Alliance Bank Intrabank Transfer … … Intrabank…
  version: v1-v2
  description: 'Initiates an intra-bank transfer between two Western Alliance Bank accounts and searches

    intra-bank transfers as originator or beneficiary.'
  contact:
    name: Western Alliance Bank API Developer Portal
    url: https://developer.westernalliancebank.com/s/
  termsOfService: https://www.westernalliancebancorporation.com/sites/default/files/2025-05/api-services-terms-conditions.pdf
  x-family: Transactional
  x-generated-from: documentation
  x-source: https://developer.westernalliancebank.com/sfsites/c/cms/delivery/media/MC2GPNZ5A6AFBB7FPCQ6YISYCQY4
  x-source-page: https://developer.westernalliancebank.com/s/cms-document/user-guide-wab-intrabank-transfer-api-MC2GPNZ5A6AFBB7FPCQ6YISYCQY4
  x-provenance:
    generated: '2026-09-17'
    method: derived
    source: postman/western-alliance-bancorporation-intrabank-transfer-api-user-guide.pdf
    note: Hand transcription of the provider's user guide; the guide documents endpoints, request/response JSON and an error index but no full schema, so field types are inferred from the sample values only.
servers:
- url: https://api-connect.westernalliancebank.com
  description: Production (the host used in every cURL sample in the guide)
- url: https://api-connect.westernalliancebanktest.com
  description: Client UAT environment (API Services Terms 6(b) - all data must be fake / masked test data)
security:
- bearerToken: []
tags:
- name: Intrabank Search
  description: On-demand lookup of intra-bank transfers; a fallback when the webhook is missed, not a replacement for it.
paths:
  /trnsct-ibt-eapi/api/v2/transactions/intraBankSearch:
    post:
      operationId: searchIntraBankTransfers
      summary: Search intra-bank transfers (originator or beneficiary mode)
      description: 'Searches transfers where the supplied AccountId is the Originator or the Beneficiary.

        Exactly one of ValueDate, PaymentId or PaymentMessageReference is accepted per call,

        together with SystemIdentifier and the account. The query parameter `page` is required.'
      tags:
      - Intrabank Search
      parameters:
      - $ref: '#/components/parameters/XCorrelationId'
      - name: page
        in: query
        required: true
        schema:
          type: integer
        example: 1
        description: Result page number (required; omitting it returns 400).
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/IntraBankSearchRequest'
            examples:
              beneficiary:
                value:
                  SystemIdentifier: ECG
                  AccountId: '1313131313'
                  Type: Beneficiary
                  PaymentId: 09232025124
              originator:
                value:
                  SystemIdentifier: ECG
                  AccountId: '1212121212'
                  Type: Originator
                  PaymentId: 09232025124
      responses:
        '200':
          description: Matching transfers.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/IntraBankSearchResponse'
              example:
                CurrentPage: /transactions/intraBankSearch?page=1
                TransactionCount: 1
                Transactions:
                - TransactionId: '526605645490'
                  SendersReferenceNumber: 09232025124
                  BeneficiaryReference: '250923092149235'
                  StatusMessage: Completed
                  Amount: '124'
                  Currency: USD
                  FundTransferDirection: O
                  FundTransferReleaseDate: '2025-09-23'
                  RemittanceInformation: TestTransaction
                  OriginatorAccountId: '1212121212'
                  OriginatorAddress2: RENO NV 89523
                  OriginatorAddress3: US
                  BeneficiaryAccountId: '1313131313'
                  BeneficiaryName: INTERNAL ACCOUNT
        '400':
          description: Missing required `page` parameter, or more than one of ValueDate / PaymentId / PaymentMessageReference supplied.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorEnvelope'
              examples:
                missingPage:
                  value:
                    errors:
                    - code: 400
                      message: Required query parameter page not specified
                      additionalInfo: Required query parameter page not specified
                multipleParameters:
                  value:
                    errors:
                    - code: 400
                      message: Unavailable
                      additionalInfo: Invalid search parameter. Either ValueDate or PaymentId or PaymentMessageReference will be accepted. Please provide any one of the aforementioned parameter along with SystemIdentifier and OriginatorAccountId.
components:
  schemas:
    ErrorEnvelope:
      type: object
      properties:
        errors:
          type: array
          items:
            type: object
            properties:
              code:
                type: integer
              message:
                type: string
              additionalInfo:
                type: string
    IntraBankSearchResponse:
      type: object
      properties:
        CurrentPage:
          type: string
        TransactionCount:
          type: integer
        Transactions:
          type: array
          items:
            $ref: '#/components/schemas/IntraBankTransaction'
    IntraBankSearchRequest:
      type: object
      required:
      - SystemIdentifier
      - AccountId
      - Type
      properties:
        SystemIdentifier:
          type: string
        AccountId:
          type: string
        Type:
          type: string
          enum:
          - Beneficiary
          - Originator
        ValueDate:
          type: string
          description: yyyy-MM-dd. Mutually exclusive with PaymentId and PaymentMessageReference.
        PaymentId:
          type: string
        PaymentMessageReference:
          type: string
    IntraBankTransaction:
      type: object
      properties:
        TransactionId:
          type: string
          description: Equals the PaymentMessageReference.
        SendersReferenceNumber:
          type: string
          description: Equals the client PaymentId.
        BeneficiaryReference:
          type: string
        StatusMessage:
          type: string
          description: e.g. Completed, Cancelled.
        Amount:
          type: string
        Currency:
          type: string
        FundTransferDirection:
          type: string
        FundTransferReleaseDate:
          type: string
        RemittanceInformation:
          type: string
        FundTransferReasonCode:
          type: string
          description: Present on unsuccessful transfers (e.g. MS01).
        FundTransferReasonDescription:
          type: string
        FundTransferCreditorName:
          type: string
        OriginatorName:
          type: string
        OriginatorAccountId:
          type: string
        OriginatorAddress2:
          type: string
        OriginatorAddress3:
          type: string
        BeneficiaryAccountId:
          type: string
        BeneficiaryName:
          type: string
  parameters:
    XCorrelationId:
      name: X-Correlation-Id
      in: header
      required: true
      schema:
        type: string
        format: uuid
      description: Client-generated GUID used to correlate the request across WAB systems.
  securitySchemes:
    bearerToken:
      type: http
      scheme: bearer
      description: Bearer token from GET /entitlements-get-token-eapi/api/v1/token (Token API); the guide labels it "IBT Token". Tokens are valid for a limited period (API Services Terms 6(c)(iii)).