API Overview: Difference between revisions

From Safe Creative API
Jump to navigation Jump to search
w>Jguillo
No edit summary
w>Jguillo
No edit summary
Line 1: Line 1:
= Introduction =
= Introduction =
Safe Creative API Web Services are accessible via a REST-like interface. The interface is rooted at <code><nowiki>http://api.safecreative.org/v2/</nowiki></code> unless you are using the arena server that lives in the arena subdomain: <code><nowiki>http://arena.safecreative.org/v2/</nowiki></code>.
Safe Creative API Web Services are accessible via a REST-like interface. The interface is rooted at <code><nowiki>http://api.safecreative.org/v2/</nowiki></code> unless you are using the arena server that lives in the arena subdomain: <code><nowiki>http://arena.safecreative.org/v2/</nowiki></code>.


All requests must be done using the UTF-8 charset (HTTP request charset should be UTF-8).
All requests must be done using the UTF-8 charset (HTTP request charset should be UTF-8).

Revision as of 15:46, 3 May 2010

Introduction

Safe Creative API Web Services are accessible via a REST-like interface. The interface is rooted at http://api.safecreative.org/v2/ unless you are using the arena server that lives in the arena subdomain: http://arena.safecreative.org/v2/.

All requests must be done using the UTF-8 charset (HTTP request charset should be UTF-8). Responses are formatted as UTF-8 XML. It is strongly recommended to use HTTPS instead of HTTP. Some methods are required to be called using HTTPS.


API functions reference

Generic methods

User management

Master tables

Works info

Work management

Multiauthorship

Search

How to

Troubleshooting