meta data for this page
  •  

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
contacts [2023/09/14 15:00] – johnnycontacts [2023/12/24 15:33] (current) – [Contacts] Technical and billing contact portal permissions wrongecho
Line 1: Line 1:
 ====== Contacts ====== ====== Contacts ======
 +
 +Each of your customer have different key stakeholders that you may correspond with during the course of business. These stakeholders are considered Contacts within the ITFlow system. When a Contact within a Client record submits a ticket via email into your ITFlow system, the ticket is automatically assigned to the relevant Client based on the email contact of the Contact.
  
 Allow your clients to interact with the ITFlow portal by creating contacts. Allow your clients to interact with the ITFlow portal by creating contacts.
  
-{{::contacts-listing.png|}}+{{::contacts-listing.png?direct|}}
  
 You can record the following information about a client contact: You can record the following information about a client contact:
Line 10: Line 12:
   * Title   * Title
   * Mark as "important"   * Mark as "important"
-  * Mark as a technical / billing contact+  * Mark as a technical / billing contact - this also allows them to see technical and/or billing info in the client portal
   * Department   * Department
   * Phone / Extension / Mobile   * Phone / Extension / Mobile
Line 22: Line 24:
 /api/v1/contacts /api/v1/contacts
  
-**Read - Retrieve contact information (/read.php)**+==== Read - Retrieve contact information (/read.php) ==== 
  
   * **Default / No params - Returns all contacts**   * **Default / No params - Returns all contacts**
   * contact_id - Specific contact ID from the ITFlow database   * contact_id - Specific contact ID from the ITFlow database
   * contact_email - Specific contact via e-mail   * contact_email - Specific contact via e-mail
 +  * contact_phone_or_mobile - Specific contact via their mobile or office phone
  
 <code> <code>
-Invoke-RestMethod -Uri "http://127.0.0.1/itflow/api/v1/contacts/read.php?api_key=XetQjoZiti5Opg7y&contact_id=8" | ConvertTo-Json+Invoke-RestMethod -Uri "https://demo.itflow.org/api/v1/contacts/read.php?api_key=XetQjoZiti5Opg7y&contact_id=8" | ConvertTo-Json
  
 { {
Line 48: Line 52:
 </code> </code>
  
-**Create - Create a new contact (/create.php)**+==== Create - Create a new contact (/create.php) ==== 
  
 Specify all parameters as below, even if empty. E-mail must not already exist. The new contact ID will be returned. Specify all parameters as below, even if empty. E-mail must not already exist. The new contact ID will be returned.
Line 54: Line 59:
  
 <code> <code>
-$uri = "http://127.0.0.1/itflow/api/v1/contacts/create.php"+$uri = "https://demo.itflow.org/api/v1/contacts/create.php"
  
 $body = @" $body = @"
Line 85: Line 90:
 </code> </code>
  
-**Update - Update an new contact (/update.php)**+==== Update - Update an new contact (/update.php) ====
  
 Specify all parameters as below, even if empty. Same parameters as create endpoint, just additionally specify the contact_id to update. Specify all parameters as below, even if empty. Same parameters as create endpoint, just additionally specify the contact_id to update.
Line 92: Line 97:
 <code> <code>
  
-$uri = "http://127.0.0.1/itflow/api/v1/contacts/update.php"+$uri = "https://demo.itflow.org/api/v1/contacts/update.php"
  
 $body = @" $body = @"