Export
Config

Rate this page:

Config

Get current export path

GET /config/export-path

Return the current export path. This is the directory that the data pipeline will write files to.

In the examples below, substitute https://your-domain.atlassian.net/ with the Data Center URL https://myexamplesite.com/rest/datapipeline/latest/ where myexamplesite is your domain. Remember to include your context path if you have one configured.

Request

There are no parameters for this request.

Example

1
2
3
curl --request GET \
  --url 'https://your-domain.atlassian.net/config/export-path' \
  --header 'Accept: application/json'

Responses

Returns the current export path.

Content typeValue
application/json

ConfigExportPathRequest

Change export path

PUT /config/export-path

Create or update a custom export path. This is the directory that the data pipeline will write files to.

In the body of the request pass the absolute path to your preferred directory, for example:

1
2
3
{
  "path": "/tmp/new/path"
}

In the examples below, substitute https://your-domain.atlassian.net/ with the Data Center URL https://myexamplesite.com/rest/datapipeline/latest/ where myexamplesite is your domain. Remember to include your context path if you have one configured.

Request

There are no parameters for this request.

Example

1
2
3
curl --request PUT \
  --url 'https://your-domain.atlassian.net/config/export-path' \
  --header 'Accept: application/json'

Responses

Returns details of the updated export path.

Content typeValue
application/json

ConfigExportPathRequest

Revert to default export path

DELETE /config/export-path

Delete the custom export path and revert to the default path. This is the path that the data pipeline will export files to.

In the examples below, substitute https://your-domain.atlassian.net/ with the Data Center URL https://myexamplesite.com/rest/datapipeline/latest/ where myexamplesite is your domain. Remember to include your context path if you have one configured.

Request

There are no parameters for this request.

Example

1
2
3
curl --request DELETE \
  --url 'https://your-domain.atlassian.net/config/export-path' \
  --header 'Accept: application/json'

Responses

Returns the updated export path.

Content typeValue
application/json

ConfigExportPathRequest

Get current export schedule

GET /config/schedule

Administrators can schedule regular exports. Get the details of the current export schedule, if a schedule exists.

In the examples below, substitute https://your-domain.atlassian.net/ with the Data Center URL https://myexamplesite.com/rest/datapipeline/latest/ where myexamplesite is your domain. Remember to include your context path if you have one configured.

Request

There are no parameters for this request.

Example

1
2
3
curl --request GET \
  --url 'https://your-domain.atlassian.net/config/schedule' \
  --header 'Accept: application/json'

Responses

Returns details of the current export schedule if a schedule exists. Returns an empty response if a schedule does not exist.

Content typeValue
application/json

ConfigExportScheduleResponse

Create or update export schedule

PUT /config/schedule

Administrators can schedule regular exports. Create a new export schedule or update the current export schedule.

In the body of the request pass the date and time intervals and export parameters, as follows:

1
2
3
4
5
6
7
{
 "days": ["sun", "tue"],
 "time": "00:00:00",
 "repeatIntervalInWeeks": 3,
 "fromDate": "2020-07-26T11:14:00Z",
 "schemaVersion": 2
}

In the examples below, substitute https://your-domain.atlassian.net/ with the Data Center URL https://myexamplesite.com/rest/datapipeline/latest/ where myexamplesite is your domain. Remember to include your context path if you have one configured.

Request

There are no parameters for this request.

Example

1
2
curl --request PUT \
  --url 'https://your-domain.atlassian.net/config/schedule'

Responses

Returns confirmation that the request to create schedule has been received.

A schema has not been defined for this response code.

Delete export schedule

DELETE /config/schedule

Turn off scheduled exports, and delete the current export schedule.

In the examples below, substitute https://your-domain.atlassian.net/ with the Data Center URL https://myexamplesite.com/rest/datapipeline/latest/ where myexamplesite is your domain. Remember to include your context path if you have one configured.

Request

There are no parameters for this request.

Example

1
2
curl --request DELETE \
  --url 'https://your-domain.atlassian.net/config/schedule'

Responses

Returns confirmation that the schedule was succesfully deleted, if a schedule exists.

A schema has not been defined for this response code.

Get schema versions

GET /config/schema

Get a list of all supported schema versions.

The export schema defines the structure of the export. We only introduce new schema versions for breaking changes, such as removing a field, or if the way the data is structured changes. New fields are simply added to the latest schema version. Older schema versions will be marked as deprecated, and may be removed in future versions. You can still export using these versions, just be aware we won’t update them with any new fields.

In the examples below, substitute https://your-domain.atlassian.net/ with the Data Center URL https://myexamplesite.com/rest/datapipeline/latest/ where myexamplesite is your domain. Remember to include your context path if you have one configured.

Request

There are no parameters for this request.

Example

1
2
3
curl --request GET \
  --url 'https://your-domain.atlassian.net/config/schema' \
  --header 'Accept: application/json'

Responses

Returns a list of supported schema versions in descending order.

Content typeValue
application/json

Array<SchemaResponse>

Rate this page: