Welcome to the ehouse API. This user guide has been created with developers in mind however it should also provide a guide to what is possible within our architecture. The concept of the API is to integrate existing ehouse relationships within either the end client platform or a third party software provision. When integrated API allows the end user a complete 'end to end' solution, never requiring human interaction with ehouse on any part of the order fulfillment process. They can place, amend and delete orders for the full variety of services ehouse offers, arrange appointment times for ehouse operatives to conduct the work, receive back the digital assets, all via the API. Future API features will contain the ability to create and amend brochures directly within the end user platform outside of the ehouse client extranet. We welcome comments and suggestions, please direct these to admin@ehouse.co.uk with 'API' in the subject line.
Security
API is only available to access via SSL, authentication and authorization will be done using bearer tokens. Users will need to send username and password to acquire a token which can be used to consume the API.Versioning
There are two types of versioning practice used in ehouse API
Major versions will be released under URL versioning
Minor versions within a major version will be released under custom header versioning