Hey everyone Did anyone experienced success with t...
# singer-taps
s
Hey everyone Did anyone experienced success with tap-linkedin-ads ! , I cloned https://github.com/MeltanoLabs/tap-linkedin-ads/tree/main and configured with required details like acess_token,accounts,campaign,campaign_group,creative etc in meltano.yml but there is some issue with tap as attached meltano.yml as below version: 1 default_environment: dev send_anonymous_usage_stats: true project_id: linkedin_sdk plugins: extractors: - name: tap-linkedin-ads namespace: tap_linkedin_ads pip_url: -e . capabilities: - state - catalog - discover settings: - name: access_token kind: password sensitive: true - name: accounts - name: user_agent value: meltano - name: campaign - name: owner - name: campaign_group - name: creative - name: start_date value: '2023-01-01T000000Z' - name: end_date value: '2023-04-01T000000Z' config: accounts: access_token: owner: campaign: campaign_group: creative: start_date: '2020-05-01' end_date: '2024-06-28' - name: Linkedin-Accounts inherit_from: tap-linkedin-ads select: - accounts
👀 1
r
Look like the API version the tap is using is now sunset. I would open an issue on the tap.
Since you have a local copy, you can try updating the API version and see if it works.
s
Thank you Reuben. I changed version to latest 202406 [random ] and throws different error code 400 2024-07-24T130445.943568Z [info ] singer_sdk.exceptions.FatalAPIError: 400 Client Error: Bad Request for path: /rest/adAccounts cmd_type=elb consumer=False job_name=dev:tap-l inkedin-ads-to-target-jsonl name=tap-linkedin-ads producer=True run_id=66762166-9bb6-4bee-8733-500769755f77 stdio=stderr string_id=tap-linkedin-ads 2024-07-24T130446.038859Z [info ] Incremental state has been updated at 2024-07-24 130446.038859. any help here - Thank you
r
Difficult to say without seeing the full response. I would recommend making the same request with
curl
that the tap is making here and see what you get. Alternatively, you can (temporarily) add a logging statement in the tap to print out the response body in
parse_response
. These are the
202406
docs for the
/adAccounts
endpoint: https://learn.microsoft.com/en-us/linkedin/marketing/integrations/ads/account-structure/create-and-manage-accounts?view=li-lms-2024-06&tabs=http#search-for-accounts > From 202401 version and above, we have moved from index based pagination to cursor based pagination for our search APIs. Also, you might need to update
X-Restli-Protocol-Version
here, as per > The Rest.li 2.0.0 syntax is required for most calls to
/adAccounts
. Include the header
X-RestLi-Protocol-Version: 2.0.0
in your request. I suspect other endpoints might be affected too.
👍 1