Skip to end of banner
Go to start of banner

On-boarding Requirements

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Current »

Increff RMS as a service is integrated to multiple platforms like Cleartax for E-Invoicing and Clickpost, Shiprocket and Shipway which are Logistic Aggregators. To use these platforms via Increff RMS brands would have to configure the credentials for these platforms on RMS UI. This section is dedicated to such on boarding flows.

Also RMS as a product is available as a SAAS offering. The process of account creation for RMS is as mentioned below.

Clickpost

  • The following credentials would be required for Clickpost

    • username

    • apikey

    • webhookKey - This is only required if Brands want notifications to be pushed from RMS

  • If the Brand already has a Clickpost account, the account manager would help in getting these credentials.

  • For RMS to consume notifications from Clickpost and send the notifications to Brands, the RMS url has to be configured on the logistic aggregator panel and the webhook would have to be configured on RMS UI.

    • Go to the Clickpost settings page

    • Select the Notification tab.

    • Go to the Webhooks: Selected status section

    • There the client can select which all statuses to be pushed to RMS. The same statuses will be pushed by RMS to the client’s system.

    • In the same page, the client has to configure RMS’s url in the webhook url. RMS Clickpost Notification URL: https://saas.increff.com/rms/in/api/clickpost/notify

    • The generated key displayed on this page here has to be set as the webhook key on RMS UI.

Shiprocket

  • The following credentials would be required for Clickpost

    • email

    • password

    • webhookKey - This is only required if Brands want notifications to be pushed from RMS

  • The email and password here are the Shiprocket API user credentials and not the Login credentials. They can be generated by Brands by

    • Go to Shiprocket Home page after logging in.

    • Go to the Settings page from the sidebar.

    • In the API section, click on Configure

    • The Settings-Configure tab opens. Here a new Shiprocket API user can be created by clicking on the “Create an API User“ button. Enter the email and password.

    • These same email and password will then be configured on RMS UI.

  • For RMS to consume notifications from Shiprocket and send the notifications to Brands, the RMS url has to be configured on the logistic aggregator panel and the webhook would have to be configured on RMS UI.

    • Go to Shiprocket Home page after logging in.

    • Go to the Settings page from the sidebar.

    • In the API section go to Webhooks

    • Type in the RMS’s url in the URL field. RMS Shiprocket Notification URL:https://saas.increff.com/rms/in/api/st/notify

    • Whatever has been set as webhook key on the RMS UI for Shiprocket will have to be set in the token field.

Shipway

  • The following credentials are required for Shipway

    • Email - This email is the same as your Shipway Login email.

    • License Key

  • To get License Key

    • Go to Shipway Home page.

    • On the top right corner, click on the username to open the dropdown

    • Click on Profile

    • Go to Manage Profile section

    • The License Key will be present in this page.

  • For RMS to consume notifications from Shipway and send the notifications to Brands, the below RMS url would have to be shared with the Shipway team.

  • No labels