Sticky.io Connector – Tables, API Endpoints, Versioning, and Load Strategy

The Sticky.io Connector integrates subscription commerce, billing, customer, and order data directly from Sticky.io APIs. Sticky.io currently exposes entities across multiple API versions (Legacy/V1, V2, and V3). Based on endpoint availability and data completeness, the connector uses the corresponding API version for each entity.

Official Documentation:
• https://developer.sticky.io/
• API Reference: https://developer.sticky.io/reference

Countries

This table contains country master data used across orders, billing, shipping, and customer entities.

The connector retrieves reference country information directly from Sticky.io.

API Version: V3
Endpoint Used: /v3/countries
Load Type: Full Load

Channels

This table contains configured acquisition and sales channel information.

This entity currently uses a legacy endpoint as no equivalent documented V2/V3 endpoint is available.

API Version: Legacy / Old API
Endpoint Used: Internal legacy endpoint
Documentation: Not publicly documented
Load Type: Full Load

Payment_Methods

This table contains payment method configurations available within Sticky.io.

The data is extracted as reference information for transaction and subscription billing.

API Version: V3
Endpoint Used: /v3/payment-methods
Load Type: Full Load

Shipping

This table contains shipping configurations and fulfillment-related information.

Shipping methods and operational metadata are extracted as complete snapshots.

API Version: V3
Endpoint Used: /v3/shipping
Load Type: Full Load

Contacts

This table contains customer contact and profile information stored in Sticky.io.

Records include customer identifiers, communication details, account references, and update metadata.

Incremental sync captures newly created and modified records.

API Version: V3
Endpoint Used: /v3/contacts
Incremental Parameter: Updated timestamp filters
Load Type: Incremental

CustomerCustomFields

This table contains customer-level custom attributes configured within Sticky.io.

The table enables extraction of custom metadata attached to customer records.

API Version: V3
Endpoint Used: /v3/customer-custom-fields
Load Type: Full Load

CustomFields

This table stores custom field definitions available within Sticky.io.

Each record defines reusable metadata fields across supported entities.

API Version: V3
Endpoint Used: /v3/custom-fields
Load Type: Full Load

Orders

This table contains order and transaction information generated within Sticky.io.

Each record includes order identifiers, customer information, pricing details, payment references, statuses, and timestamps.

Although Sticky.io provides V3 documentation references, order extraction currently relies on the V1 implementation because equivalent functionality is not available in V2.

Supported incremental extraction allows efficient synchronization of historical and ongoing order updates.

Documentation Reference: V3 Order Documentation
Actual API Version Used: V1
Endpoint Used:
POST https://{{app_key}}.sticky.io/api/v1/order_find

This API returns a large volume of order IDs (approximately 50K records in historical loads). To retrieve detailed order information, the connector calls the child API:

POST https://{{app_key}}.sticky.io/api/v1/order_view
 the order_view API has a processing limitation and supports parsing a maximum of 500 order IDs per request. To ensure reliability and avoid source-side limitations, the current implementation processes order details sequentially by invoking the API one order at a time for detail extraction will improvise these soon 

Incremental Parameters Used:

start_time

end_time

Pagination: Page based
Load Type: Incremental

Subscriptions

This table contains recurring subscription lifecycle and billing information.

Records include subscription identifiers, customer references, billing schedules, subscription status, products, and recurring payment metadata.

Subscription extraction leverages newer APIs where available while maintaining compatibility with existing source support.

Documentation References:
V3 Subscription Documentation
V2 Subscription Documentation

API Version Used: V2

Endpoint Used:
GET /v2/subscriptions

Incremental Parameters Used:

start_date

end_date

Pagination: Cursor/Page based
Load Type: Incremental

Accounts

This table contains account-level configuration and administrative metadata.

Account data is synchronized through full extraction.

API Version: V3
Endpoint Used: /v3/accounts
Load Type: Full Load

Users

This table contains user and access configuration details.

Records include user information, permissions, and account assignments.

API Version: V3
Endpoint Used: /v3/users
Load Type: Full Load

Billing_Models

This table contains billing configuration models used to define recurring payment behavior.

Records include billing schedules, pricing definitions, and rebill logic.

API Version: V3
Endpoint Used: /v3/billing-models
Load Type: Full Load

Campaigns

This table contains marketing and campaign configuration data.

Records include campaign identifiers, statuses, names, and operational metadata.

API Version: V3
Endpoint Used: /v3/campaigns
Load Type: Full Load

API Version Summary

I updated it to focus on actual API version + endpoint used per table, instead of generic descriptions.