Skip to content
gokart-logo-v3
GoKart - Documentation - Offer Wall Integration
  • Pages
    • Welcome
    • Glossary
    • icon picker
      SDK API Schema Disclaimer
    • API Release Notes
      • API Release Notes 1.0.1
      • API Release Notes 1.0.2
      • API Release Notes 1.0.3
      • API Release Notes 1.0.4
    • Integration with GoKart
      • 1. Offer Wall Integration
        • Integration Options
          • URL
            • Example #1
            • Example #2
            • Example #3
            • Example #4
          • Iframe
            • Example #1
            • Example #2
            • Example #3
            • Example #4
          • API
            • v1
              • Offer-Centric
                • Get Offers
                  • Example
                • Get Offer Details
                • Get Offer Link
                • Get Offer Link Redirect
              • PubMember-Centric
                • Get Offers
              • General Schemas
                • Response Data
                • Pagination
                • Filterting & Sorting
                • Addtl Query Parameters
          • API Rate Limits
      • 2. Conversion Callback Integration
        • Integration Options
          • API
            • Security Options
            • Schema: v1
    • Tracking Parameters
      • Publisher Parameters
        • pub_gender
        • pub_age
        • pub_geo_country
        • pub_geo_state
        • pub_postal_code
        • pub_sub_#
      • GoKart Parameters
      • Conversion Parameters
    • Monitoring
      • View, Click, Conversion
      • Event History Logs
    • Environments
      • Your Own Tenant
        • Your Web App
        • Your Web API
    • Live Technical Support
gokart-logo-v3
GoKart - Documentation - Offer Wall Integration
/
SDK API Schema Disclaimer
Share
Explore

SDK API Schema Disclaimer

Important Notice

Our API schema is continuously evolving as we add new fields and capabilities. To ensure a smooth integration, please design your implementation to be flexible enough to handle additional fields without relying on strict field matching. We are committed to backward compatibility, which means that while new fields may be introduced, existing fields will neither be removed nor altered.
Key Recommendations:
Dynamic Schema: New fields may be introduced over time. Please design your integration to be robust and adaptable.
Flexible Integration: Avoid enforcing strict matching rules. This approach helps prevent integration issues as our API evolves.
Backward Compatibility: We guarantee that existing fields will remain unchanged, ensuring that previous integrations continue to work seamlessly.
Stay Updated: Regularly consult our
Release Notes
⁠
to review the latest changes and updates.
Thank you for your understanding and cooperation.


Want to print your doc?
This is not the way.
Try clicking the ··· in the right corner or using a keyboard shortcut (
CtrlP
) instead.