FMTC Tech Corner: API v3

Twitter Facebook Linked In Paper Plan

Written by Josh Hutter

Welcome to the latest edition of FMTC’s Tech Corner. Today we are diving into the exciting features of our new v3 API endpoints. Whether you’re a long-time subscriber of FMTC’s or just getting started, this comprehensive guide will equip you with the knowledge you need to harness the power of our upgraded API. 

Key Changes in v3

  • URL Structure: The latest v3 endpoints are now accessed via, marking a shift from the previous domain.
  • New Fields: Additional fields like coupon_code_on_page, code_verified_at, and link_verified_at have been introduced, offering more detailed information about deals.
    • coupon_code_on_page
      • This is an automated field to determine if FMTC has found the coupon code on the deal’s landing page.
    • code_verified_at
      • This is the date that the code was verified by FMTC, shown in UTC.
    • link_verified_at
      • This is the date that the affiliate link was verified by FMTC, shown in UTC.
  • Field Mappings: The updated API provides clear mappings for input and output parameters across different versions, ensuring developers can easily adapt their integrations. For more information, you can reference the API Transition Documentation
  • Pagination: Efficient data navigation is made possible with pagination, allowing for better handling of large datasets.

This upgrade is not just a technical enhancement but also a strategic move to stay ahead in the competitive affiliate marketing space. By updating to v3, developers can enhance their current application’s capabilities and prepare for future advancements. As FMTC’s API continues to evolve, using the latest version ensures compatibility with new features and improvements, keeping your application at the forefront of affiliate marketing technology.

Enhancements for Developers

Delaying upgrades can lead to technical debt, accumulated inefficiencies, outdated code, and compatibility issues. v3 provides a clean slate, allowing everyone to build on a solid foundation. Many architectural and technical enhancements have been made to accelerate FMTC’s ability to add more updates to our system. It’s like renovating your house — addressing maintenance now prevents major overhauls later. 

Enhanced Performance

With the introduction of v3, developers can expect a boost in performance. The new version offers optimized data retrieval processes, ensuring faster response times and reduced server load. This translates to a more efficient and seamless experience when accessing deal and merchant information.

Changing from v1/v2 to v3 Endpoints

If you are currently using either of the previous endpoints from FMTC, our developers recommend following the instructions outlined in this document. The instructions provide a comprehensive overview of the new endpoint structure, including a proper mapping of all our fields. This way, you’ll have a clear understanding of where the data originates within the new structure.

Next Steps: Advanced Filtering

Even with the release of this new version, we have additional updates coming soon. The upcoming versions will introduce more advanced filtering options, specifically new deal types allowing users to tailor the data fetched to their specific needs. You will be able to filter out deals by content type (discount vs. non-discount), page type (homepage, clearance page, category pages, etc.), or even how the deal will be used (mobile app, in store, website, etc). Whether it’s deals active within a certain date range or merchant details by country, the new input parameters provide greater control over the API’s output. This level of customization ensures that applications can display the most relevant and up-to-date information.

As always, a dedicated team is here to assist you! If you have any questions or concerns, feel free to contact your account manager or email us at [email protected]. Curious about other FMTC technologies? Find more information on FMTC’s tools in Tech Corner:

Leave a Reply

Your email address will not be published. Required fields are marked *

Related Posts