...
| Code Block |
|---|
| title | Staff Web Service URL |
|---|
|
http://<domain>/connector/api/2011-11/staff |
Lead Sources
The Connector supports lead sources as well.
| Code Block |
|---|
| title | Lead Web Service URL |
|---|
|
http://<domain>/connector/api/2011-11/leadsource |
Save Lead Source
| Code Block |
|---|
| language | html/xml |
|---|
| title | Request |
|---|
|
<leadSource>
<providerInfo>
<identifier>INTOUCH</identifier>
<clientID>1111</clientID>
<clubID>11111111-1111-1111-1111-111111111111</clubID>
<recordID>FACEBOOK</recordID>
</providerInfo>
<leadInfo>
<name>Facebook</name>
<active>true</active>
</leadInfo>
</leadSource> |
| Code Block |
|---|
| language | html/xml |
|---|
| title | Response |
|---|
|
<response xmlns="http://www.intouchfollowup.com/api/2011-11">
<uuid>cf912bbd-7d10-41a5-b37e-1e11beff4e0c</uuid>
</response> |
Fetch Lead Source
TODO
URL: http://<domain>/connector/api/2011-11/leadsource?provider=PROVIDER_ID&identifier=FACEBOOK
Fetch Lead Sources
TODO
URL: http://<domain>/connector/api/2011-11/leadsource?provider=PROVIDER_ID&client_id=xxx&club_id=xxx
Errors
For those unfamiliar with ReSTful style web services, it is actually built on top of regular old HTTP. This means that (technically speaking) if you make a request to fetch a user and that user isn’t found you will actually get an HTTP response status of 404. I say technically speaking because the implementer of a web service doesn’t have to adhere to that. It is perfectly acceptable to give a normal HTTP response status of 200 and just have a different payload. All implementers need to be aware of how each web service works of course. Connector will be implemented in that if any type of real error occurred in the backend, an HTTP response code in the 400-599 range will be returned (these are the error codes).
...