Connector Improvement: API response to match API parameters
For many of the GET connector details responses the result produces values in the JSON that are not acceptable when sent to the PATCH endpoint.
For a Facebook Ads connector for example, the API returns
"sync_mode": "SPECIFIC_ACCOUNTS"
but when making a PATCH request the response is
"code": "InvalidInput",
"message": "Invalid config object. (Cannot deserialize value of type `com.fivetran.integrations.facebook.common.model.SyncMode` from String \"SPECIFIC_ACCOUNTS\": not one of the values accepted for Enum class: [SpecificAccounts, AllAccounts]\n at [Source: UNKNOWN; line: -1, column: -1] (through reference chain: com.fivetran.integrations.facebook.ads.FacebookAdsCredentialsPatch[\"sync_mode\"]))"
I see the same thing for many values and it is easy enough to change from a user side, but frustrating that the values output by the API are not the same ones it consumes.
-
Official comment
Hey James,
Apologies for the late reply here, but we were unable to reproduce this. Could you send up a support ticket with the exact sequence of API calls you made (with full URIs) so we can attempt to debug/try and reproduce?
Jimmy
Please sign in to leave a comment.
Comments
1 comment