Standard Integrations APIs

Introduction

Increff Omni provides a set standard of APIs which help external systems integrate with Increff Omni system

Index
Integrating any ERP with Increff OMS
Integrating any E-Commerce Webshop with Increff OMS
Integrating any POS system (Store) with Increff OMS
Integrating any WMS with Increff OMS
- Listing and Inventory APIs
  - Listing Creation For EFS
  - Update Inventory in Increff OMS
- Orders Events
  - Push Outward Order Events API
  - Push Outward Order Events API (Beta)
- Picklist APIs
  - Create Picklist for Orders In Increff OMS
  - Add Orders to PickList
- Order Processing and Update APIs
- Return APIs
- Search Store Orders API
- Migrating from Increff v0 to v1 OMS APIs
Authentication
- Get Credential
Masters APIs
- SKU Masters (Product Masters)
- Vendor Masters
- Customer Masters
- Sending Masters through FTP
- Bundled SKU Definition APIs
Inwards APIs
- Inward Orders Creation APIs
  - Create Inward Order API
  - Create Inward Order API (Beta)
- Inward Order Modifications APIs
- ASN APIs
- Inward Order Posting Notifications APIs
  - Receiving (GRN) updates against Order APIs
  - Receiving (GRN) updates against Gate Entry APIs
- Get Item Barcode Details API (For Inward Orders)
- Generate Item Codes API
- Search Inward Order Strategies (New API)(Beta)
Outwards APIs
- Outward Order Creation APIs
- Outward Order Processing APIs
- Outward Order modification APIs
- Outward Order Notifications API to External systems (ERP/POS)
- Custom Order Attributes
  - Search Custom Order Attributes Keys API
  - Search Custom Order Attributes API
- Cross Dock APIs
- Get Item Barcode Details APIs (For Outward Orders)
  - Get Item Barcode Details API (For B2C Orders)
  - Get Item Barcode Details API (For B2B Orders)
- Cart Split Shipment and Estimate Delivery Date API
- Cart Split Shipment API (New API)(Beta)
Inventory APIs
- (Location Wise) Available To Promise Inventory API
- (Consolidated) Available To Promise Inventory
- Search Inventory API (For ERP and Marketplace Channels)
- Push Available to Promise Inventory API (For Stores)
- Search Inventory API (For Marketplace channels)(Beta)
- Get Locations Details API
Returns APIs
- Create Return Order API
- Create Return Order API (Beta)
- Cancel Return Order Items API
- Return Order Acknowledgement API
- Update Returns API
- Return Order Posting API (For ERP Systems)
- Return Order Posting API (For ERP Systems)(Beta)
- Return Order Processed Notification to POS
- Return Order Processed Notification to POS (Beta)
- Add Items to Existing Return Orders API (Beta)
Integration APIs FAQs
Error Handling in APIs
Tax Code Specification
Rate Limiting Strategy
API Testing
- ASIM (Omni Integration Api Simulator)
- Template for Testing
- Increff-Client onbarding on Staging
State Names (Indian)
Possible Nuances while using Increff Standard APIs
Integration Terminology
Marketplaces Integrating with Increff Standard APIs

Why should we integrate using Increff Omni APIs? Why Increff Omni cannot integrate with our ERP or E-Commerce Portal?

Increff Omni APIs have functionality for both ERP and e-commerce integrations. As opposed to this, if we integrate with clients, then we will need to integrate with 2 separate sets of APIs – one for ERP and another for e-commerce. This becomes highly inefficient.

You get any upgrades for free – any new features we develop here for other clients get automatically available to you also for integration. These could be related to integrations with WCS (for example).

Our team can support you better, as they have full expertise on our APIs. If we consume your APIs then it results in a lot of client specific KT at our end.

Integrating with our APIs is faster, cheaper, and bug free. Many large brands and brand-houses have rapidly integrate with us. Typically, clients can integrate with us in a month, while it takes ~2-3 months for us to integrate with clients.

The interfaces provided by clients are usually inadequate. Often APIs provided by clients miss proper error handling, data size handling, idempotency etc. Our APIs are very comprehensive and encompass all use-cases that we have encountered till date.

Clients are unable to provide good API documentation. This leads to too many unnecessary meetings / KT sessions. We have a comprehensive documentation.