1. REST API for Oracle Eloqua Marketing Cloud Service
  2. Tasks
  3. Bulk
  4. 2.0
  5. activities

Create an activity export definition

post

/api/bulk/2.0/activities/exports

Creates a new activity export definition. After a successful request, the next step is to synchronize the data. See the tutorial for details on how to export data.

Request

Supported Media Types
Body ()
The request body contains details of the activity export definition.
Root Schema : ActivityExportIndividual
Type: object
Title: ActivityExportIndividual
The request body defines the details of the activity export definition.
Show Source
  • Title: areSystemTimestampsInUTC
    Whether or not system timestamps will be exported in UTC. See Filtering tutorial for an example of filtering when areSystemTimestampsInUTC is set to true.
  • Title: autoDeleteDuration
    Time until the definition will be deleted, expressed using the ISO-8601 standard.
  • Title: createdAt
    The date and time the entity was created, expressed using the ISO-8601 standard. This is a read-only property.
  • Title: createdBy
    The login id of the user who created the entity. This is a read-only property.
  • Title: crmAccountIdField
    The ML statement for an existing contact field which addresses the CRM account ID.
  • Title: dataRetentionDuration
    The length of time exported data should remain in the staging area. Bulk API 2.0 uses the ISO-8601 standard for specifying all durations. Valid values are anything from PT1H (1 hour) to P14D (2 weeks). This setting will default to PT12H (12 hours) if not explicitly set during export definition creation.
  • Title: externalSystemId
    The external system ID is used when exporting data containing CRM fields.
  • fields
    Title: fields
    List of fields to be included in the operation.
  • Title: filter
    The filter parameter uses Eloqua Markup Language to only return certain results. Learn more about filters.
  • Title: kbUsed
    The amount of space used in kilobytes. This is a read-only property.
  • Title: maxRecords
    The maximum amount of records.
  • Title: name
    The name of the export definition.
  • Title: productIdField
    The ML statement for an existing campaign field which addresses the product ID.
  • Title: updatedAt
    The date and time the entity was last updated, expressed using the ISO-8601 standard. This is a read-only property.
  • Title: updatedBy
    The login id of the user that last updated the entity. This is a read-only property.
  • Title: uri
    System-generated unique resource identifier that defines the definition for future referencing. This is a read-only property.
Nested Schema : fields
Type: object
Title: fields
List of fields to be included in the operation.
Back to Top

Response

Supported Media Types

201 Response

Success.
Body ()
Root Schema : ActivityExportIndividualResponse
Type: object
Title: ActivityExportIndividualResponse
The response body includes information about the activity export definition.
Show Source
  • Title: areSystemTimestampsInUTC
    Whether or not system timestamps will be exported in UTC. See Filtering tutorial for an example of filtering when areSystemTimestampsInUTC is set to true.
  • Title: autoDeleteDuration
    Time until the definition will be deleted, expressed using the ISO-8601 standard.
  • Title: createdAt
    The date and time the entity was created, expressed using the ISO-8601 standard. This is a read-only property.
  • Title: createdBy
    The login id of the user who created the entity. This is a read-only property.
  • Title: crmAccountIdField
    The ML statement for an existing contact field which addresses the CRM account ID.
  • Title: dataRetentionDuration
    The length of time exported data should remain in the staging area. Bulk API 2.0 uses the ISO-8601 standard for specifying all durations. Valid values are anything from PT1H (1 hour) to P14D (2 weeks). This setting will default to PT12H (12 hours) if not explicitly set during export definition creation.
  • Title: externalSystemId
    The external system ID is used when exporting data containing CRM fields.
  • fields
    Title: fields
    List of fields to be included in the operation.
  • Title: filter
    The filter parameter uses Eloqua Markup Language to only return certain results. Learn more about filters.
  • Title: kbUsed
    The amount of space used in kilobytes. This is a read-only property.
  • Title: maxRecords
    The maximum amount of records.
  • Title: name
    The name of the export definition.
  • Title: productIdField
    The ML statement for an existing campaign field which addresses the product ID.
  • Title: updatedAt
    The date and time the entity was last updated, expressed using the ISO-8601 standard. This is a read-only property.
  • Title: updatedBy
    The login id of the user that last updated the entity. This is a read-only property.
  • Title: uri
    System-generated unique resource identifier that defines the definition for future referencing. This is a read-only property.
Nested Schema : fields
Type: object
Title: fields
List of fields to be included in the operation.

400 Response

Bad request. See Status Codes for information about other possible HTTP status codes.

401 Response

Unauthorized. See Status Codes for information about other possible HTTP status codes.

403 Response

Forbidden. See Status Codes for information about other possible HTTP status codes.

404 Response

The requested resource was not found. See Status Codes for information about other possible HTTP status codes.

409 Response

There was a conflict. See Status Codes for information about other possible HTTP status codes.

410 Response

The requested resource is no longer available. See Status Codes for information about other possible HTTP status codes.

412 Response

The resource you are attempting to delete has dependencies, and cannot be deleted. See Status Codes for information about other possible HTTP status codes.

413 Response

Storage space exceeded. See Status Codes for information about other possible HTTP status codes.

500 Response

The service has encountered an internal server error. See Status Codes for information about other possible HTTP status codes.

503 Response

There was a timeout processing the request. See Status Codes for information about other possible HTTP status codes.
Back to Top

Examples

The following examples demonstrate how to create a new activity export definition using an HTTP request and cURL. For more information on requests, see API requests. See the tutorial for details on how to export data.

HTTP Request Example

Create a new activity export definition:


POST /activities/exports
Content-Type: application/json

Request body:


{
   "name":"Form submit activity id export",
   "fields":{
      "ActivityId":"{{Activity.Id}}"
   },
   "filter":"'{{Activity.Type}}'='FormSubmit'"
}

Response:


{
    "name":"Form submit activity id export",
    "fields":{
        "ActivityId":"{{Activity.Type}}"
    },
    "filter":"'{{Activity.Type}}'='FormSubmit'",
    "dataRetentionDuration":"PT12H",
    "id":"/activities/exports/29386",
    "createdBy":"API.User",
    "createdAt":"2015-08-17T19:08:29.2772694Z",
    "updatedBy":"API.User",
    "updatedAt":"2015-08-17T19:08:29.2772694Z"
}

cURL Example

Here is the same example in cURL given an instance with the name APITest, username API.User, and POD of 3. 


curl --user "APITest\API.User" --header "Content-Type: application/json" --request POST --data '{"name":"Form submit activity id export","fields":{"ActivityId":"{{Activity.Id}}"},"filter":"'{{Activity.Type}}'='FormSubmit'"}' https://secure.p03.eloqua.com/api/bulk/2.0/activities/exports
Back to Top