| Feature Type: |
| |
| New Feature |
| |
| Anticipated Launch Date: |
| |
| February 2006 |
| |
| Developer Impact: |
| |
| This report can be used by any developer who has a production application and is making production API calls within the past 6 months. Note: Although the report will store up to 6 months of data from today's date, special data tables were created for this report and the earliest data available is from January 28, 2006. |
| |
| Feature Description: |
| |
|
The API Usage Report displays production API calls by application for each developer. Sandbox calls will be viewable in the next release of the product. |
| |
| Developers will select a timeframe within the past 6 month period as well as the application they want to monitor. A summary section provides the percentage of API calls that failed, percentage of calls in legacy schema, percentage of calls not compliant with the minimum recommended compatibility level as well as notify the user if they are subscribed to Notifications in legacy schema. The body of the report is split into 2 sections: 1 for unified schema calls and one for legacy schema calls. The API calls are displayed by Function Name, #Successful, #Failed, and #Not Compliant with the minimum compatibility level. You can see your production calls after 10 minutes of the calls execution/data return. |
| |
| This project will enable developers to monitor almost real time their application activity and view progress toward schema migration.
|
| |
| Feature Benefits: |
| |
| This report will help eBay Developers monitor and evaluate the performance of their applications as well as see when the application is close to their application API call limit |
| |
|
**Update-Important Additional Information**
|
| |
| REST API |
| |
| We have found a bug in the API Usage Report where REST API developers using unified schema will incorrectly be informed that their calls are still "legacy". We are working on a fix for this now and anticipate the fix to be released by end of Feb 2006 for US and mid March 2006 for international. |
| |
| REST API developers who are still using the legacy REST API can update the REST output to unfied schema by passing "Schema=1" in the query string of their REST call and modifying the application to handle the new output. For more information on using unified schema in REST, see our REST API Documentation. |
| |
| Authentication Token Tool |
| |
| For developers using the Authentication Token Tool , you will have 2 calls displayed on the API Usage report as legacy calls:
SetReturnURL and GetUser for each token generated by the Tool. We are scheduled to migrate the API used by Authentication Token Tool by May 2006. |
| |
