CRM Glennis Standard Lead API

An API that will accept inquirer referrals.


Authentication

When making API calls to CRMLead API, each request requires a JWT token in the 'Bearer' header.

Example:


            $.ajax({
              url: "https://dev-saas.atriacom.com/crmlead/api/lead",
              type: 'POST',
              contentType: "application/json",
              data: JSON.stringify(new Object()),
              headers: {"Authorization": 'Bearer ' + my_jwt_token}
            });

Authenticated JWT Token

To get a token, send a Basic user credential to the Token endpoint. The JWT Token does have an expiration, so you can re-use it until it expires. Be sure to keep your token and credential secure!

Example:


            $.ajax({
              url: "https://dev-saas.atriacom.com/crmlead/api/token",
              type: 'POST',
              headers: {"Authorization": 'Basic ' + btoa(username + ':' + password)}
            });

Error

The API uses HTTP response codes to indicate the success or failure of an API request. Codes in the 2xx range indicate success. Codes in the 4xx range indicate client input failed requirement (e.g. missing a required parameter). Codes in the 5xx range indicate server error.

Examples:

  • 200 - Ok -Everything worked as expected.
  • 400 - Bad Request - Often request missing inputs/validation.
  • 401 - Unauthorized - Missing or invalid credential.
  • 403 - Forbidden - Credential does not have the right permission.
  • 404 - Not Found - The requested source does not exist.
  • 415 - Unsupported Media Type - The requested need to specify 'appication/json'.
  • 500 - Server Errors - Something went wrong on CRMLead API.

Resources

Available Endpoints:


           POST - https://dev-saas.atriacom.com/crmlead/api/lead
           POST - https://dev-saas.atriacom.com/crmlead/api/token