Punchh Loyalty Transfers API

The Loyalty Transfers API from Punchh — 3 operation(s) for loyalty transfers.

Operations 3

POST /api2/mobile/loyalty_transfers/points Transfer Loyalty Points #
POST /api2/mobile/loyalty_transfers/currency Transfer Loyalty Currency #
POST /api2/mobile/loyalty_transfers/reward Transfer Loyalty Reward #

Documentation

Specifications

Schemas & Data

📊
JSONSchema
https://raw.githubusercontent.com/api-evangelist/punchh/refs/heads/main/json-schema/mobile-access-token-schema.json
📊
JSONSchema
https://raw.githubusercontent.com/api-evangelist/punchh/refs/heads/main/json-schema/mobile-create-user-request-schema.json
📊
JSONSchema
https://raw.githubusercontent.com/api-evangelist/punchh/refs/heads/main/json-schema/mobile-login-request-schema.json
📊
JSONSchema
https://raw.githubusercontent.com/api-evangelist/punchh/refs/heads/main/json-schema/mobile-mark-offers-read-request-schema.json
📊
JSONSchema
https://raw.githubusercontent.com/api-evangelist/punchh/refs/heads/main/json-schema/mobile-transaction-details-request-schema.json
📊
JSONSchema
https://raw.githubusercontent.com/api-evangelist/punchh/refs/heads/main/json-schema/mobile-transaction-details-schema.json
📊
JSONSchema
https://raw.githubusercontent.com/api-evangelist/punchh/refs/heads/main/json-schema/mobile-update-user-profile-request-schema.json
📊
JSONSchema
https://raw.githubusercontent.com/api-evangelist/punchh/refs/heads/main/json-schema/mobile-user-session-schema.json
📊
JSONStructure
https://raw.githubusercontent.com/api-evangelist/punchh/refs/heads/main/json-structure/mobile-access-token-structure.json
📊
JSONStructure
https://raw.githubusercontent.com/api-evangelist/punchh/refs/heads/main/json-structure/mobile-create-user-request-structure.json
📊
JSONStructure
https://raw.githubusercontent.com/api-evangelist/punchh/refs/heads/main/json-structure/mobile-login-request-structure.json
📊
JSONStructure
https://raw.githubusercontent.com/api-evangelist/punchh/refs/heads/main/json-structure/mobile-mark-offers-read-request-structure.json
📊
JSONStructure
https://raw.githubusercontent.com/api-evangelist/punchh/refs/heads/main/json-structure/mobile-transaction-details-request-structure.json
📊
JSONStructure
https://raw.githubusercontent.com/api-evangelist/punchh/refs/heads/main/json-structure/mobile-transaction-details-structure.json
📊
JSONStructure
https://raw.githubusercontent.com/api-evangelist/punchh/refs/heads/main/json-structure/mobile-update-user-profile-request-structure.json
📊
JSONStructure
https://raw.githubusercontent.com/api-evangelist/punchh/refs/heads/main/json-structure/mobile-user-session-structure.json
📊
JSONSchema
https://raw.githubusercontent.com/api-evangelist/punchh/refs/heads/main/json-schema/online-ordering-online-order-checkin-request-schema.json
📊
JSONSchema
https://raw.githubusercontent.com/api-evangelist/punchh/refs/heads/main/json-schema/online-ordering-online-order-checkin-response-schema.json
📊
JSONSchema
https://raw.githubusercontent.com/api-evangelist/punchh/refs/heads/main/json-schema/online-ordering-online-order-redemption-request-schema.json
📊
JSONSchema
https://raw.githubusercontent.com/api-evangelist/punchh/refs/heads/main/json-schema/online-ordering-online-order-redemption-response-schema.json
📊
JSONStructure
https://raw.githubusercontent.com/api-evangelist/punchh/refs/heads/main/json-structure/online-ordering-online-order-checkin-request-structure.json
📊
JSONStructure
https://raw.githubusercontent.com/api-evangelist/punchh/refs/heads/main/json-structure/online-ordering-online-order-checkin-response-structure.json
📊
JSONStructure
https://raw.githubusercontent.com/api-evangelist/punchh/refs/heads/main/json-structure/online-ordering-online-order-redemption-request-structure.json
📊
JSONStructure
https://raw.githubusercontent.com/api-evangelist/punchh/refs/heads/main/json-structure/online-ordering-online-order-redemption-response-structure.json
📊
JSONSchema
https://raw.githubusercontent.com/api-evangelist/punchh/refs/heads/main/json-schema/platform-functions-redeemable-schema.json
📊
JSONStructure
https://raw.githubusercontent.com/api-evangelist/punchh/refs/heads/main/json-structure/platform-functions-redeemable-structure.json

