Facebook Ads Scraper avatar

Facebook Ads Scraper

Try for free

Pay $5.00 for 1,000 Campaigns

View all Actors
Facebook Ads Scraper

Facebook Ads Scraper

apify/facebook-ads-scraper
Try for free

Pay $5.00 for 1,000 Campaigns

Extract advertising data from one or multiple Facebook Pages. Get page details, reach estimates, publisher platforms, report count, number of impressions, ad IDs, timestamps, and more. Download Facebook ads data in JSON, CSV, and Excel and use it in apps, spreadsheets, and reports.

Do you want to learn more about this Actor?

Get a demo
CH

Inconsistent Field Naming in API Responses (Snake_case to CamelCase)

Closed

checkoutclub opened this issue
a month ago

Dear APIFY Support Team,

I hope this message finds you well. I have encountered an issue with the API responses that has caused significant disruptions in my workflow.

Yesterday, the API was returning fields using underscores as separators (e.g., page_profile_picture_url, video_hd_url). However, today, I noticed that the naming convention has changed to camelCase (e.g., pageProfilePictureUrl, videoHdUrl). Below are some examples of the changes:

page_profile_picture_url -> pageProfilePictureUrl display-format -> displayFormat .ad_library_page_info.page_info.page_verification -> pageInfo.adLibraryPageInfo.pageInfo.pageVerification original_image_url -> originalImageUrl video_hd_url -> videoHdUrl link_description -> linkDescription

I had previously adjusted my code to accommodate the snake_case format, but with this sudden change to camelCase, I have experienced numerous errors. Although I have updated my code to handle the new format, I would like to understand what the final field naming convention will be.

Are there ongoing changes to the API, and when can we expect a stable version with a consistent field naming standard to avoid further code breaks?

Your assistance in clarifying this would be greatly appreciated.

Thank you in advance for your support.

jakubkonecny avatar

Hello, we have decided to go with changing the response that Meta API gives us, which was snakecase, to camelcase, so it matches with the rest of Apify Meta actors and their workflows. We are sorry that we caused any workflow troubles, and this is most likely the final version of naming conventions for this actor for the foreseeable future. Thank you for your feedback :)

Developer
Maintained by Apify
Actor metrics
  • 333 monthly users
  • 43 stars
  • 100.0% runs succeeded
  • 5 days response time
  • Created in Apr 2023
  • Modified 1 day ago