• Overview

  • Getting Started Guide
  • Rationale for Existence
  • Authentication
  • Key Concepts
  • Technical Notes
  • For All Calls

• Resources

  • customers
  • users
  • people
  • documents
  • locations
  • companies
  • schools

• Objects

  • Customer
  • User
  • Person
  • Document
  • Location
  • Company
  • School
  • Search Results

Technical Notes

• The Knodes API adheres to REST principles.

• All parameters are passed as arguments to a appropriate HTTP method (GET, POST, PUT, or DELETE)

• HTTP status codes are used as the return code.

• There is no custom envelope data, all data is returned as JSON in the response body.

• All calls must be made over HTTPS.

• Congruent with HATEOAS, each resource contains a "links" array that contains both the absolute link to the current entity (rel="self") and to associated aspects of the entity.