Data access calls can be made from server-side code, providing you with access to granular features and data. Using RESTful commands, your data can be created, retrieved, updated, or deleted programmatically. The response from these calls is XML.

CellService Calls for retrieving, editing, and moderating content cells. FeedService Calls to subscribe to RSS Feeds containing activity reports. ImageService Calls to upload images. ReportService Calls to fetch reports. TagService Calls for retrieving, editing, and using tags. TemplateService Calls for retrieving and managing templates. UserService Calls to manage user data, sessions, and permission levels. NamespaceService Calls to manage namespaces associated with a developer key. DiscussionService Calls for retrieving, and managing discussion threads.

Common Request Parameters These common parameters are required on many data access calls. Structured Data Output The responses from Injected follow a structured format.

Calls on Behalf of Users

Most calls to the data access API will be made on behalf of an end user. For example, the following types of calls provide access control appropriate to the signed in state and level of permissions of a user: retrieve and edit content, retrieve reputation data associated with a user account, or interact with Wetpaint's social feature set. A small number of API calls, such as to authenticate users, will be system-level calls. Such calls must be made from your server and require additional security parameters.

Post Calls Require Content Length

When making POST calls, the HTTP content length must be specified. Most development platforms (PHP, ASP.net, JScript) do this for you, but in special cases, you may need to do this manually. Calls that include the parameters on the query string should have a content length set set to zero. If your POST parameters are included in the HTTP request body, then the content length should be set to the total size of the content packet.

Example of setting content length in php:

<?php

header("Content-Length: 0");
?>