Skip navigation

Code It

3 Posts authored by: ta*2639084*im

1) (optional) Initiate a Get inquiry to get Site ID, site name, URIs, and user details

     URI to initiate the action GET https://login.eloqua.com/id

       9-19-2013 6-04-21 PM.png

Response as it appears in Fiddler - JSON format:
9-19-2013 6-06-03 PM.png

2) Initiate a POST request to create an Export definition:

URI to initiate the export: POST https://secure.eloqua.com/API/Bulk/1.0/contact/export?format=json
This time you have to provide the details of the fields and the data that you want to include in the export:

This could look something like this:

{"name":"Tarek.Naim",

"fields":{"ID":"{{Contact.Id}}",

"filter":{"filterRule":"VALUEEQUALSCOMPARISONVALUE",

"value":"{{Contact.Field(C_EmailAddress)}}","comparisonValue":"tarek.naim@oracle.com"},

  "secondsToRetainData":

14400,"secondsToAutoDelete":14400,"kbUsed":0}

9-19-2013 6-10-55 PM.png


Response status should be 201 and should look something like:

9-19-2013 6-19-57 PM.png



3) Initiate a POST request to create a SYNC

POST https://secure.eloqua.com/API/Bulk/1.0/sync

Request Body: {"syncedInstanceUri":"/contact/export/14"}

9-19-2013 6-27-12 PM.png

Response would look something like this:

9-19-2013 6-27-01 PM.png
4) You can Poll the sync to make sure it's been created successfully:

URI: https://secure.eloqua.com/API/Bulk/1.0/sync/syncID

9-19-2013 6-29-25 PM.png
Response should indicate a success status

9-19-2013 6-29-51 PM.png


5) Initiate a Get request to get the data from the staging area:

GET https://secure.eloqua.com/API/Bulk/1.0/contact/export/EPORTID/data?page=1&pageSize=10&format=json

Response would show the data in the staging area

To ensure a faster resolution time on API related cases that get submitted to Eloqua support, it would be helpful if you can provide the following information when you first submit the case:

1) An explanation of the use-case or business objective and end goals that you're hoping to achieve using API.

Eg: You might want to import data from an external system to Eloqua. It would be helpful to touch on why you want to bring the data to Eloqua and what you want to do with it. Again, this is all on a high-level to help us understand your use-case and keep it in mind as we're devising technical solutions.

 

2) Whenever possible, try to determine if the issue is an API issue or whether the API is just bringing the issue to the surface.

Eg: You're importing data cards to Eloqua through API but the datacards services are not running. It would be helpful to see if you can create a data card manually directly through the App and see if the datacard services run. If they don't, then this would confirm that the issue is not API related.

 

3) Once you think that the issue is API related, the two most important pieces of information are the REQUEST AND RESPONSE header and bodies. What we're interested in here is not so much your Java or C# code that's executing the API calls but rather the API request that gets sent to Eloqua as a result of the code execution - or whatever method you're using to execute these API calls. One good way to get that request header and body is to run a web tool called Fiddler that would allow you to monitor the traffic on your computer -- including the API calls. You can drag and drop a call from the left side of the window to the composer tab and see the Request header and body. You can also monitor the response header and body that way too. Another tool that can be helpful too is Firebug which is an add-on on firefox. The response code result -- 200, 400, 403, along with the exact message are very important as well.

8-14-2013 2-03-12 PM.png

 

4) It's also important for support to have an understanding of: How long has the issue been occurring for? When did it start? Is it intermittent or does it occur all the time? When was the last time that the client you were able -- if ever, to run a similar request successfully?

 

5) Please provide us with a sense of the business impact that this issue is having on your operations

 

6) For authentication/privileges issues, ensure that the user has the API security Group and that the credentials are valid. You can verify whether the credentials are valid by attempting to login to the application -- using the API user credentials, the same way any Eloqua user would.

 

With all this information provided in the case, you will ensure that your case gets routed quickly to the appropriate resources at the support team and get the attention and action needed in a timely manner.

Thanks,

Tarek

The table below shows the limits for different methods of importing/uploading data to Eloqua

Upload/Import TypeSize allowed
REST API 1.0500MB
BULK API32MB -- pages, or 50k records
SOAP API64MB -- RAW envelope size limit, no file size limit
Data Cards Upload Wizard500MB
Contact file Upload Wizard500MB
SFTP/FTP based AutosynchsNo Limit
Autosynchs - Get Contacts, etc..No Limit
Content upload - PDF Document, files10MB
Images50MB
Call Script, Fax Document, Call Center Batch -- Only applicable to E910MB
HTML Content for Landing Pages10MB

Notice from the table above that all wizard-based uploads have a limit of 500MB

Filter Blog

By date: By tag: