- LIGHTSPEED RETAIL API DOCUMENTATION HOW TO
- LIGHTSPEED RETAIL API DOCUMENTATION INSTALL
- LIGHTSPEED RETAIL API DOCUMENTATION FULL
- LIGHTSPEED RETAIL API DOCUMENTATION VERIFICATION
- LIGHTSPEED RETAIL API DOCUMENTATION LICENSE
Make sure you have set an expiry for every personal token you create. Set an expiry on each Personal Token you create
LIGHTSPEED RETAIL API DOCUMENTATION HOW TO
If you don't know how to rotate or change a token, it's likely that an application is a better fit. If the Personal Token needs to be changed, you'll need to know how to rotate/change it. If a Personal Token is created under your Retail POS user, create a descriptive name so you know where it's being used. Understand how you're using a Personal Token If you do require long-term use, it is best to use OAuth 2.0 authorisation as described in our developer documentation. These credentials consist of an access key and a secret, but they also include a token that allows you to renew the access key automatically when the access key expires. Instead, you can generate credentials through the Retail POS developer portal. In many scenarios, you will not need a long-term personal access token that never expires. Do not use Personal Tokens for long-term use You can use tools from Lightspeed like an API explorer or Postman collection to build a sense for what data you have access to. You can also choose to have 'Inactive' tokens turn red in X days. Get familiar with the API docs from Lightspeed Review the API documentation from Lightspeed to see what data you might be able to pull into Google Sheets. For example, < 30 days (Green), < 90 days (Yellow), < 180 days (Red).
To make this easier, we have implemented a change to the personal token user interface in Retail POS that displays 'token age'. It is best to change personal access tokens on a regular basis. By removing any unused tokens you will be reducing the risk of misuse going forward.
LIGHTSPEED RETAIL API DOCUMENTATION FULL
Personal Tokens provide full access to the retailer's store. Make sure you remove any unused Personal Tokens.
LIGHTSPEED RETAIL API DOCUMENTATION INSTALL
Installation Use your favorite package manager to install any of the packages and save to your package. The best way to do it is by adding the Authorization header, just like it's done for OAuth tokens: Authorization: Bearer _here_goes_your_token_īest Practices for managing personal tokens Remove unused Personal Tokens Lightspeed SDK Note: This is not a Lightspeed official package. If you do require long-term use, it is best to use OAuth 2.0 authorisation as described in our developer documentation.Įvery request to sent to the Retail POS API needs to be authorised. You can extend or remove the expiry date by editing the current token or creating a new one. If the token you have provided a developer expires, the integration they have built will no longer work. If you are building multiple apps for your store it is recommended you create a token for each app. All your existing tokens will still work as usual. Once the token is saved, you will not be able to view your Personal Tokens in clear text in the Personal Tokens page. You can then copy the token to send it through to your developer(s).
Once this is done click Generate Personal Token. It is also important to make this unique to avoid any confusion if you have multiple tokens active.Įxpiry date: This will be disabled by default however, if you only want the custom integration or script to be able to access your data for a limited time, you can specify a token expiry date. Token name: for this field put in a name for your reference. To create a token navigate to Setup -> Personal Tokens Make sure you send this privately and don’t publicly share the information anywhere. Offers are subject to approval.By providing a developer with this token they will have full access to the data in your store.
LIGHTSPEED RETAIL API DOCUMENTATION LICENSE
Zolve Azpire Credit Cards are issued by Community Federal Savings Bank, Member FDIC pursuant to its license from Mastercard, and are subject to the terms of Azpire Deposit Account and Azpire Credit Card Agreement. Deposits are subject to FDIC insurance up to the legally permissible amount. Zolve Debit Cards are issued by Community Federal Savings Bank, Member FDIC pursuant to its license with Mastercard, and are subject to the terms of a Deposit Account and Debit Card Agreement. Zolve Credit Cards are issued by Community Federal Savings Bank, Members FDIC pursuant to its license from Mastercard, and are subject to the terms of a Cardholder Agreement. All banking products are provided by our partnering banks. is a financial technology company, not a bank or lender.
LIGHTSPEED RETAIL API DOCUMENTATION VERIFICATION
They are subject to completion and verification of the application as per the predetermined criteria established by Zolve. *Pre-approved offers do not guarantee approval.
0 kommentar(er)
