Using Client Libraries
Integrate the Apple Ads Platform API using an Apple-maintained client library instead of a custom HTTP client.
Overview
Writing your own integration means owning retry logic, response parsing, and model definitions for every endpoint you call, and keeping all of it correct as the API evolves. A client library takes on that maintenance burden for you, letting your team focus on campaign logic instead of plumbing.
Apple distributes each library through standard, language-specific means, and maintains and versions it alongside the Apple Ads Platform API, so new endpoints, fields, and enumeration values become available through routine dependency updates rather than manual rework. The libraries also handle the OAuth token lifecycle, including requesting and refreshing access tokens, so your application code can focus on calling endpoints rather than managing credentials. Sensible defaults get you running quickly, and extension points let you adapt request handling, logging, and credential management to fit how you built your application.
Select a Library
Choose the library that matches your application’s language:
Language | Repository |
|---|---|
Swift | |
Python | |
Java | |
Node.js |
Get Started
To generate the credentials your application authenticates with, complete the setup steps in Implementing OAuth for the Apple Ads Platform API before integrating a client library. Each repository includes a README with installation instructions, authentication setup, and usage examples specific to that language. To install the library and construct a client, refer to the README for your library’s language. For details on the underlying request and response structures the libraries wrap, see Calling the Apple Ads Platform API.