Bidder location URL with HTTPS cannot be updated

56 views
Skip to first unread message

Gabor Mate

unread,
Feb 19, 2015, 5:20:38 AM2/19/15
to google-doubleclick-a...@googlegroups.com
We are in the process to transition our end points to the HTTPS protocol. Our TAM has set up a second bidder location on the US_EAST region with a secure URL and now I'm trying to update the QPS on that location. Unfortunately I am getting the following error:

'Error calling PATCH https://www.googleapis.com/adexchangebuyer/v1.3/accounts/12345678: (400) The bidder url is invalid.'

Here is the body of the of the PATCH request:

{"bidderLocation":[{"maximumQps":5000,"region":"EUROPE","url":"http:\/\/rtbeu.something.com"},{"maximumQps":7500,"region":"US_WEST","url":"http:\/\/rtbwest.something.com"},{"maximumQps":10000,"region":"US_EAST","url":"http:\/\/rtbeast.something.com"},{"maximumQps":499,"region":"US_EAST","url":"https:\/\/rtb-ssl.something.com"}]}

On any other seats where we don't have https url yet the PATCH call works correctly.

Am I doing something wrong or https URLs are not supported yet in the API? Any workaround? Right now we cannot adjust the QPS at all for this seat as the call always fails.

Thnx.

Gabor

Mark Saniscalchi

unread,
Feb 19, 2015, 12:43:10 PM2/19/15
to google-doubleclick-a...@googlegroups.com
Hello Gabor,

I've reproduced the issue and have been in contact with the engineering team. The bidderLocation url field doesn't allow urls containing "https://" yet, although we'll be rolling out an update next week that will allow you to do this.

Regards,
Mark Saniscalchi

Gabor Mate

unread,
Feb 20, 2015, 1:45:34 AM2/20/15
to google-doubleclick-a...@googlegroups.com
Thank you Mark, will confirm here next week how it worked.

Gabor
Reply all
Reply to author
Forward
0 new messages