URGENT: 404 Error connecting to API

[GoogleCodeExporter]

---------------------------------------------------------------------------
NOTE: This issue tracking system is for Google Analytics developer products
only.
If you are not a developer/programmer visit:
http://www.google.com/analytics/support.html
---------------------------------------------------------------------------
Name of affected component: Core Reporting API

Name of related library and version, if applicable (e.g. Java, Python,
HTTP, Objective-C, etc.): ASP.NET C#

Issue summary:
All calls to the API return "The remote server returned an error: (404) Not 
Found.". This started last night and continues today. It has been working 
perfectly for months before this.

Steps to reproduce issue:
1. Make an API call.

Expected output:
Returned data.

Actual results:
404 Error

Original issue reported on code.google.com by amo...@gmail.com on 27 May 2015 at 5:59

[GoogleCodeExporter]

Cannot reproduce and there are not enough details in the report. Also, this is 
likely an implementation issue and not a bug or feature request. You should ask 
for help in the Reporting API forums:
https://groups.google.com/forum/?fromgroups#!forum/google-analytics-data-export-
api

Original comment by pfrise...@google.com on 27 May 2015 at 1:22

• Changed state: Invalid

[GoogleCodeExporter]

This is not an implementation issue unless something has changed in the API.  
It is happening on ALL 30+ of our client sites and has been working perfectly 
without modification for months now.

Original comment by amo...@gmail.com on 27 May 2015 at 1:24

[GoogleCodeExporter]

What authentication method are you using?

Original comment by pfrise...@google.com on 27 May 2015 at 1:27

[GoogleCodeExporter]

I suspect this has to do with the deprecation of the API ClientLogin method as 
other people are complaining about the same thing having started last night...
In case you are in the same boat, here is a reference to the note which was 
obviously only implemented last night and not on the 20th of April.

Important: ClientLogin has been officially deprecated as of April 20, 2012 and 
is no longer available as per our deprecation policy. We encourage you to 
migrate to OAuth 2.0 as soon as possible.

Original comment by amo...@gmail.com on 27 May 2015 at 1:42