Hi, I'm Ask INFA!
What would you like to know?
ASK INFAPreview
Please to access Ask INFA.

Table of Contents

Search

  1. Preface
  2. Introducing Reference 360
  3. Getting started with Reference 360
  4. Manage system reference data
  5. Manage reference data sets
  6. Manage code lists
  7. Manage code values
  8. Manage crosswalks
  9. Import data
  10. Manage hierarchies
  11. Manage attributes
  12. Manage workflows
  13. Manage jobs
  14. Monitor Reference 360
  15. Reference 360 REST API
  16. Glossary

Reference 360

Reference 360

Export code lists at point in time to JSON format (v4)

Export code lists at point in time to JSON format (v4)

Exports the code values in a code list at a point in time to the JSON format based on the internal ID or alias of the code list.

POST request

To export code values in a code list based on the internal ID or alias, submit a POST request with the following URI:
/rdm-service/external/v4/export
In the request header, you must specify the
Accept
attribute to
application/json
.
Use the following parameters in the request body to specify the code list to export:
Field
Type
Description
dateFormat
String
Format used for dates. Use one of the following formats:
  • DE
    . For dd.mm.yyyy format.
  • ISO
    . For yyyy-mm-dd format.
  • US_HYPHEN
    . For mm-dd-yyyy format.
  • US_SLASH
    . For mm/dd/yyyy format.
delimiter
String
Delimiter used to separate values. Value must be
ASTERISK
,
CIRCUMFLEX
,
COLON
,
COMMA
,
PIPE
,
SECTION
,
SEMICOLON
,
SPACE
, or
TAB
.
textQualifier
String
Symbol used to indicate where a text begins and ends. Value must be
DOUBLE_QUOTE
,
SINGLE_QUOTE
, or
NO_QUOTE
.
startingRow
String
Line number from which to start importing data. By default, all rows are imported.
filename
String
File name for the exported file. Value must end with the
.csv
file extension.
codepage
String
Code page used for the export file. Value must be
UTF8
.
containerType
String
Type of asset that contains code values. Value must be
codelist
.
containerKey
String
Internal ID or alias of a code list.
filter
Object
Optional. Filter criteria for exporting filtered code values. For more information, see Filter criteria for export version 2 and 3.
excludeParentId
Boolean
Optional. Indicates whether to include the parent ID of code values in the JSON file. Value is
true
or
false
. Default is
false
.
pageSize
Number
Optional. Number of records to display on each page. The maximum value is
10000
. Default is
10000
.
page
Number
Optional. Page number to display. Default is
0
.
sort
Array
Optional. Sort criteria for exporting sorted code values. Values must be comma-separated field names prefixed with their sort directions. The plus symbol (+) indicates ascending order, and the minus symbol (-) indicates descending order. For example,
"_sort": ["+Name","-Code"]
indicates to sort the names in the ascending order and codes in the descending order.
pit
String
Optional. Date or date and time to retrieve the point in time information about the code list. Use the following ISO formats for date, and date and time:
  • Date. yyyy-mm-dd
  • Date and time. yyyy-mm-dd HH-mm-ss
addLabelsForReferenceAttribute
Boolean
Optional. Displays values for reference and dependent attributes based on the display attributes of reference and dependent code lists, respectively.
includeMetadataAttributes
Boolean
Optional. Indicates whether to include metadata of the code list in the JSON format. Default is
false
.

POST response

The response is in the JSON format.
When you export code values in a code list, the API response does not include the code values that don't contain relationships. The number of exported code values might result in mismatch with the number of imported code values.

POST example

To export the code values in a code list at a point in time based on the internal ID or alias, you might use the following request:
POST https://use4-mdm.dm-us.informaticacloud.com/rdm-service/external/v4/export HTTP/1.1 Content-Type: application/json Accept: application/json IDS-SESSION-ID: XXXXXXXXXXXXXXXXXXXXXX Content-Length: 356 { "delimiter": "SEMICOLON", "textQualifier": "DOUBLE_QUOTE", "startingRow": "0", "codepage": "UTF8", "dateFormat": "ISO", "filename": "export.json", "containerType": "CODELIST", "containerKey": "ent_country", "pageSize": 3, "page": 0, "pit": "2025-06-18 22-30-24" }
The following sample response shows the exported data in the JSON format:
HTTP/1.1 200 OK Content-Type: application/json;charset=UTF-8 Content-Length: 426 { "pageSize": 3, "page": 0, "totalNumberOfElements": 251, "numberOfElements": 3, "lastPage": false, "firstPage": true, "content": [ { "Code": "AC", "fields": { "Code": "AC", "Name": "Ascension" } }, { "Code": "AD", "fields": { "Code": "AD", "Name": "Andorra" } }, { "Code": "AE", "fields": { "Code": "AE", "Name": "United Arab Emirates" } } ] }

0 COMMENTS

We’d like to hear from you!