Verify if an email exists before submitting SurveyAPI

Erik Leaver · August 2017

Hi, I'm asing this question on behalf of a client.

The client is working with an outside vendor on a paid acquisition campaign. The vendor can successfully add or update a constituent record using the CRSurveyAPI. However, the client only wants to add records that don't already exist in Luminate. Is there a way to check to see if an email address already exists in LO before submitting the survey? Ideally this would be done using a client side call but I'm guessing the call would need to be done via a server side call.

Thanks,

Erik Leaver

Brian Mucha · August 2017

Erik Leaver:

Hi, I'm asing this question on behalf of a client.

The client is working with an outside vendor on a paid acquisition campaign. The vendor can successfully add or update a constituent record using the CRSurveyAPI. However, the client only wants to add records that don't already exist in Luminate. Is there a way to check to see if an email address already exists in LO before submitting the survey? Ideally this would be done using a client side call but I'm guessing the call would need to be done via a server side call.

Thanks,

Erik Leaver

http://open.convio.com/api/#constituent_api.getUser_method.html

If called as a Client API, this method requires authentication. If the requester is an administrator (normally only the case using the Server API):

One of cons_id, member_id, or primary_email must be specified in order to locate the record.

Client or Server, but the logged in user has to be an admin.

Erik Leaver · August 2017

Thanks Brian. So glad we got to meet in Chicago at the summit last year!

I see in further down in the documentation that:

If the requester is a constituent using the Client API:

An authentication token representing the logged-in user must be passed.
Only the constituent record of the logged in user may be retrieved.

In this case we have the auth token representing the logged in user (which we need to submit the survey). shouldn't that allow us to see if a record exists?

08/28/2017 15:46:07 CDT HTTP status code 403 is not whitelisted (200, 201, 202, 203, 204, 205, 206, 300, 301, 302, 303, 304, 305 or 307). Will retry this lead. https://secure2.convio.net/XXXX/site/CRConsAPI;jsessionid=00000000.app202b?NONCE_TOKEN=86CAFFE8C848E3D9957ADBC737F5294C method=getUser&api_key=XXXXXXi&response_format=json&primary_email=dar%2B3%40gmail.com&v=1.0&auth=4spGAX4gdHMz7Nk31x3aKyQ9mDGi2q7D5jW3GAi1rKUNMYuJ2w5caFwZ0x_zRVNIW6rLEsTDHeU 403 (Forbidden) {"errorResponse":{"code":"14","message":"Get failed: getting a record is not allowed for the caller."}}

Time:

Error:

URL:

Request Body:

Response Code:

Response Body:

Cheers,

Erik

Brian Mucha · August 2017

Yes, but that doesn't account for someone ELSE using the email address in question.

Say I'm logged in as bmucha@luriechildrens.org. It would let me submit bmucha@google.com, even though I already have that address in use on a different account.

So using the user's creds would not be 100%, but maybe you could live with that so the whole thing could be easier.

Verify if an email exists before submitting SurveyAPI

Comments

Categories