Obtaining API Credentials
ERPNext authenticates to Unicommerce with four values from your Uniware account. Gather them before you open the settings page; they are all you need for ERPNext to fetch an access token on its own.
The values you need
| Value | Example | Purpose |
|---|---|---|
| Unicommerce Site | demostaging.unicommerce.com |
Your tenant host |
| Client ID | my-trusted-client |
The API client identifier issued for your tenant. |
| Username | apiuser@yourcompany |
The Uniware user the integration acts as. |
| Password | - | That user's password. |
Where each value comes from
- Unicommerce Site is the host portion of your Uniware URL. If you sign in at
https://acme.unicommerce.co.in, your site isacme.unicommerce.co.in. - Client ID is provided by Unicommerce when API access is enabled for your tenant. If you do not have one, request it from Unicommerce support.
- Username and Password should belong to a dedicated integration account rather than an individual's login. A dedicated account keeps the integration working when staff change and makes its activity easy to audit.
Permissions the account needs
Grant the integration user permission to:
- Read sales orders, invoices, and shipments. Required for order sync.
- Read and write items. Required only if you push ERPNext Items to Unicommerce.
- Read inventory snapshots and adjust inventory. Required only if you use GRN sync.
Tip: Validate the setup against your staging tenant (for example
demostaging.unicommerce.com) before pointing ERPNext at production. The credentials and behaviour are identical, so nothing about the configuration changes when you switch environments.
Last updated 2 months ago
Was this helpful?