Got feedback or spotted a mistake?

Leave a comment at the end of this page or email contact@krishagni.com

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 15 Next »

The purpose of this document is to explain the caTissue Plus REST APIs. The REST APIs will be consumed by the caTissue User Interface (built in backbone.js) as well as available for usage for integration with other systems, building plugins or building custom User Interfaces.

Common Characteristics of REST Resources

The following characteristics apply to all caTissue API resources:

  • You access a resource by sending an HTTP request to the caTissue server. The server replies with a response that either contains the data you requested or a status indicator, and in some cases both.
  • All resources are located at http[s]://<host-name>:<port>/catissuecore/rest.
  • You request a particular resource by appending a particular path to this base URL
  • All resources may return any of the below mentioned status codes:
codeApplies toStatus Message
200All resources 
201All POST/PUT requestsResource created/updated successfully
400All requestsInvalid parameters, this will also includes application specific error messages
401All requestsAuthorization failed
403All requests 
404All requestsResource not found, also includes specified resource id/name/title
500All requestsInternal server error

On this page, when a portion of a URL, path, or parameter value is shown in italics, it indicates that you should replace the italicized value with a particular value appropriate to your request.

Authentication

caTissue REST API's are signed requests, accessible to all the users who has access to caTissue application. To access the REST API's user need to pass their caTissue credentials by setting them in request Authorization header. The username/password should be encoded in base 64 encoding scheme.

 

Modules

 

 

 

  • No labels