Other Resources

🔗
Examples
https://raw.githubusercontent.com/api-evangelist/punchh/refs/heads/main/examples/mobile-access-token-example.json
🔗
Examples
https://raw.githubusercontent.com/api-evangelist/punchh/refs/heads/main/examples/mobile-create-user-request-example.json
🔗
Examples
https://raw.githubusercontent.com/api-evangelist/punchh/refs/heads/main/examples/mobile-login-request-example.json
🔗
Examples
https://raw.githubusercontent.com/api-evangelist/punchh/refs/heads/main/examples/mobile-mark-offers-read-request-example.json
🔗
Examples
https://raw.githubusercontent.com/api-evangelist/punchh/refs/heads/main/examples/mobile-transaction-details-example.json
🔗
Examples
https://raw.githubusercontent.com/api-evangelist/punchh/refs/heads/main/examples/mobile-transaction-details-request-example.json
🔗
Examples
https://raw.githubusercontent.com/api-evangelist/punchh/refs/heads/main/examples/mobile-update-user-profile-request-example.json
🔗
Examples
https://raw.githubusercontent.com/api-evangelist/punchh/refs/heads/main/examples/mobile-user-session-example.json
🔗
JSONLD
https://raw.githubusercontent.com/api-evangelist/punchh/refs/heads/main/json-ld/punchh-mobile-context.jsonld
🔗
PostmanCollection
https://raw.githubusercontent.com/api-evangelist/punchh/refs/heads/main/collections/punchh-mobile.postman_collection.json
🔗
OpenCollection
https://raw.githubusercontent.com/api-evangelist/punchh/refs/heads/main/collections/punchh-mobile.opencollection.json
🔗
Examples
https://raw.githubusercontent.com/api-evangelist/punchh/refs/heads/main/examples/online-ordering-online-order-checkin-request-example.json
🔗
Examples
https://raw.githubusercontent.com/api-evangelist/punchh/refs/heads/main/examples/online-ordering-online-order-checkin-response-example.json
🔗
Examples
https://raw.githubusercontent.com/api-evangelist/punchh/refs/heads/main/examples/online-ordering-online-order-redemption-request-example.json
🔗
Examples
https://raw.githubusercontent.com/api-evangelist/punchh/refs/heads/main/examples/online-ordering-online-order-redemption-response-example.json
🔗
JSONLD
https://raw.githubusercontent.com/api-evangelist/punchh/refs/heads/main/json-ld/punchh-online-ordering-context.jsonld
🔗
PostmanCollection
https://raw.githubusercontent.com/api-evangelist/punchh/refs/heads/main/collections/punchh-online-ordering.postman_collection.json
🔗
OpenCollection
https://raw.githubusercontent.com/api-evangelist/punchh/refs/heads/main/collections/punchh-online-ordering.opencollection.json
🔗
Examples
https://raw.githubusercontent.com/api-evangelist/punchh/refs/heads/main/examples/platform-functions-redeemable-example.json
🔗
JSONLD
https://raw.githubusercontent.com/api-evangelist/punchh/refs/heads/main/json-ld/punchh-platform-functions-context.jsonld
🔗
PostmanCollection
https://raw.githubusercontent.com/api-evangelist/punchh/refs/heads/main/collections/punchh-platform-functions.postman_collection.json
🔗
OpenCollection
https://raw.githubusercontent.com/api-evangelist/punchh/refs/heads/main/collections/punchh-platform-functions.opencollection.json

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • 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/punchh-loyalty-transfers-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.

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

OpenAPI Specification

punchh-loyalty-transfers-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: Mobile Loyalty Transfers API
  version: '1.0'
  contact:
    name: Punchh Dev Support
    url: https://developers.punchh.com
  description: 'Punchh provides a robust platform for offering loyalty programs to customers. When a business integrates its back-end with the Punchh server, the Punchh APIs become instrumental in executing loyalty programs for enrolled customers, primarily via business-branded mobile apps and websites tailored by Punchh.


    To establish integration with the Punchh APIs, you need to understand how they are invoked and what responses are returned by the Punchh server. You can call APIs using any suitable API test client, such as Postman. Thus, the response to every API call made in Postman under a chosen environment (in app and/or platform) is reflected in the app and/or platform.'
