REST Calls

The Reverse Invoke REST API provides the JSON-based calls required to change and coordinate synchronization states between the daemon and Talk2Sync.

These operations allow the daemon to communicate the current synchronization state, exchange product and order data, report processing results, and complete synchronization transactions.

Available REST Calls

The following operations are available as part of the Talk2Sync Reverse Invoke API:

• Ask if Fetching — Checks whether Talk2Sync is requesting data from the external system.
• Push Products Page — Sends a page of products to Talk2Sync.
• Set Finish Products Push — Marks the product push operation as completed.
• Push Orders Page — Sends a page of orders to Talk2Sync.
• Set Finish Orders Push — Marks the order push operation as completed.
• Set Finish All Pushes — Completes the overall push operation.
• Ask if Pulling — Checks whether Talk2Sync has data available for the external system to retrieve.
• Pull Products Page — Retrieves a page of products from Talk2Sync.
• Get Next Product to Pull — Retrieves the next product pending processing.
• Notify Product Success — Reports that a product was successfully stored.
• Notify Product Failure — Reports that a product could not be stored.
• Set Finish Product Pulls — Marks the product pull operation as completed.
• Pull Orders Page — Retrieves a page of orders from Talk2Sync.
• Get Next Orders to Pull — Retrieves the next orders pending processing.
• Notify Orders Success — Reports that orders were successfully stored.
• Notify Orders Failure — Reports that orders could not be stored.
• Set Finish Order Pulls — Marks the order pull operation as completed.
• Transact Finish Pull — Completes the current pull transaction.

Next Steps

Review the REST calls according to the synchronization direction:

• Fetching changes: Use the fetching operations when the daemon needs to send data to Talk2Sync.
• Pulling changes: Use the pulling operations when the daemon needs to retrieve data from Talk2Sync.

For the complete sequence in which these operations are executed, see the Reverse Connections Protocol.