When you publish a Lapp –
- You’ll receive an API URL and security token for each environment (test and live).
- Calls to the Lapps API URL should always be POST.
- This security token should be passed in the request header as x-api-key.
- Once a Lapp is published, if you’ve written logs, the Logs option will show up in your navigation menu.
- Published Lapps can be used in automation, webhooks and rules and notifications in your LeadSquared application.
- Click the Save button to save your code.
- Once your code is saved, the Publish button will appear alongside the Save button. When you click the Publish button, the option to publish your Lapp to the test environment will appear. You can only publish a Lapp to live once it is published to the test environment.
- Once published to test, you’ll see a pop-up with your API URL and Token.
- The Logs link will also appear in your navigation menu on the left side of the page.
Logs will only appear after your Lapp is published. In the example below, we’re pushing some data to a Lapp using Postman (https://www.getpostman.com) and then reviewing the logs –
- Copy and paste the Lapp API URL in Postman (you can use any similar tool).
- Set the HTTP Method to POST.
- Create the API Header “x-api-key” in Postman and copy and paste the Lapp security token.
- Pass the API body (“Message”: “Hello World” in this example) in JSON format.
- Click the Logs option in the navigation pane in LeadSquared.
- Click the Edit (wheel) icon to view Lapp Request Details and Code Logs.
- There might be a delay of maximum 1 minute between calling the Lapp API and the logs showing up.
- Logs will be auto-deleted after a certain period of time.
After publishing a Lapp you can call it from –