find_apisBrowse and filter every API in the catalog.
get_api_artifactsOne API's artifacts, grouped by type.
get_openapiThe primary OpenAPI for this API.
find_similar_apisAPIs that look like this one.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This API

curl "https://apis.io/api/v1/apis/hihealth:hihealth-mobile-wallet-tokenization-api"

All apis

curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

openapi: 3.2.0
info:
  contact:
    name: API Support
    email: support@getpliant.com
    url: https://www.getpliant.com
  title: Pliant Partner Mobile Wallet Tokenization API
  description: Pliant Partner API
  version: 2.1.0
  license:
    name: MIT
    url: https://opensource.org/license/MIT
servers:
- url: https://partner-api.getpliant.com/api
  description: Pliant Production Server
- url: https://sandbox.partner-api.getpliant.com/api
  description: Pliant Sandbox Server
- url: https://pci-api.getpliant.com
  description: PCI Vault Production Server
- url: https://pci-sandbox.partner-api.getpliant.com
  description: PCI Vault Sandbox Server
security:
- bearerAuth: []
tags:
- name: Mobile Wallet Tokenization
  description: This tag is for operations related to mobile wallet tokenization
paths:
  /mobile-wallet-tokenizations:
    get:
      summary: List Mobile Wallet Tokenizations
      description: Returns all mobile wallet tokenizations for mobile wallets for the given card or organization. At least one of both is needed, the input parameters are treated as an OR condition.
      tags:
      - Mobile Wallet Tokenization
      operationId: get-mobile-wallet-tokenization
      parameters:
      - name: organizationId
        in: query
        description: The unique identifier of the organization.
        schema:
          type: string
          format: uuid
        required: false
      - name: cardId
        in: query
        description: The unique identifier of the card.
        schema:
          type: string
          format: uuid
        required: false
      responses:
        '200':
          description: Ok
          content:
            application/json:
              schema:
                type: object
                properties:
                  data:
                    type: array
                    items:
                      $ref: '#/components/schemas/TokenizationDetails'
        '400':
          $ref: '#/components/responses/400'
        '401':
          $ref: '#/components/responses/401'
        '403':
          $ref: '#/components/responses/403'
        '429':
          $ref: '#/components/responses/429'
        '500':
          $ref: '#/components/responses/500'
  /mobile-wallet-tokenizations/subscription:
    post:
      summary: 'Callback: Add/Update'
      description: Subscribe to callbacks for this entity or change an existing callback.
      tags:
      - Mobile Wallet Tokenization
      operationId: create-mobile-wallet-tokenization-subscription
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              properties:
                callbackUrl:
                  type: string
                  format: uri
                  example: https://myserver.com/send/callback/here
                  description: The URL to send the callback to. Must be a valid and reachable URL. We do some basic validation to ensure the URL is syntactically correct and reachable for Pliant. Only HTTPS URLs are supported.
                eventTypes:
                  type: array
                  description: The event types to subscribe to.
                  items:
                    type: string
                    enum:
                    - CARD_TOKENIZATION_OTP
                    - CARD_TOKENIZATION_STATUS_CHANGE
              required:
              - callbackUrl
              - eventTypes
      responses:
        '201':
          description: Created
        '401':
          description: Unauthorized
        '403':
          description: Forbidden
        '500':
          description: Internal Server Error
      callbacks:
        cardTokenizationOTP:
          '{$request.body#/callbackUrl}':
            post:
              parameters:
              - in: header
                name: X-Organization-Id
                schema:
                  type: string
                  format: uuid
                  description: 'Referencing the organization this callback was sent for. See [guides](/docs/callbacks) for more details. Example value: `54e6e7e7-0c23-4a54-bccb-2d3ff2fd02df`.'
              - in: header
                name: X-Partner-Organization-Id
                schema:
                  type: string
                  description: 'Filled, if the value `partnerOrganizationId` is [set](/reference/update-organization) by the partner on the organization itself. Referencing the organization identifier of the partner. Example value: `abc123`.'
              - in: header
                name: X-Payment-Program-Id
                schema:
                  type: string
                  format: uuid
                  description: 'Referencing the payment program this callback was sent for. See [guides](/docs/callbacks) for more details. Example value: `54e6e7e7-0c23-4a54-bccb-2d3ff2fd02df`.'
              - in: header
                name: X-Callback-Id
                schema:
                  type: string
                  format: uuid
                  description: 'A unique identifier for this callback. Can be used to deduplicate callbacks to achieve idempotent behavior. See [guides](/docs/callbacks) for more details. Example value: `12a03093-eaad-4ae5-9d8d-42e7f6f8b7c6`.'
              - in: header
                name: X-Callback-Created-At
                schema:
                  type: string
                  format: date-time
                  description: 'The date and time when the callback was created. Can be used to reorder callbacks. See [guides](/docs/callbacks) for more details. Example value: `2024-03-15T15:55:58.623375258Z`.'
              requestBody:
                $ref: '#/components/requestBodies/TokenizationOTPCallback'
              responses:
                '200':
                  description: We expect the partner to return a HTTP 200 status code if the callback was successfully received. On 4xx and 5xx status codes, we will [retry](/docs/callbacks#retries) the callback.
        cardTokenizationStatusChange:
          '{$request.body#/callbackUrl}':
            post:
              parameters:
              - in: header
                name: X-Organization-Id
                schema:
                  type: string
                  format: uuid
                  description: 'Referencing the organization this callback was sent for. See [guides](/docs/callbacks) for more details. Example value: `54e6e7e7-0c23-4a54-bccb-2d3ff2fd02df`.'
              - in: header
                name: X-Partner-Organization-Id
                schema:
                  type: string
                  description: 'Filled, if the value `partnerOrganizationId` is [set](/reference/update-organization) by the partner on the organization itself. Referencing the organization identifier of the partner. Example value: `abc123`.'
              - in: header
                name: X-Payment-Program-Id
                schema:
                  type: string
                  format: uuid
                  description: 'Referencing the payment program this callback was sent for. See [guides](/docs/callbacks) for more details. Example value: `54e6e7e7-0c23-4a54-bccb-2d3ff2fd02df`.'
              - in: header
                name: X-Callback-Id
                schema:
                  type: string
                  format: uuid
                  description: 'A unique identifier for this callback. Can be used to deduplicate callbacks to achieve idempotent behavior. See [guides](/docs/callbacks) for more details. Example value: `12a03093-eaad-4ae5-9d8d-42e7f6f8b7c6`.'
              - in: header
                name: X-Callback-Created-At
                schema:
                  type: string
                  format: date-time
                  description: 'The date and time when the callback was created. Can be used to reorder callbacks. See [guides](/docs/callbacks) for more details. Example value: `2024-03-15T15:55:58.623375258Z`.'
              requestBody:
                $ref: '#/components/requestBodies/TokenizationStatusCallback'
              responses:
                '200':
                  description: We expect the partner to return a HTTP 200 status code if the callback was successfully received. On 4xx and 5xx status codes, we will [retry](/docs/callbacks#retries) the callback.
    delete:
      summary: 'Callback: Remove'
      description: Remove a callback subscription for this entity.
      tags:
      - Mobile Wallet Tokenization
      operationId: remove-mobile-wallet-tokenization-subscription
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              properties:
                eventTypes:
                  type: array
                  description: The event types to unsubscribe from.
                  items:
                    type: string
                    enum:
                    - CARD_TOKENIZATION_OTP
                    - CARD_TOKENIZATION_STATUS_CHANGE
              required:
              - eventTypes
      responses:
        '200':
          description: Ok
  /mobile-wallet-tokenizations/{tokenizationId}:
    get:
      summary: Mobile Wallet Tokenization Details
      description: Return details for a single Mobile Wallet Token
      tags:
      - Mobile Wallet Tokenization
      operationId: get-mobile-wallet-tokenization-details
      parameters:
      - name: tokenizationId
        in: path
        description: The unique identifier of the tokenization.
        schema:
          type: string
          format: uuid
        required: true
      responses:
        '200':
          description: Ok
          content:
            application/json:
              schema:
                type: object
                $ref: '#/components/schemas/TokenizationDetails'
        '400':
          $ref: '#/components/responses/400'
        '401':
          $ref: '#/components/responses/401'
        '403':
          $ref: '#/components/responses/403'
        '429':
          $ref: '#/components/responses/429'
        '500':
          $ref: '#/components/responses/500'
components:
  schemas:
    Error:
      type: object
      properties:
        errorCode:
          type: string
          description: The error code
        exceptionId:
          type: string
          format: uuid
          description: The id of the exception that was thrown
        message:
          type: string
          description: The cause of the error or further explanations on the error
    TokenizationOTPCallback:
      properties:
        organizationId:
          type: string
          format: uuid
          description: The organization ID.
        cardId:
          type: string
          format: uuid
          description: The card ID.
        cardAccountId:
          type:
          - string
          - 'null'
          format: uuid
          description: The unique identifier of the card account this card belongs to.
        tokenizationId:
          type: string
          format: uuid
          description: The tokenization ID.
        otp:
          type: string
          description: The OTP for this tokenization process.
        activationMethod:
          type: string
          enum:
          - EMAIL
          - SMS
          - OTHER
          description: The activation method for the tokenization process, meaning how the OTP should be transferred to the cardholder. Valid values are `EMAIL`, `SMS` and `OTHER`. If `EMAIL`, the OTP should be send via email by the partner to the cardholder. If `SMS`, the OTP is send via SMS to the cardholder directly by Thredd (Pliant's credit card processor). The partner can omit this callback basically, or add additional logic if relevant. `OTHER` acts as a fallback if the activation method is not properly defined, it is up to the partner to decide the method then.
    TokenizationDetails:
      type: object
      properties:
        tokenizationId:
          type: string
          format: uuid
          description: The ID of the tokenization request, internal to Pliant.
        cardId:
          type: string
          format: uuid
          description: The ID of the card that was tokenized.
        organizationId:
          type: string
          format: uuid
          description: The ID of the organization that owns the card.
        wallet:
          type: string
          description: The type of wallet that is used. For now the only valid values are `APPLE` and `ANDROID`.
          enum:
          - APPLE
          - ANDROID
        tokenExpirationDate:
          type:
          - string
          - 'null'
          description: Date when this token expires.
          format: date
        deviceId:
          type:
          - string
          - 'null'
          description: A technical identification of the device that is carrying the mobile wallet.
        deviceName:
          type:
          - string
          - 'null'
          description: A user-defined name identifying the device that is carrying the mobile wallet.
        provisioningStatus:
          type: string
          description: The status of the provisioning flow overall. It can be used to determine if the cardholder has successfully tokenized a card in a mobile wallet. Details about the order of status can be found in our guides section about the [green](/docs/apple-pay-google-pay-integration#green-flow-status-changes) and [yellow](/docs/apple-pay-google-pay-integration#yellow-flow-status-changes) flow.
          enum:
          - TOKEN_CREATED
          - PASSCODE_SENT
          - TOKEN_PROVISIONED
          - TOKEN_ACTIVATED
          - TOKEN_ACTIVATION_FAILED
        tokenStatus:
          type: string
          description: The status of the provisioned token itself. So after the provisioning flow finishes (see `provisioningStatus`) the token becomes `ACTIVE` and can then change status depending on how the user acts with the credit card in his mobile wallet.
          enum:
          - ACTIVE
          - DEACTIVATED
          - DELETED
          - INACTIVE
          - SUSPENDED
          - UNKNOWN
        provisioningStartedAt:
          type: string
          description: Date and time when this token provisioning was started. The format of the date-time is `YYYY-MM-DDTHH:MM:SS.000000` in UTC.
          format: date-time
          example: '2024-07-19T01:02:03.000000'
        provisioningCompletedAt:
          type:
          - string
          - 'null'
          description: Date and time when this token provisioning was completed. The format of the date-time is `YYYY-MM-DDTHH:MM:SS.000000` in UTC.
          format: date-time
          example: '2024-07-19T01:02:03.000000'
        provisioningDeletedAt:
          type:
          - string
          - 'null'
          description: Date and time when this token provisioning was deleted. The format of the date-time is `YYYY-MM-DDTHH:MM:SS.000000` in UTC.
          format: date-time
          example: '2024-07-19T01:02:03.000000'
        tokenId:
          type:
          - string
          - 'null'
          description: The token ID generated by the mobile wallet to store the card.
    TokenizationStatusCallback:
      properties:
        organizationId:
          type: string
          format: uuid
        cardId:
          type: string
          format: uuid
        cardAccountId:
          type:
          - string
          - 'null'
          format: uuid
          description: The unique identifier of the card account this card belongs to.
        tokenizationId:
          type: string
          format: uuid
        provisioningStatus:
          type: string
          description: The status of the provisioning flow overall. It can be used to determine if the cardholder has successfully tokenized a card in a mobile wallet. Details about the order of status can be found in our guides section about the [green](/docs/apple-pay-google-pay-integration#green-flow-status-changes) and [yellow](/docs/apple-pay-google-pay-integration#yellow-flow-status-changes) flow.
          enum:
          - TOKEN_CREATED
          - PASSCODE_SENT
          - TOKEN_PROVISIONED
          - TOKEN_ACTIVATED
          - TOKEN_ACTIVATION_FAILED
        tokenStatus:
          type: string
          description: The status of the provisioned token itself. So after the provisioning flow finishes (see `provisioningStatus`) the token becomes `ACTIVE` and can then change status depending on how the user acts with the credit card in his mobile wallet.
          enum:
          - ACTIVE
          - DEACTIVATED
          - DELETED
          - INACTIVE
          - SUSPENDED
          - UNKNOWN
        deviceId:
          type:
          - string
          - 'null'
          description: A technical identification of the device that is carrying the mobile wallet.
        wallet:
          type: string
          description: The type of wallet that is used. For now the only valid values are `APPLE` and `ANDROID`.
          enum:
          - APPLE
          - ANDROID
    Event:
      type: object
      properties:
        eventType:
          type: string
          description: The type of event.
  responses:
    '429':
      description: Too Many Requests. The API consumer has sent too many requests in a given amount of time. Please check our [API guidelines](/docs/pliant-api-guidelines#api-rate-limits).
      content:
        application/json:
          schema:
            type: object
            properties:
              error:
                type: string
                description: Detailed description of the error and breached rate limit.
    '500':
      description: Internal Server Error. The request was not completed due to an internal error.
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
    '401':
      description: Unauthorized. The API consumer is not authorized to access the requested resource.
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
    '400':
      description: Bad Request. The API consumer sent a malformed request which could not be processed.
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
    '403':
      description: Forbidden. The API consumer is not allowed to access the requested resource.
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
  requestBodies:
    TokenizationOTPCallback:
      content:
        application/json:
          schema:
            allOf:
            - $ref: '#/components/schemas/Event'
            - $ref: '#/components/schemas/TokenizationOTPCallback'
    TokenizationStatusCallback:
      content:
        application/json:
          schema:
            allOf:
            - $ref: '#/components/schemas/Event'
            - $ref: '#/components/schemas/TokenizationStatusCallback'
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer
      description: This API uses oAuth2 with client credentials flow to [obtain the Bearer Token](/docs/authenticated-api-usage).
      bearerFormat: JWT
x-provenance:
  method: searched
  source: https://partner.getpliant.com/reference
  harvested: '2026-10-14'
  tool: harvest-readme-openapi.py
  note: Assembled verbatim from the OpenAPI definition ReadMe embeds in each operation page of the provider's developer portal; paths and components merged by API title, nothing authored.
  assembled_from:
  - https://partner.getpliant.com/reference/activate-partner-organization-authorization.md
  - https://partner.getpliant.com/reference/activate-physical-card.md
  - https://partner.getpliant.com/reference/approve-card-limit-requests.md
  - https://partner.getpliant.com/reference/approve-card-request.md
  - https://partner.getpliant.com/reference/assign-project-team.md
  - https://partner.getpliant.com/reference/assign-to-team.md
  - https://partner.getpliant.com/reference/batch-update-cards-limits.md
  - https://partner.getpliant.com/reference/bulk-upsert-subscriptions.md
  - https://partner.getpliant.com/reference/cancel-onboarding-submission.md
  - https://partner.getpliant.com/reference/card-pan-and-cvv-pci-vault.md
  - https://partner.getpliant.com/reference/claim-card-as-copilot.md
  - https://partner.getpliant.com/reference/create-access-link.md
  - https://partner.getpliant.com/reference/create-account-entry-subscription.md
  - https://partner.getpliant.com/reference/create-accounting-project-subscription.md
  - https://partner.getpliant.com/reference/create-accounting-team-subscription.md
  - https://partner.getpliant.com/reference/create-accounting-transaction-subscription.md
  - https://partner.getpliant.com/reference/create-and-submit-onboarding-submission.md
  - https://partner.getpliant.com/reference/create-beneficiary-payment-detail.md
  - https://partner.getpliant.com/reference/create-beneficiary-subscription.md
  - https://partner.getpliant.com/reference/create-beneficiary.md
  - https://partner.getpliant.com/reference/create-card-account-payout.md
  - https://partner.getpliant.com/reference/create-card-account-subscription.md
  - https://partner.getpliant.com/reference/create-card-account-transfer.md
  - https://partner.getpliant.com/reference/create-card-account.md
  - https://partner.getpliant.com/reference/create-card-control-subscription.md
  - https://partner.getpliant.com/reference/create-card-copilot-subscription.md
  - https://partner.getpliant.com/reference/create-card-limit-request-subscriptions.md
  - https://partner.getpliant.com/reference/create-card-limit-requests.md
  - https://partner.getpliant.com/reference/create-card-request-subscription.md
  - https://partner.getpliant.com/reference/create-card-request.md
  - https://partner.getpliant.com/reference/create-card-subscription.md
  - https://partner.getpliant.com/reference/create-cardholder-subscription.md
  - https://partner.getpliant.com/reference/create-cashback-subscription.md
  - https://partner.getpliant.com/reference/create-custom-field-option.md
  - https://partner.getpliant.com/reference/create-custom-field.md
  - https://partner.getpliant.com/reference/create-external-transfer-subscription.md
  - https://partner.getpliant.com/reference/create-external-transfer.md
  - https://partner.getpliant.com/reference/create-lead.md
  - https://partner.getpliant.com/reference/create-mobile-wallet-tokenization-subscription.md
  - https://partner.getpliant.com/reference/create-onboarding-submission-subscription.md
  - https://partner.getpliant.com/reference/create-onboarding-submission.md
  - https://partner.getpliant.com/reference/create-organization-subscription.md
  - https://partner.getpliant.com/reference/create-organization.md
  - https://partner.getpliant.com/reference/create-payment-subscription.md
  - https://partner.getpliant.com/reference/create-project.md
  - https://partner.getpliant.com/reference/create-receipt-automatching-subscription.md
  - https://partner.getpliant.com/reference/create-receipt-subscription.md
  - https://partner.getpliant.com/reference/create-statement-subscription.md
  - https://partner.getpliant.com/reference/create-team.md
  - https://partner.getpliant.com/reference/create-transaction-subscription.md
  - https://partner.getpliant.com/reference/create-vop-verification.md
  - https://partner.getpliant.com/reference/deactivate-card-account.md
  - https://partner.getpliant.com/reference/deactivate-cardholder.md
  - https://partner.getpliant.com/reference/deactivate-partner-organization-authorization.md
  - https://partner.getpliant.com/reference/deactivate-team.md
  - https://partner.getpliant.com/reference/delete-card-limit-requests.md
  - https://partner.getpliant.com/reference/delete-card-request.md
  - https://partner.getpliant.com/reference/delete-custom-field-option.md
  - https://partner.getpliant.com/reference/delete-custom-field.md
  - https://partner.getpliant.com/reference/delete-project.md
  - https://partner.getpliant.com/reference/delete-receipt.md
  - https://partner.getpliant.com/reference/delete-subscription.md
  - https://partner.getpliant.com/reference/delete-team.md
  - https://partner.getpliant.com/reference/delete-transaction-comment.md
  - https://partner.getpliant.com/reference/enable-pliant-app-access.md
  - https://partner.getpliant.com/reference/enroll-card-click-to-pay.md
  - https://partner.getpliant.com/reference/generate-test-transactions-in-sandbox.md
  - https://partner.getpliant.com/reference/get-account-entries.md
  - https://partner.getpliant.com/reference/get-accounting-transactions-batch.md
  - https://partner.getpliant.com/reference/get-available-cards.md
  - https://partner.getpliant.com/reference/get-beneficiaries.md
  - https://partner.getpliant.com/reference/get-beneficiary-details.md
  - https://partner.getpliant.com/reference/get-beneficiary-payment-detail.md
  - https://partner.getpliant.com/reference/get-beneficiary-payment-details.md
  - https://partner.getpliant.com/reference/get-callback-details.md
  - https://partner.getpliant.com/reference/get-callback-log.md
  - https://partner.getpliant.com/reference/get-callback-subscriptions.md
  - https://partner.getpliant.com/reference/get-callback.md
  - https://partner.getpliant.com/reference/get-card-account-details.md
  - https://partner.getpliant.com/reference/get-card-accounts-available-currencies.md
  - https://partner.getpliant.com/reference/get-card-accounts-summary.md
  - https://partner.getpliant.com/reference/get-card-accounts.md
  - https://partner.getpliant.com/reference/get-card-controls-by-card.md
  - https://partner.getpliant.com/reference/get-card-controls-supported-countries.md
  - https://partner.getpliant.com/reference/get-card-controls-supported-currencies.md
  - https://partner.getpliant.com/reference/get-card-limit-request-detail.md
  - https://partner.getpliant.com/reference/get-card-pin.md
  - https://partner.getpliant.com/reference/get-card-request-details.md
  - https://partner.getpliant.com/reference/get-card-requests.md
  - https://partner.getpliant.com/reference/get-cardholder-details.md
  - https://partner.getpliant.com/reference/get-cards.md
  - https://partner.getpliant.com/reference/get-cashback-amounts.md
  - https://partner.getpliant.com/reference/get-cashback-configuration.md
  - https://partner.getpliant.com/reference/get-cashback-history.md
  - https://partner.getpliant.com/reference/get-cashback-receipt.md
  - https://partner.getpliant.com/reference/get-cashback-transactions.md
  - https://partner.getpliant.com/reference/get-custom-field-options.md
  - https://partner.getpliant.com/reference/get-custom-fields.md
  - https://partner.getpliant.com/reference/get-external-transfer-details.md
  - https://partner.getpliant.com/reference/get-external-transfers.md
  - https://partner.getpliant.com/reference/get-mobile-wallet-tokenization-details.md
  - https://partner.getpliant.com/reference/get-mobile-wallet-tokenization.md
  - https://partner.getpliant.com/reference/get-multiple-card-details.md
  - https://partner.getpliant.com/reference/get-onboarding-reference-data-activity-codes.md
  - https://partner.getpliant.com/reference/get-onboarding-reference-data-industry.md
  - https://partner.getpliant.com/reference/get-onboarding-submission-document.md
  - https://partner.getpliant.com/reference/get-onboarding-submission.md
  - https://partner.getpliant.com/reference/get-organization-details.md
  - https://partner.getpliant.com/reference/get-organization-external-bank-account.md
  - https://partner.getpliant.com/reference/get-organization-risk-status.md
  - https://partner.getpliant.com/reference/get-organizations-external-bank-accounts.md
  - https://partner.getpliant.com/reference/get-otp-for-pci-widget.md
  - https://partner.getpliant.com/reference/get-partner-signing-jwks.md
  - https://partner.getpliant.com/reference/get-payment-program.md
  - https://partner.getpliant.com/reference/get-payments-detail.md
  - https://partner.getpliant.com/reference/get-payments.md
  - https://partner.getpliant.com/reference/get-project.md
  - https://partner.getpliant.com/reference/get-projects.md
  - https://partner.getpliant.com/reference/get-receipt-automatcher-status.md
  - https://partner.getpliant.com/reference/get-receipt-detail.md
  - https://partner.getpliant.com/reference/get-receipts.md
  - https://partner.getpliant.com/reference/get-single-card-details.md
  - https://partner.getpliant.com/reference/get-statement-csv.md
  - https://partner.getpliant.com/reference/get-statement-detail.md
  - https://partner.getpliant.com/reference/get-statementpdf.md
  - https://partner.getpliant.com/reference/get-statements.md
  - https://partner.getpliant.com/reference/get-team.md
  - https://partner.getpliant.com/reference/get-teams.md
  - https://partner.getpliant.com/reference/get-transactions-detail-batch.md
  - https://partner.getpliant.com/reference/get-transactions-detail.md
  - https://partner.getpliant.com/reference/get-transactions.md
  - https://partner.getpliant.com/reference/get-vop-verification.md
  - https://partner.getpliant.com/reference/invite-cardholders.md
  - https://partner.getpliant.com/reference/invite-owner.md
  - https://partner.getpliant.com/reference/issue-card-instant-with-pci.md
  - https://partner.getpliant.com/reference/issue-card-instant.md
  - https://partner.getpliant.com/reference/issue-card.md
  - https://partner.getpliant.com/reference/list-card-limit-requests.md
  - https://partner.getpliant.com/reference/list-cardholders.md
  - https://partner.getpliant.com/reference/list-identity-verifications.md
  - https://partner.getpliant.com/reference/list-onboarding-submissions.md
  - https://partner.getpliant.com/reference/list-organizations.md
  - https://partner.getpliant.com/reference/load-cards-batch.md
  - https://partner.getpliant.com/reference/lock-card.md
  - https://partner.getpliant.com/reference/metadata-receipt-to-automatcher.md
  - https://partner.getpliant.com/reference/reassign-platform-fee-card.md
  - https://partner.getpliant.com/reference/receipt-as-merged-pdf.md
  - https://partner.getpliant.com/reference/receipt-as-pdf.md
  - https://partner.getpliant.com/reference/receipt-original.md
  - https://partner.getpliant.com/reference/receipt-thumbnail.md
  - https://partner.getpliant.com/reference/redeem-cashback.md
  - https://partner.getpliant.com/reference/register-cardholders.md
  - https://partner.getpliant.com/reference/reject-card-limit-requests.md
  - https://partner.getpliant.com/reference/reject-card-request.md
  - https://partner.getpliant.com/reference/remove-account-entry-subscription.md
  - https://partner.getpliant.com/reference/remove-accounting-project-subscription.md
  - https://partner.getpliant.com/reference/remove-accounting-team-subscription.md
  - https://partner.getpliant.com/reference/remove-accounting-transaction-subscription.md
  - https://partner.getpliant.com/reference/remove-beneficiary-subscription.md
  - https://partner.getpliant.com/reference/remove-card-account-subscription.md
  - https://partner.getpliant.com/reference/remove-card-control-subscription.md
  - https://partner.getpliant.com/reference/remove-card-copilot-subscription.md
  - https://partner.getpliant.com/reference/remove-card-limit-request-subscription.md
  - https://partner.getpliant.com/reference/remove-card-request-subscription.md
  - https://partner.getpliant.com/reference/remove-cardholder-subscription.md
  - https://partner.getpliant.com/reference/remove-cards-subscription.md
  - https://partner.getpliant.com/reference/remove-cashback-subscription.md
  - https://partner.getpliant.com/reference/remove-external-transfer-subscription.md
  - https://partner.getpliant.com/reference/remove-mobile-wallet-tokenization-subscription.md
  - https://partner.getpliant.com/reference/remove-onboarding-submission-subscription.md
  - https://partner.getpliant.com/reference/remove-organization-subscription.md
  - https://partner.getpliant.com/reference/remove-payment-subscription.md
  - https://partner.getpliant.com/reference/remove-pliant-app-access.md
  - https://partner.getpliant.com/reference/remove-receipt-automatching-subscription.md
  - https://partner.getpliant.com/reference/remove-receipt-subscription.md
  - https://partner.getpliant.com/reference/remove-statement-subscription.md
  - https://partner.getpliant.com/reference/remove-transaction-subscription.md
  - https://partner.getpliant.com/reference/replace-card.md
  - https://partner.getpliant.com/reference/resend-callbacks.md
  - https://partner.getpliant.com/reference/revoke-access-link.md


# --- truncated at 32 KB (35 KB total) ---
# Full source: https://raw.githubusercontent.com/api-evangelist/hihealth/refs/heads/main/openapi/hihealth-mobile-wallet-tokenization-api-openapi.yml