Build with the Mobile Authorization API to request authorization tokens to initialize Square mobile solutions like the Reader SDK. To embed Square mobile development solutions, you must create a service to request mobile authorization codes. You should integrate this into your existing OAuth process if possible.
Build with the Mobile Authorization API
To build with the Mobile Authorization API, the following must be true:
- You're using HTTPS - HTTPS is required for all production Square API calls. HTTP calls are only supported for developing and testing on localhost.
- You're using production credentials - The Mobile Authorization API isn't supported in the Square Sandbox.
Additionally, you need the following information:
To use the steps in this topic, you need the following:
- An active location ID - Copy a valid developer account location ID from the Production mode Locations setting page of your Square application in the Developer Dashboard.
- A valid access token - For more information, see Access Tokens and Other Square Credentials.
Add code to use the location ID and OAuth token to request a mobile authorization code. The authorization service should return the mobile authorization code to the calling application but for the sake of this example, Square simply prints it to the screen.
Create mobile authorization code
Mobile authorization codes are short lived and should be used immediately to authorize mobile solutions like the Reader SDK. Mobile authorization doesn't expire after a set amount of time. Authorization remains valid unless it's explicitly revoked (for example, by calling
deauthorize in the Reader SDK) or the authorized application fails to take a payment within 90 days.