The newest version of the API, v201203, is at your service. It includes a brand new
testing environment, read-only access to video creatives, team level filtering, and more. A full list of features can be found on our
release notes page.
Test networks
Starting in v201203, you’ll be able to create
test networks, which offer a wider range of functionality than the existing sandbox networks. To create test networks, you'll need a
new Google account. Once you’ve called
NetworkService.makeTestNetwork() with that account, you’ll sign in to test networks the
same way as production, without having to sign up for a DFP account. Additionally, all SOAP requests can now be sent to https://www.google.com instead of https://sandbox.google.com; moving from test networks to production now will only require you to change your network code. Stay tuned for an upcoming blog post in which we will detail how to use these new networks and our plans for the legacy sandbox environment.
Network codes
In the previous versions,
network codes were only required if you belonged to more than one network. Beginning in v201203, network codes will now be required for all requests except
NetworkService.getAllNetworks() and
NetworkService.makeTestNetwork(). This change will reduce latency for some requests and will make it easier for you to keep track of which requests are going to which networks, especially now that test and production networks have the same domain for requests.
Video creatives
Video creatives are now read-only accessible through the CreativeService. We plan to expose more functionality going forward, but we understand the current need of publishers and 3rd parties to report on and analyze what creatives exist in their network. Look out for more work coming in this area.
Teams
v201201 introduced teams and,
as we mentioned, promised future functionality of filtering objects by those teams. In v201203, you’ll be able to set team IDs on
inventory,
orders, and
company. Then, when calls are made with that user, only objects that belong to their team will be returned. You will also receive an error if you attempt to update an object that you don’t have access to.
Stay tuned for upcoming blog posts on the new test networks and network service best practices. As always, let us know if you want to see any new features or blog posts on our
forum.
-
Adam Rogal, DFP API Team
