# API Touchpoints Supported Fynd Konnect provides a comprehensive suite of REST APIs that enable seamless integration between your ERP/WMS systems and various sales channels. Our APIs follow standard HTTP protocols and support JSON-encoded requests and responses, making integration straightforward and efficient. Curious about our API capabilities? Visit our [API Reference](/konnect/apis/konnect) to dive into the complete specification and experiment with our endpoints. ### Authorization The Generate Access Token API provide secure access management for Fynd Konnect channels. They allow the generation of access tokens at both company and location levels, enabling robust authentication for all subsequent API calls. This endpoint ensure controlled permissions across the organization, handle token refresh cycles, and validate token integrity, establishing a secure foundation for interaction with the platform’s services. br Explore Generate Access Token API Specification Company Level Auth - Generates an access token that works across all APIs for all stores/warehouses within a seller account. It provides a comprehensive view and control over the entire company's e-commerce operations. Location Level Auth - Creates an access token for a particular store or warehouse. Each store requires a separate token for managing orders, allowing for more granular control and security at the individual location level. ### Catalog #### Product Count The Product Count API retrieves accurate SKU count in real time, assisting with catalog synchronization and inventory reconciliation by monitoring catalog health and completeness. br Explore Product Count API Specification Use Cases - Pre-Inventory Update Check: Helps verify the current SKU count before initiating any bulk inventory updates, ensuring data consistency. - System Health Monitoring: Acts as an effective tool for monitoring inventory integrity, helping identify discrepancies in SKU counts between systems. Best Practices - Schedule Regular Calls: Execute this API call at regular intervals to maintain synchronization and identify missing SKUs. - Integrate with Dashboards: Use the SKU count data for inventory reporting and dashboard analytics, giving a quick overview of current stock availability. #### Product Listings The Product Listings API fetches detailed SKU information with support for pagination and filtering, returning complete product details—including pricing—which is essential for bulk data retrieval and system synchronization. br Explore Product Listings API Specification Features - Supports pagination parameters such as `page_number` and `page_size`, which optimize the retrieval process for larger catalogs. - Allows filtering results by specific SKU identifiers, making it easy to narrow down the search to relevant products. - Supports multi-attribute filtering, enabling results to be refined based on attributes like category, brand, or status. Use Cases - Batch Inventory Updates: Retrieve SKUs in batches to update inventory, pricing, or product attributes more efficiently. - Data Validation: Helps validate whether specific SKUs are listed, ensuring the completeness of data before performing other operations. Best Practices - Optimize Page Size: Adjust the `page_size` parameter based on system capabilities, ideally set to a maximum of 500. - Use Filters Wisely: Apply specific filters to limit the results, reducing unnecessary data load and enhancing processing efficiency. - Combine with Inventory Check: Use this API in conjunction with the Get Product Count API to ensure the listings match the total SKU count, ensuring consistency. ### Pricing #### Update Price The Update Price API enables dynamic price management across the product catalog. It facilitates the updating of Maximum Retail Price (MRP) and Effective Selling Price (ESP) for multiple SKUs simultaneously, supporting bulk operations and synchronization of prices across various sales channels. br Explore Update Price API Specification Use Cases - Promotional Adjustment: Modify prices during sales or special events. - Price Synchronization: Align prices across multiple sales channels. - Dynamic Pricing: Enable regular updates to respond to market trends. Best Practices - Bulk Updates: Use bulk price updates for efficiency. - Frequent Scheduling: Schedule regular price updates to reflect real-time changes. - Integrate with Promotions: Link pricing updates to promotional campaigns on Fynd Commerce for seamless adjustments. ### Inventory #### Update Inventory The Update Inventory API provides real-time stock management across multiple store locations. It supports bulk inventory adjustments, stock transfers, and ensures that inventory levels are accurately maintained across all sales channels. By preventing overselling through instant updates, Update Inventory endpoint plays a crucial role in maintaining inventory accuracy and operational efficiency. br Explore Update Inventory API Specification Use Cases - Replenishment: Adjust inventory levels when new stock arrives. - Out-of-Stock Management: Update stock to reflect product unavailability. - Seasonal Adjustments: Prepare stock levels based on seasonal demand. Best Practices - Daily Updates: Schedule updates at least once daily for real-time accuracy. - Delta Updates: Use delta updates to minimize data load and improve performance. - Combine with Inventory Checks: Use this API with the Get Product Count API to verify accuracy. ### Orders #### Fetch Orders br Fetch Orders retrieves orders based on status filters with pagination and detailed order information for status tracking and monitoring. Explore Get Orders API Specification Features - Supports pagination to handle large datasets, allowing efficient data management. - Enables filtering by order status, such as `CREATED`, `CONFIRMED`, `PROCESSING`, etc. Use Cases - Batch Processing: Retrieve multiple orders at once for bulk operations. - Order Tracking: Monitor both the forward and return order flows. Best Practices - Use filters to narrow down results and manage data load. - Regularly poll for order status updates to keep systems in sync. #### Fetch Order by ID Fetch Order by ID allows detailed lookups of individual orders, providing item-level specifics, payment, shipment, and customer information. br Explore Get Order by ID API Specification Details - Parameter: `orderId` (required) - The unique identifier of the order to be retrieved. - Benefit: Provides a detailed view of order specifics, allowing precise tracking, analysis, and management. - Response Structure: Returns order ID, item details, payment status, shipment info, and timestamps. Use Cases - Customer Support: Quickly access order details to assist with inquiries. - Order Analysis: Review order history and transaction details for analytics. Best Practices - Use this endpoint for troubleshooting or analyzing individual order issues. - Combine with order modification or cancellation for efficient management. #### Order Cancellation Order Cancellation manages the cancellation process for entire orders or specific bag items. br Explore Order Cancellation API Specification Details - Response Structure: Provides confirmation of cancellation status, including order ID and affected items. Use Cases - Modify Orders: Cancel unconfirmed orders due to stock issues or customer requests. - Inventory Management: Free up inventory when cancellations are made. Best Practices - Ensure the order is not yet confirmed before initiating cancellation. - Use cancellation reason codes for tracking and analysis. #### Order Confirmation Order Confirmation streamlines the processing of bulk order confirmations, updating statuses efficiently and integrating with fulfillment workflows. br Explore Order Confirmation API Specification Details - Benefit: Streamlines workflow by confirming multiple orders at once, improving operational efficiency. - Response Structure: Returns confirmation status, order IDs, and success/failure details. Use Cases - Batch Confirmation: Confirm large numbers of orders simultaneously for bulk processing. - Order Finalization: Lock orders for fulfillment to prevent further modifications. Best Practices - Use bulk confirmation during high-volume sales events. - Validate order data before confirmation to avoid discrepancies. #### Update Invoice Update Invoice enables the third-party Aggregators to push customer invoices to Fynd, managing tax calculations and supporting multiple formats. br Explore Update Invoice API Specification Ensure the order is confirmed before updating invoice information. Use Cases - Invoice Generation: Finalize order details and generate invoices for shipping. - Financial Reconciliation: Align invoicing data with financial systems. Best Practices - Validate invoice data before submission to avoid errors. - Regularly synchronize invoice status with financial records. #### Courier Details Courier Details fetches logistics information like Airway Bill Number (AWB) and courier assignments to facilitate shipment tracking. br Explore Courier Details API Specification Use Cases - Shipment Tracking: Provide customers with accurate tracking information. - Logistics Analysis: Monitor courier performance and delivery times. Best Practices - Integrate with customer-facing systems for real-time tracking updates. - Use this information for analyzing courier performance and delivery times. #### Shipping Label Shipping Label generates standardized labels for packages, supporting various standard shipping requirements and enabling bulk label creation. br Explore Shipping Label API Specification Details Shipping labels contain crucial information such as destination address, sender address, tracking numbers, and barcodes required by courier services. Use Cases - Order Preparation: Retrieve shipping labels to affix on packages before dispatch. - Compliance: Ensure that packages meet courier and regulatory requirements with correct labeling. - Efficiency: Streamline the packaging process by generating labels in bulk. Best Practices - Validate Order Status: Ensure orders are packed or ready for shipping before generating labels. - Bulk Generation: Generate labels for multiple orders at once to save time. - Integration: Integrate label generation into your warehouse management system for seamless operations. #### Customer Invoice Customer Invoice produces detailed billing documentation, including tax and pricing breakdowns, ensuring regulatory compliance. br Explore Customer Invoice API Specification Use Cases - Customer Communication: Include invoices in shipments to provide customers with purchase details. - Accounting: Use invoices for financial reconciliation and record-keeping. - Compliance: Ensure compliance with tax regulations by providing accurate invoices. Best Practices - Verify Invoice Details: Ensure all invoice information is accurate and up-to-date before sending. - Digital Storage: Keep digital copies of invoices for record-keeping and auditing purposes. - Automate Generation: Integrate invoice generation into your order processing workflow to reduce manual effort. #### Order Pack Using the Order Pack, Aggregator can update Fynd when orders are packed and ready for dispatch. br Explore Order Pack API Specification Use Cases - Fulfillment Preparation: Mark orders as packed to signal readiness for dispatch. - Batch Operations: Update multiple orders simultaneously during batch packing. Best Practices - Verify Cancellation Status: Check if any orders have been canceled before packing to avoid processing errors. - System Integration: Integrate packing status updates with your warehouse management system for efficient workflow. - Coordinate with Shipping Schedules: Use packing status to align with courier pickup times. #### Order Dispatch Marks orders as dispatched, indicating they have left the warehouse and are en route to the customer br Explore Order Dispatch API Specification Details - Benefit: Updates order status for all stakeholders, providing visibility into the shipping process. - Response Structure: Returns dispatch status, tracking information, and order ID. Use Cases - Shipping Confirmation: Confirm that orders are on their way to customers. - Logistics Coordination: Trigger real-time tracking updates to customers and logistics teams. Best Practices - Coordinate with Courier Services: Ensure that the dispatch status aligns with the actual pickup by the courier. - Notify Customers: Send shipment notifications to customers with tracking information. - Update Inventory Systems: Reflect the dispatch in your inventory management to maintain accurate stock levels. ### Returns #### Fetch Returns Retrieves information on shipments that are marked with return statuses, providing insights into the return process br Explore Get Returns API Specification Use Cases - Return Tracking: Monitor the status of returns for timely processing. - Analytics: Analyze return patterns to identify common issues and improve product quality or service. Best Practices - Regular Monitoring: Poll for return updates regularly to ensure timely handling. - Customer Service Integration: Provide up-to-date return information to customer service teams. - Data Analysis: Use return data to identify trends and implement improvements. #### Update Return & QC Accepts returned items and updates the system based on quality inspection results br Explore Update Return & QC API Specification Use Cases - Return Processing: Confirm the acceptance or rejection of returned items based on quality checks. - Inventory Replenishment: Restock acceptable returns to improve inventory levels. Best Practices - Detailed Documentation: Clearly document the reason codes and QC results. - System Updates: Update inventory and financial systems based on QC outcomes. - Compliance: Ensure adherence to company policies and legal requirements during the QC process. #### Credit Note Issues and posts credit notes for returned items, facilitating accurate financial reconciliation for refunds br Explore Credit Note API Specification Use Cases - Refund Processing: Issue credit notes as part of the return management process, allowing for prompt customer refunds. - Financial Reconciliation: Align return-related financial transactions with credit note issuance. Best Practices - Verify Return Completion: Ensure return acceptance is complete before issuing credit notes. - Accurate Record-Keeping: Maintain detailed records of issued credit notes for auditing. - Automation: Integrate credit note issuance with accounting systems to streamline financial adjustments.