Difference between revisions of "API"
(→Event Forms) |
(→Event Forms) |
||
Line 181: | Line 181: | ||
Get Event Forms Details: | Get Event Forms Details: | ||
::[[API:EventForms:Details:Get|https://app.callproof.com/api/contact/event_form/details/get/]] | ::[[API:EventForms:Details:Get|https://app.callproof.com/api/contact/event_form/details/get/]] | ||
+ | |||
+ | Create Event Form: | ||
+ | ::[[API:EventForms:Contact:Create|https://app.callproof.com/api/contact/event_form/create/]] | ||
=== API Errors === | === API Errors === | ||
We followed standard errors from w3.org. A link is provided here: http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html | We followed standard errors from w3.org. A link is provided here: http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html |
Revision as of 13:33, 8 August 2017
Contents
API
The CallProof API can be used to automate backend workflows.
API Keys
API Ping
API Ping:
Reps
Update Reps Stats HTML:
Delete Reps Stats HTML:
Get Reps:
App Stats
Created Company Notes:
Update Company Stats HTML:
Delete Company Stats HTML:
Contacts
Created Contacts:
Updated Contacts:
Find Contacts:
Get Contact:
Update Contact:
Update Contact Reps:
Create Contact:
Delete Contact:
Update Contact Custom Fields:
Contact Phones
Get Updated Contact Phones:
Get Contact Phones:
Update Contact Phone:
Create Contact Phone:
Contact Notes
Get Contact Notes:
Update Contact Note:
Create Contact Note:
Delete Contact Note:
Calls
Created Calls:
Calls By ID:
Appointments
Updated Appointments:
New Appointment:
End Appointment:
Custom Fields
Get Custom Fields:
Update Custom Field:
Create Custom Field:
Update Custom Field Option:
Create Custom Field Option:
Companies
Create Companies:
Update Companies:
Delete Companies:
Opportunity
Get Opportunity Stages:
Get Opportunity Type:
Get Contact Opportunity:
Create Opportunity:
Followup
Updated Followup:
New Followup:
Event Forms
Get Event Forms:
Get Contact Event Forms:
Get Event Forms Details:
Create Event Form:
API Errors
We followed standard errors from w3.org. A link is provided here: http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html