Rest API vs client library

[SR]

Though it is recommended to use the client libraries, do we have any difference between REST API and client libraries in terms of feature support, error handling, performance etc. Please confirm.

Also let me know whether we can use REST API for creating search and display campaigns using batch job https://googleads.googleapis.com/v10/customers/{customerId}/batchJobs:mutate

[Google Ads API Forum Advisor]

Hi Sr,

Thank you for reaching out to the Google Ads API support team.

The REST interface directly without the use of a Google-supported client library. The REST API is useful if you are writing your own custom code to use REST directly or using a third-party HTTP client library. We strongly recommend using our official client libraries wherever you can. All Google provided client libraries are implemented using gRPC, except for the Perl library, which uses the REST interface.  Yes, you can user REST interface for mutate operation. Let me know If you have any question.

Thanks,

Nirmita Google Ads API Team

ref:_00D1U1174p._5004Q2ZJT3Q:ref

[SR]

Thanks for your response.

Could you please explain in detail on why you strongly recommend client libraries? 

Are there any functionalities that are not supported in Rest API?

Will there be any performance issues with Rest API?

[Google Ads API Forum Advisor]

Hi Sr,

Thank you for reaching out.

Client libraries provide idiomatic, type-safe code in each supported language and handle many low-level details of communication with the API (like timeout settings, result set pagination, and authentication). Our client libraries also include an extensive set of code examples and utilities that assist with common tasks, such as constructing resource names and handling field masks. There is no performance issue with Rest API. You may refer to this guide. Let me know if you have any question.