servers:
- url: https://SERVER_NAME_GOES_HERE.punchh.com
tags:
- name: Loyalty Transfers
paths:
  /api2/mobile/loyalty_transfers/points:
    post:
      summary: Transfer Loyalty Points
      description: 'Enables a user to transfer loyalty points from their account to another user''s account by specifying the recipient''s email address or phone number and the number of points to transfer.


        The recipient must be an existing member in the loyalty system. The transfer is subject to the business''s configured transfer limits, including maximum transfer limits per account and daily receiving limits for the recipient.


        **Prerequisite**<br>

        Peer-to-peer points transfers must be enabled for the business. Contact your Punchh representative to update this Punchh platform configuration.

        <!--Cockpit > Earnings > Transferred Loyalty Expiry > Enable Peer-to-Peer Points Transfers-->'
      operationId: mobile_loyalty_transfer_points
      tags:
      - Loyalty Transfers
      parameters:
      - $ref: '#/components/parameters/signature'
      - $ref: '#/components/parameters/Content-Type'
      - $ref: '#/components/parameters/Accept-Language'
      - $ref: '#/components/parameters/User-Agent'
      - $ref: '#/components/parameters/Authorization'
      responses:
        '200':
          description: OK
          content:
            application/json:
              schema:
                type: array
                items:
                  type: string
              examples:
                default:
                  value:
                  - 1 transferred to Recipient Name
        '400':
          description: Bad Request
          content:
            application/json:
              schema:
                type: object
                properties:
                  error:
                    type: string
              examples:
                Missing required parameter:
                  value:
                    error: 'Required parameter missing or the value is empty: points_to_transfer'
                Missing recipient email or identifier:
                  value: "{\n    \"errors\": {\n        \"recipient_email\": \"Required parameter missing or the value is empty.\",\n        \"recipient_email_or_recipient_identifier\": \"Required parameter missing or the value is empty\"\n    }\n}"
        '401':
          description: Unauthorized
          content:
            application/json:
              schema:
                type: object
                properties:
                  error:
                    type: string
              examples:
                Unauthorized:
                  value:
                    error: You need to sign in or sign up before continuing.
        '422':
          description: Unprocessable Entity
          content:
            application/json:
              schema:
                type: array
                items:
                  type: string
              examples:
                Insufficient balance:
                  value:
                  - Not enough reward balance available to redeem. Current Balance of 96 is less than 100 requested
                No user found for the provided email or phone number:
                  value:
                  - Recipient not found
                Receiver limit exceeded:
                  value:
                  - Receiver limit exceeded for points (max 5 in 30h)
                Duplicate phone numbers:
                  value:
                  - Something went wrong with the transfer. Please check your input and try again.
                Daily receiving limit reached:
                  value:
                  - This transfer cannot be completed because the receiving member has reached the daily receiving limit.
                Maximum transfer limit exceeded:
                  value:
                  - Your transfer cannot be completed because it exceeds the maximum transfer limit set for your account.
                Invalid password:
                  value:
                  - Invalid password. Please try again.
                Service unavailable:
                  value:
                  - This service is currently unavailable for your account. Please contact support.
                Password required:
                  value:
                  - Password is required for peer-to-peer transfer.
      requestBody:
        content:
          application/json:
            schema:
              type: object
              properties:
                client:
                  type: string
                  description: OAuth client ID provided by the business
                access_token:
                  type: string
                  description: Token issued to the user after logging into the app of the business
                recipient_email:
                  type: string
                  description: Email address of the recipient to whom the loyalty points will be transferred. <br><br><b>Note:</b> Either `recipient_email` or `recipient_identifier` is required. When both `recipient_identifier` and `recipient_email` are provided, `recipient_identifier` takes precedence.
                recipient_identifier:
                  type: string
                  description: 'Accepts either an email address or a phone number to identify the recipient of the points transfer. `recipient_identifier` is the primary parameter used to identify the recipient. The system automatically detects whether the provided value is an email address or a phone number. <br><br><b>Note:</b> Either `recipient_email` or `recipient_identifier` is required. When both `recipient_identifier` and `recipient_email` are provided, `recipient_identifier` takes precedence.

                    * If a valid phone number or email matches a single guest account, the transfer proceeds.

                    * If a phone number matches multiple guest accounts, the transfer is blocked, and an error is returned. To prevent duplicate phone number error, we recommend enabling phone number uniqueness for the business. Contact your Punchh representative to update this Punchh platform configuration.

                    * If no matching guest is found for the provided email or phone number, a "recipient not found" error is returned.'
                points_to_transfer:
                  type: number
                  description: Number of loyalty points to transfer to the recipient
                password:
                  type: string
                  description: Password of the user initiating the transfer. Required for peer-to-peer transfer.
              required:
              - client
              - access_token
              - points_to_transfer
              - password
            examples:
              Using email:
                value:
                  client: CLIENT_GOES_HERE
                  access_token: ACCESS_TOKEN_GOES_HERE
                  recipient_email: recipient@example.com
                  recipient_identifier: recipient@example.com
                  points_to_transfer: '1'
                  password: PASSWORD_GOES_HERE
              Using phone number:
                value:
                  client: CLIENT_GOES_HERE
                  access_token: ACCESS_TOKEN_GOES_HERE
                  recipient_identifier: '1111111111'
                  points_to_transfer: '1'
                  password: PASSWORD_GOES_HERE
  /api2/mobile/loyalty_transfers/currency:
    post:
      summary: Transfer Loyalty Currency
      description: 'Enables a user to transfer loyalty currency (banked reward balance) from their account to another user''s account by specifying the recipient''s email address or phone number and the amount to transfer.


        The recipient must be an existing member in the loyalty system. The transfer is subject to the business''s configured transfer limits, including maximum transfer limits per account and daily receiving limits for the recipient.


        **Prerequisite**<br>

        Peer-to-peer currency transfers must be enabled for the business. Contact your Punchh representative to update this Punchh platform configuration.

        <!--Cockpit > Earnings > Transferred Loyalty Expiry > Enable Peer-to-Peer Currency Transfers-->'
      operationId: mobile_loyalty_transfer_currency
      tags:
      - Loyalty Transfers
      parameters:
      - $ref: '#/components/parameters/signature'
      - $ref: '#/components/parameters/Content-Type'
      - $ref: '#/components/parameters/Accept-Language'
      - $ref: '#/components/parameters/User-Agent'
      - $ref: '#/components/parameters/Authorization'
      responses:
        '200':
          description: OK
          content:
            application/json:
              schema:
                type: array
                items:
                  type: string
              examples:
                default:
                  value:
                  - $1.00 transferred to Recipient Name
        '400':
          description: Bad Request
          content:
            application/json:
              schema:
                type: object
                properties:
                  error:
                    type: string
              examples:
                Missing required parameter:
                  value:
                    error: 'Required parameter missing or the value is empty: amount_to_transfer'
                Missing recipient email or identifier:
                  value: "{\n    \"errors\": {\n        \"recipient_email\": \"Required parameter missing or the value is empty.\",\n        \"recipient_email_or_recipient_identifier\": \"Required parameter missing or the value is empty\"\n    }\n}"
        '401':
          description: Unauthorized
          content:
            application/json:
              schema:
                type: object
                properties:
                  error:
                    type: string
              examples:
                Unauthorized:
                  value:
                    error: You need to sign in or sign up before continuing.
        '422':
          description: Unprocessable Entity
          content:
            application/json:
              schema:
                type: array
                items:
                  type: string
              examples:
                Insufficient balance:
                  value:
                  - Not enough reward balance available to redeem. Current Balance of $96.00 is less than $100.00 requested
                No user found for the provided email or phone number:
                  value:
                  - Recipient not found
                Receiver limit exceeded:
                  value:
                  - Receiver limit exceeded for currency (max 5 in 30h)
                Duplicate phone numbers:
                  value:
                  - Something went wrong with the transfer. Please check your input and try again.
                Daily receiving limit reached:
                  value:
                  - This transfer cannot be completed because the receiving member has reached the daily receiving limit.
                Maximum transfer limit exceeded:
                  value:
                  - Your transfer cannot be completed because it exceeds the maximum transfer limit set for your account.
                Invalid password:
                  value:
                  - Invalid password. Please try again.
                Service unavailable:
                  value:
                  - This service is currently unavailable for your account. Please contact support.
                Password required:
                  value:
                  - Password is required for peer-to-peer transfer.
      requestBody:
        content:
          application/json:
            schema:
              type: object
              properties:
                client:
                  type: string
                  description: OAuth client ID provided by the business
                access_token:
                  type: string
                  description: Token issued to the user after logging into the app of the business
                recipient_email:
                  type: string
                  description: Email address of the recipient to whom the loyalty currency will be transferred. <br><br><b>Note:</b> Either `recipient_email` or `recipient_identifier` is required. When both `recipient_identifier` and `recipient_email` are provided, `recipient_identifier` takes precedence.
                recipient_identifier:
                  type: string
                  description: 'Accepts either an email address or a phone number to identify the recipient of the currency transfer. `recipient_identifier` is the primary parameter used to identify the recipient. The system automatically detects whether the provided value is an email address or a phone number. <br><br><b>Note:</b> Either `recipient_email` or `recipient_identifier` is required. When both `recipient_identifier` and `recipient_email` are provided, `recipient_identifier` takes precedence.

                    * If a valid phone number or email matches a single guest account, the transfer proceeds.

                    * If a phone number matches multiple guest accounts, the transfer is blocked, and an error is returned. To prevent duplicate phone number error, we recommend enabling phone number uniqueness for the business. Contact your Punchh representative to update this Punchh platform configuration.

                    * If no matching guest is found for the provided email or phone number, a "recipient not found" error is returned.'
                amount_to_transfer:
                  type: number
                  description: Amount of loyalty currency to transfer to the recipient
                password:
                  type: string
                  description: Password of the user initiating the transfer. Required for peer-to-peer transfer.
              required:
              - client
              - access_token
              - amount_to_transfer
              - password
            examples:
              Using email:
                value:
                  client: CLIENT_GOES_HERE
                  access_token: ACCESS_TOKEN_GOES_HERE
                  recipient_email: recipient@example.com
                  recipient_identifier: recipient@example.com
                  amount_to_transfer: '1'
                  password: PASSWORD_GOES_HERE
              Using phone number:
                value:
                  client: CLIENT_GOES_HERE
                  access_token: ACCESS_TOKEN_GOES_HERE
                  recipient_identifier: '1111111111'
                  amount_to_transfer: '1'
                  password: PASSWORD_GOES_HERE
  /api2/mobile/loyalty_transfers/reward:
    post:
      summary: Transfer Loyalty Reward
      description: 'Enables a user to transfer a loyalty reward from their account to another user''s account by specifying the recipient''s email address or phone number and the reward ID to transfer.


        The recipient must be an existing member in the loyalty system. The transfer is subject to the business''s configured transfer limits, including maximum transfer limits per account and daily receiving limits for the recipient.


        **Prerequisite**<br>

        Peer-to-peer rewards transfers must be enabled for the business. Contact your Punchh representative to update this Punchh platform configuration.

        <!--Cockpit > Earnings > Transferred Loyalty Expiry > Enable Peer-to-Peer Rewards Transfers-->'
      operationId: mobile_loyalty_transfer_reward
      tags:
      - Loyalty Transfers
      parameters:
      - $ref: '#/components/parameters/signature'
      - $ref: '#/components/parameters/Content-Type'
      - $ref: '#/components/parameters/Accept-Language'
      - $ref: '#/components/parameters/User-Agent'
      - $ref: '#/components/parameters/Authorization'
      responses:
        '200':
          description: OK
          content:
            application/json:
              schema:
                type: array
                items:
                  type: string
              examples:
                default:
                  value:
                  - Base Redeemable transferred to Recipient Name
        '400':
          description: Bad Request
          content:
            application/json:
              schema:
                type: object
                properties:
                  error:
                    type: string
              examples:
                Missing required parameter:
                  value:
                    error: 'Required parameter missing or the value is empty: reward_to_transfer'
                Missing recipient email or identifier:
                  value: "{\n    \"errors\": {\n        \"recipient_email\": \"Required parameter missing or the value is empty.\",\n        \"recipient_email_or_recipient_identifier\": \"Required parameter missing or the value is empty\"\n    }\n}"
        '401':
          description: Unauthorized
          content:
            application/json:
              schema:
                type: object
                properties:
                  error:
                    type: string
              examples:
                Unauthorized:
                  value:
                    error: You need to sign in or sign up before continuing.
        '422':
          description: Unprocessable Entity
          content:
            application/json:
              schema:
                type: array
                items:
                  type: string
              examples:
                Reward does not exist:
                  value:
                  - Reward doesn't exist or has already been redeemed.
                No user found for the provided email or phone number:
                  value:
                  - Recipient not found
                Receiver limit exceeded:
                  value:
                  - Receiver limit exceeded for rewards (max 5 in 30h)
                Duplicate phone numbers:
                  value:
                  - Something went wrong with the transfer. Please check your input and try again.
                Daily receiving limit reached:
                  value:
                  - This transfer cannot be completed because the receiving member has reached the daily receiving limit.
                Maximum transfer limit exceeded:
                  value:
                  - Your transfer cannot be completed because it exceeds the maximum transfer limit set for your account.
                Invalid password:
                  value:
                  - Invalid password. Please try again.
                Service unavailable:
                  value:
                  - This service is currently unavailable for your account. Please contact support.
                Password required:
                  value:
                  - Password is required for peer-to-peer transfer.
      x-stoplight:
        id: loyalty-transfers-reward
      requestBody:
        content:
          application/json:
            schema:
              type: object
              properties:
                client:
                  type: string
                  description: OAuth client ID provided by the business
                access_token:
                  type: string
                  description: Token issued to the user after logging into the app of the business
                recipient_email:
                  type: string
                  description: Email address of the recipient to whom the loyalty reward will be transferred. <br><br><b>Note:</b> Either `recipient_email` or `recipient_identifier` is required. When both `recipient_identifier` and `recipient_email` are provided, `recipient_identifier` takes precedence.
                recipient_identifier:
                  type: string
                  description: 'Accepts either an email address or a phone number to identify the recipient of the reward transfer. `recipient_identifier` is the primary parameter used to identify the recipient. The system automatically detects whether the provided value is an email address or a phone number. <br><br><b>Note:</b> Either `recipient_email` or `recipient_identifier` is required. When both `recipient_identifier` and `recipient_email` are provided, `recipient_identifier` takes precedence.

                    * If a valid phone number or email matches a single guest account, the transfer proceeds.

                    * If a phone number matches multiple guest accounts, the transfer is blocked, and an error is returned. To prevent duplicate phone number error, we recommend enabling phone number uniqueness for the business. Contact your Punchh representative to update this Punchh platform configuration.

                    * If no matching guest is found for the provided email or phone number, a "recipient not found" error is returned.'
                reward_to_transfer:
                  type: number
                  description: ID of the reward to transfer to the recipient
                password:
                  type: string
                  description: Password of the user initiating the transfer. Required for peer-to-peer transfer.
              required:
              - client
              - access_token
              - reward_to_transfer
              - password
            examples:
              Using email:
                value:
                  client: CLIENT_GOES_HERE
                  access_token: ACCESS_TOKEN_GOES_HERE
                  recipient_email: recipient@example.com
                  recipient_identifier: recipient@example.com
                  reward_to_transfer: '73786533580'
                  password: PASSWORD_GOES_HERE
              Using phone number:
                value:
                  client: CLIENT_GOES_HERE
                  access_token: ACCESS_TOKEN_GOES_HERE
                  recipient_identifier: '1111111111'
                  reward_to_transfer: '73786533580'
                  password: PASSWORD_GOES_HERE
components:
  parameters:
    Accept-Language:
      schema:
        type: string
        default: en
      name: Accept-Language
      in: header
      description: Preferred language
    signature:
      schema:
        type: string
        default: '{{$$.env.signature}}'
      name: x-pch-digest
      in: header
      description: The [signature](/docs/dev-portal-mobile/additional-topics/signature-sha256) for the API call
      required: true
    User-Agent:
      schema:
        type: string
        default: AppName/AppVersion/BuildNumber (OS; Model; MANUFACTURER; MODEL; OS Version)
      in: header
      name: User-Agent
      description: Used to identify the software, device, and application initiating the request, providing information about the client to the server. For details, see [User Agent](/docs/dev-portal-mobile/additional-topics/user-agent).
      required: true
    Content-Type:
      schema:
        type: string
        default: application/json
      name: Content-Type
      in: header
      description: Set this header to <b>application/json</b>.
      required: true
    Authorization:
      schema:
        type: string
        default: Bearer ACCESS_TOKEN_GOES_HERE
      name: Authorization
      in: header
      description: Used to authorize the request with access_token. It should be supplied as `Bearer ACCESS_TOKEN_GOES_HERE`.
      required: true
x-stoplight:
  id: bf6eddb435209
x-ext-urls: {}