Updating managed object core data

Our API has predictable, resource-oriented URLs, and uses HTTP response codes to indicate API errors.We use built-in HTTP features, like HTTP authentication and HTTP verbs, which are understood by off-the-shelf HTTP clients.

updating managed object core data-63

is a platform for what Microsoft calls Data Services.

It is actually a combination of the runtime and a web service through which the services are exposed.

The web service can be configured to return the data in either plain XML, JSON or RDF XML.

In the initial release, formats like RSS and ATOM are not supported, though they may be in the future.

We support cross-origin resource sharing, allowing you to interact securely with our API from a client-side web application (though you should never expose your secret API key in any public website's client-side code).

JSON is returned by all API responses, including errors, although our API libraries convert responses to appropriate language-specific objects.

To make the API as explorable as possible, accounts have test mode and live mode API keys.

There is no "switch" for changing between modes, just use the appropriate key to perform a live or test transaction.

This is often useful for Connect applications that use multiple API keys during the lifetime of a process.

Authentication is transparently handled for you in subsequent method calls on the returned object.

Authenticate your account by including your secret key in API requests. Your API keys carry many privileges, so be sure to keep them secure!

Tags: , ,