For tables which you are configuring and deploying independently from Config.zip, use the following endpoints to create, update, or delete tables. All of the APIs mentioned below require you to be logged in as an administrator.
effectiveTimestampproperty specifies the effective date as a specific hour timestamp in unix epoch format. If minutes, seconds, and/or milliseconds are non-zero, the system will round to the next hour.
effectiveTimestampproperty is optional. The default
effectiveTimestampis the hour after the call is made. For example, if the current date and time is
October 1st, 2022 11:30:15am PST, the
effectiveTimestampwill be set to
October 1st, 2022 noon PST(in unix epoch format).
effectiveTimestampprecisely match an existing table with an effective date, and the table contents has changed, that table will be replaced with the new file. The tableName match is case sensitive. The effectiveTimestamp match compares the two timestamps, both of which are scoped to the hour.
If you deploy a .zip file, the name of each .csv file included in the .zip file will be used for the table name. Ensure file names match previous values if you intend to update existing tables using a bulk upload.
TableRequestincludes an exact duplicate of a previously uploaded table, the application will continue using the existing table rather than recreating it. A table is considered an exact duplicate if all of the following are unchanged:
See the Independent Table Configuration topic for more information about configuring and deploying tables independently from Config.zip.
requiredfile stringoptionaleffectiveTimestamp timestamptableName string
|string startsWith | contains | equals | all
requiredlocator stringeffectiveTimestamp timestampurlExpirationTimestamp timestamptableName stringurl string
requiredeffectiveTimestamp timestamperrorDetails stringtableName string