DocumentationDocumentation
Talk2Sync Documentation
User Documentation
Connector APIs
  • English
  • Español
Talk2Sync Documentation
User Documentation
Connector APIs
  • English
  • Español
  • User Guide Portal & API Documentation
  • User-documentation

    • User Documentation
    • Guide

      • User Guide: Introduction
      • Core Concepts
    • Talk2sync

      • Connection Buttons
      • Color Coding System
      • Issues and Alerts
      • Command Filters
      • Deleted Information Still Appears: How to Remove It
      • Deletions
    • Conexiones

      • Connection Settings
    • Fields

      • Time Based Sync
      • Data Governance
      • Special and Extra Fields
    • Productos

      • Product Fields
      • Equivalences
      • Product Search
      • Link / Unlink Products
    • Ventas

      • Fields
      • Equivalences
      • Sales Search
      • No SKU (Missing SKU)
    • Reports

      • Product Export
      • Sales Report
    • Faq

      • Amazon

        • Amazon Barcode Requirements
        • Amazon Catalog Discrepancies and ASIN Mismatches
        • Amazon Manufacturer Requirements
        • New ASIN Creation Errors and Invalid Attribute Values
        • Talk2sync, SKUs, and Product Identifiers
        • Amazon Variation Templates
      • Mercadolibre

        • Mercado Libre Official Stores
        • Mercado Libre Locations and Geographic Attributes
        • Mercado Libre Pick-up in Store
        • Mercado Libre Extra Attributes
        • Mercado Libre Image Processing and Synchronization
        • Mercado Libre Seller Unable to List Error
      • Linio

        • Linio Brand Not Registered Error
        • Linio Physical Dimensions and Weight Requirements
  • Connector APIs

    • Connector APIs
    • Quick-start

      • Introduction & Requirements
      • Add Connection
      • Configure Connection
      • Generate Keys
      • Test Your Integration
    • Webhooks

      • Webhooks API
      • Catalog

        • Webhooks: List Products
        • Webhooks: List Product by ID
        • Webhooks: Add/Update Product
      • Sales

        • Webhooks: List Orders
        • List Order by ID
        • Add/Update Order
    • Reverse-connections

      • Reverse Connections
      • Implementation-states

        • Implementation
        • Query Implementation: Products and Orders
        • Store Implementation: Products and Orders
        • Sleep and Timeouts
      • Protocol

        • Protocol
        • Overview
        • Product Upload
        • Order Upload
        • Product Download
        • Order Download
      • Rest-calls

        • REST Calls
        • Fetching-changes

          • Fetching Changes REST Calls
          • Ask if Fetching
          • Catalog

            • Push Products Page
            • Set Finish Product Pushes
          • Sales

            • Push Orders Page
            • Set Finish Order Pushes
            • Set Finish All Pushes
        • Pulling-changes

          • Pulling Changes REST Calls
          • Ask if Pulling
          • Catalog

            • Get Next Product to Pull
            • Pull Products Page
            • Notify Product Storage Success
            • Notify Product Storage Failure
            • Set Finish Product Download
          • Sales

            • Get Next Order to Pull
            • Pull Orders Page
            • Notify Order Storage Success
            • Notify Order Storage Failure
            • Set Finish Order Download
            • Transact Finish Pull

Push Products Page

The Push Products Page operation initializes the upstream synchronization process and sends product data from the external system to Talk2Sync.

Before sending products, the daemon must determine the current upstream state, synchronization strategy, entity, and cursor position. It must then initialize the upstream process and select the appropriate endpoint depending on whether Talk2Sync is requesting a health-check sample or the complete product dataset.

1. Check the Upstream State

First, retrieve the current upstream connection status:

GET https://api.talk2sync.com/api/adapters/custom/reverse/connection/{{your key}}/upstreamstatus

A response should have a structure similar to:

{
  "connectionstatus": "waiting"
}

The waiting status indicates that the upstream process is ready to be initialized.

2. Check the Synchronization Strategy

Retrieve the strategy currently requested by Talk2Sync:

GET https://api.talk2sync.com/api/adapters/custom/reverse/connection/{{your key}}/strategy

The response can be:

{
  "strategy": "push"
}

or:

{
  "strategy": "pingsample"
}

The strategy determines whether the daemon must send the complete dataset or only a sample for health checks.

  • push — Send the complete dataset.
  • pingsample — Send a sample of the dataset for health-check purposes.

3. Check the Requested Entity

Retrieve the entity currently being requested:

GET https://api.talk2sync.com/api/adapters/custom/reverse/connection/{{your key}}/entity

The response should identify the requested entity:

{
  "entity": "products"
}

or:

{
  "entity": "orders"
}

For this operation, the daemon should continue with the product upload flow only when the returned entity is products.

4. Retrieve the Cursor Offset

Retrieve the current cursor position:

GET https://api.talk2sync.com/api/adapters/custom/reverse/connection/{{your key}}/cursoroffset

A response should have a structure similar to:

{
  "cursoroffset": 1517358864869
}

The cursoroffset represents the last update timestamp, in milliseconds, of the last record discovered by Talk2Sync for the currently selected entity type.

This value can be used by the external system to determine which records should be considered during the synchronization process.

5. Initialize the Upstream Process

After obtaining the required connection information, initialize the upstream process:

POST https://api.talk2sync.com/api/adapters/custom/reverse/connection/{{your key}}/push/initialize

The endpoint should return HTTP status 200.

After initialization, querying the upstream status again should return:

{
  "connectionstatus": "initialized"
}

The daemon should proceed only after the upstream process has been successfully initialized.

6. Select the Product Push Operation

If the requested entity is products, the daemon can begin sending product data.

The endpoint depends on the previously retrieved synchronization strategy.

Sample Push

When the strategy is pingsample, send a sample for health-check purposes:

POST https://api.talk2sync.com/api/adapters/custom/reverse/connection/{{your key}}/pingsample/products

Full Product Push

When the strategy is push, send the product dataset:

POST https://api.talk2sync.com/api/adapters/custom/reverse/connection/{{your key}}/push/products

7. Product Payload

The request body should contain a products array with the products being sent to Talk2Sync:

{
  "products": [
    {
      "_id": "100004777",
      "sku": "100004777",
      "last_updated": 1517360038797,
      "title": "EON618S JBL SUBWOOFER 18\" AMPLIFICADO",
      "url": "",
      "brand": "",
      "mpn": "",
      "model": "",
      "description": "JBL Premium Transducers",
      "variations": [
        {
          "availabilities": [
            {
              "tag": "default",
              "quantity": "50"
            }
          ],
          "prices": [
            {
              "tag": "default",
              "currency": "USD",
              "number": "1060.51"
            }
          ],
          "images": [
            {
              "url": "https://www.example.com/13080-thickbox_default/eon618s-jbl-subwoofer-18-amplificado-.jpg"
            }
          ],
          "videos": [
            {
              "url": ""
            }
          ],
          "barcode": "",
          "size": "",
          "color": ""
        }
      ]
    }
  ]
}

Process Summary

The complete operation follows this sequence:

Next Steps

  • Review Set Finish Products Push to complete the product upload operation.
  • Review Push Orders Page for the corresponding order upload process.
  • Review the Product Upload protocol to understand where this operation fits in the complete reverse connection flow.
Last Updated: 8/21/26, 12:13 PM
Next
Set Finish Product Pushes