SlicingDice Documentation

SlicingDice API Docs

Welcome to the SlicingDice API documentation. You'll find comprehensive guides and documentation to help you start working with SlicingDice as quickly as possible, as well as support if you get stuck. Let's jump right in!

Get Started    Documentation

API Errors

API errors happen when the request cannot be processed due to a fatal error, such as when the user cannot authenticate with the given API key. In this case, the API returns an error HTTP status code and an error message explaining what happened.

For instance, the following error message is returned by the API when the Authentication header contains an invalid API key.

{
    "errors": [
        {
            "code": 12,
            "message": "Authentication: Invalid API key"
        }
    ]
}

Below you can find the full list of all possible API errors and a short hint of how to solve it.

General Errors

Error Code
Error Description
Possible Causes
Solution

1 (HTTP 500)

SlicingDice: Internal error.

Something went wrong with SlicingDice.

Please get in contact with our support team.

2 (HTTP 500)

SlicingDice: The /test endpoint is currently unavailable for data cleanup but will be available again within few minutes.

You have probably tried to use the /test endpoint while its data was being cleaned, that happens every six hours.

Just wait few 1-2 minutes and try to use it again.


Authentication Errors

Error Code
Error Description
Possible Causes
Solution

500 (HTTP 401)

Authentication: Missing "Authorization" header.

The Authorization header is missing from the request headers.

Include the Authorization in the request headers. Check the API Connection and Headers docs.

501 (HTTP 401)

Authentication: Missing API key in "Authorization" header.

The Authorization header is empty.

Provide a proper API key in the Authorization header. Check the API Connection and Headers docs.

502 (HTTP 401)

Authentication: Invalid API key.

The provided API key is not valid.

Replace the provided API key by a new one from the control panel or use a demo API key. Check the API Keys docs.

503 (HTTP 403)

Authentication: Incorrect API key permission.

The provided API key cannot request from the endpoint in question.

Replace the provided API key by a new one from the control panel with higher permission. Check the API Keys docs.

504 (HTTP 403)

Authentication: Remote address not in whitelisted addresses.

The API key is being used behind an IP or domain name that is not configured in the whitelisted addresses.

Add the IP or domain name to the whitelisted addresses at the control panel. Check the API Whitelists.

505 (HTTP 403)

Authentication: Custom API key cannot be used to create columns and doesn't support the "auto-create" parameter.

Custom API keys cannot be used with the POST /column endpoint or to create columns with auto-create parameter.

Use a regular write or master API key to create columns. Check the API Keys docs.

506 (HTTP 403)

Authentication: Your custom API key does not have permission to operate with the column "<column-name>".

The custom API key used tried to insert or query using the column <column-name> that it was not allowed to.

Edit the custom API key allowed columns on the control panel or use another custom API key. Check the API Keys docs.

507 (HTTP 403)

Authentication: Incorrect custom API key permission. The endpoint "<endpoint-name>" requires "<required-permission>" permission but the API key used has only "<current-permission>".

The custom API key used tried to access the endpoint <endpoint-name> not allowed for its <current-name> permission level, such as read-only, write-only or read-write.

Edit the custom API key allowed columns on the control panel or use another custom API key. Check the API Keys docs.

508 (HTTP 403)

Authentication: Incorrect custom API key permission. Cannot delete saved query created by another custom API key.

The custom API key used tried to edit a saved query that was not created by it.

Use the custom API key that created the saved query.

509 (HTTP 403)

Authentication: Custom API key cannot be used for endpoint "<endpoint>".

The custom API key used requested an endpoint which it is not allowed to.

Change the custom API key permission or use a different one allowed to request from the desired endpoint. Check the API Keys docs.

510 (HTTP 403)

Authentication: Demo API key cannot be used in production endpoint, must be used in test endpoint only.

The demo API key was used with the production endpoint, however it is only allowed to interact with the /test endpoint.

Change URL to use the /test endpoint or use a different API key. Check the API Keys docs.

511 (HTTP 403)

Authentication: Custom API key cannot be used to create tables and doesn't support the "auto-create" parameter.

Custom API keys cannot be used with the POST /table endpoint or to create tables with auto-create parameter.

Use a regular write or master API key to create tables. Check the API Keys docs.


Request Errors

Error Code
Error Description
Possible Causes
Solution

1500 (HTTP 415)

Request: Missing "Content-Type" header.

The Content-Type header is missing from the request headers.

Include Content-Type: application/json in the request headers. Check the API Connection and Headers docs.

1501 (HTTP 415)

Request: "application/json" must be specified in the "Content-Type" header.

The provided content type in Content-Type header is not application/json.

Include Content-Type: application/json in the request headers. Check the API Connection and Headers docs.

1502 (HTTP 429)

Request: You have exceeded your limit of requests per minute.

You are generating more requests per minute than allowed by the API.

Reduce request rate, wait one minute or contact our support.

1503 (HTTP 400)

Request: Incorrect JSON syntax.

Your request does not provide a valid JSON syntax.

Fix the JSON syntax before requesting again.

1504 (HTTP 405)

Request: Invalid HTTP method for this endpoint.

Your request uses an HTTP method not allowed for the given endpoint.

Use a valid HTTP method for each API Endpoint.

1505 (HTTP 404)

Request: Invalid "<endpoint>" endpoint.

Your request tried to access an invalid endpoint endpoint.

Use a valid API endpoint.
Check the API endpoints docs .

1506 (HTTP 403)

Request: HTTP is not allowed, use HTTPS instead.

Your request issued a HTTP request to an HTTPS-only endpoint.

Repeat the request with HTTPS.

1507 (HTTP 413)

Request: Exceeded maximum request size of 5 MB.

Your request is larger than 5 MB.

Break your request into smaller requests that are less than 5 MB.


Account Errors

Error Code
Error Description
Possible Causes
Solution

1000 (HTTP 403)

Account: No payment method defined.

You must provide a payment method, such as a credit card, before starting to use SlicingDice.

Visit the control panel and add a new payment method.

1001 (HTTP 403)

Account: Suspended account due to lack of payment.

Your account has been suspended because an open invoice has not been payed yet.

Visit the control panel and add a new payment method, and get in contact with us.

1002 (HTTP 403)

Account: Banned account.

Your account has been banned due violations of our terms of service.

1003 (HTTP 403)

Account: Disabled account.

Your account has been disabled due violations of our terms of service.


Insert Errors

Error Code
Error Description
Possible Causes
Solution

2000 (HTTP 400)

Insert: Insert value for "<column-name>" must be within the defined column ranges.

You tried to insert a value in the column that is out of the ranges defined during the column creation.

Check the possible ranges for the column <column-name>.

2001 (HTTP 400)

Insert: Event date is older than the database's Event Column Data Retention Time configuration.

You cannot store event data with dates that lie outside the database's Event Column Data Retention Time configuration. For instance, if your Event Column Data Retention Time is 30 days, you cannot insert data from more than 30 days ago.

Insert data in a database with greater Event Column Data Retention Time.

2002 (HTTP 400)

Insert: Event date is older than the oldest supported date.

You cannot insert event data with dates previous to 2005-01-01.

Please contact us if you need time series support for periods longer than 12 years.

2003 (HTTP 400)

Insert: Entity ID cannot be empty.

You provided an entity ID without any character.

Provide an entity ID with a non-empty string value.

2004 (HTTP 400)

Insert: Decimal value for "<column-name>" column has too many decimal places.

You tried to insert a decimal or decimal event value in the column <column-name> with more decimal places than configured.

Give a decimal value with less decimal places.

2005 (HTTP 400)

Insert: Entity value must be a JSON object.

You provided an invalid JSON object as entity values when inserting data.

Fix the JSON syntax before requesting again.

2006 (HTTP 400)

Insert: Cannot insert event data in the future.

You provided the date parameter with a date in the future for a event column.

Provide a valid date value in the past or omit it to insert with the current time.

2007 (HTTP 400)

Insert: Incorrect value type for this column.

You provided a value in a type that is not valid for the column's data type.

Provide data in the correct type before requesting again.

2008 (HTTP 400)

Insert: Entity ID must have at most 1,000 characters.

You provided an entity ID larger than allowed.

Reduce the entity ID length before requesting again.

2009 (HTTP 400)

Insert: Column value has exceeded the maximum allowed length.

You provided a column value larger than allowed.

Reduce the column value length before requesting again.

2010 (HTTP 400)

Insert: "date" parameter in event columns must be in ISO 8601 format ("YYYY-MM-DD" or "YYYY-MM-DDThh:mm:ssTZ").

You provided a date value not in YYYY-MM-DD or YYYY-MM-DDThh:mm:ssTZ format.

Provide a valid date value before requesting again.

2011 (HTTP 400)

Insert: Column "<column-name>" is not active or does not exist.

Your insertion contains a column <column-name> that is not active in the database or does not exist at all.

Check your active columns before requesting again.

2012 (HTTP 400)

Insert: Exceeded the maximum number of entity IDs.

Your request contains more entity IDs than allowed.

Split you data and insert it in multiple requests.

2013 (HTTP 400)

Insert: Exceeded the maximum number of columns.

Your request contains more columns than allowed.

Split you data and insert it in multiple requests.

2014 (HTTP 400)

Insert: Values for date column must be in ISO 8601 format ("YYYY-MM-DD").

Your request contains a value for a date column not in YYYY-MM-DD format.

Provide a valid date value before requesting again.

2015 (HTTP 400)

Insert: Invalid value for "string" type. Cannot be empty.

Your request contains an string column with empty value, such as "my-string-column": "".

Remove the column from your request or provide a non-empty value to be inserted.

2016 (HTTP 400)

Insert: Invalid parameter in event data. Must be only "value" and "date".

Your request is inserting event data with a parameter other than value and date.

Remove all parameters that are neither value nor date.

2017 (HTTP 400)

Insert: Invalid "<entity-id>" entity. Must have at least 1 column.

Your request contains an entity without any column being inserted to it.

Provide at least one column per entity to be inserted.

2018 (HTTP 400)

Insert: Missing "value" parameter in event data.

Your request is inserting event data without the value parameter.

Provide a valid value to be inserted.

2019 (HTTP 400)

Insert: Cannot repeat entity IDs in a single request.

Your insert request contains repeated entity IDs in the same message.

Aggregate the repeated entity IDs in a single entry and repeat your request.

2020 (HTTP 400)

Insert: Invalid insertion on entity-id column.

The column entity-id is an internal column and its value is based on stored entity ID. You are not allowed to insert directly on it.

You can't and don't need to insert directly on entity-id column, it is inserted automatically based on the value you pass as the Entity ID in the insertion request. Simply remove any entity-id keys present in your insertion request.


Column Errors

Error Code
Error Description
Possible Causes
Solution

3000 (HTTP 400)

Column: Missing "<parameter-name>" parameter.

Your request is missing one parameter when creating a column and cannot be completed.

Check the docs and fix the missing parameter before retrying to create the column.

3001 (HTTP 400)

Column: Invalid type.

Your request has an invalid column type.

Check our supported data types before retrying to create the column.

3002 (HTTP 400)

Column: Values used in "range" must be integers.

Your request to create an enumerated column defined the range parameter with a non-integer value.

Remove all non-integer values from the range parameter.

3003 (HTTP 400)

Column: Column already exists.

A column has already been created with the same name.

Create your column with another name.

3004 (HTTP 400)

Column: Exceeded maximum number of columns.

You are creating more columns than allowed in a single request.

Create your columns in multiple requests.

3005 (HTTP 400)

Column: Parameter "decimal-places" must be an integer.

When creating a decimal or decimal event column, you defined decimal-places with a non-integer value.

Define decimal-places with an integer number from 1 to 20, including them.

3006 (HTTP 400)

Column: Invalid value for parameter "storage". Must be either "latest-value" or "list-of-values".

When creating a column, you defined storage with a value other than "latest-value" or "list-of-values".

Define storage with either "latest-value" or "list-of-values".

3007 (HTTP 400)

Column: Invalid API name "<api-name>".

When creating a column, you defined API name with a value containing characters other than alphanumeric a-z0-9 and -.

Define API name with only alphanumeric a-z0-9 and - characters.

3008 (HTTP 400)

Column: Invalid column name.

When creating a column, you defined name with a value containing characters other than alphanumeric a-zA-Z0-9 and -.

Define name with only alphanumeric a-zA-Z0-9 and - characters.

3009 (HTTP 400)

Column: Invalid description.

When creating a column, you defined description with a value containing invalid characters ' or ".

Define description removing ' and " characters.

3010 (HTTP 400)

Column: Exceeded maximum description length.

When creating a column, you defined description containing more than 256 characters.

Define description with a smaller text.

3011 (HTTP 400)

Column: Invalid value for parameter "cardinality". Must be either "low" or "high".

When creating a string column, you defined cardinality with a value other than "low" or "high".

Define cardinality with either "low" or "high".

3012 (HTTP 400)

Column: Parameter "decimal-places" must be from 1 to 20, including them.

When creating a decimal or decimal event column, you defined decimal-places with a number greater than or equal to 20.

Define decimal-places with an integer number from 1 to 20, including them.

3013 (HTTP 400)

Column: Parameter "range" must have between 1 and 1,024 values, without any repeated one.

When creating an enumerated column, you defined range with either repeated values, less than 1 value or more than 1,024 values.

Change the range parameter to remove repeated values, provide at least 1 value or reduce to at most 1,024 values.

3014 (HTTP 400)

Column: Exceeded maximum name length.

When creating a column, you defined name containing more than 64 characters.

Define name with a smaller text of at most 64 characters.

3015 (HTTP 400)

Column: Exceeded maximum API name length.

When creating a column, you defined api-name containing more than 64 characters.

Define api-name with a smaller text.

3016 (HTTP 400)

Column: Numeric value for "<column-name>" column is either too large or too small.

When creating an enumerated column, you defined one of the values either too large or too small.

Define range parameter with values going from 2^63 - 1 to -2^63

3017 (HTTP 400)

Column: Invalid Retention Time value.

When creating an event column, you defined an invalid retention time.

Check our supported data retention times and provide a valid retention time when creating the event column.

3018 (HTTP 400)

Column: Column "<column-name>" does not exist.

You tried to update a column that does not exist.

Check your existing columns before requesting again.


Query Errors

Error Code
Error Description
Possible Causes
Solution

4000 (HTTP 400)

Query: Cannot use "seconds" for periods greater than the last 24 hours.

Your request defined a time interval resolution of "seconds", which is available only for queries with periods spanning the last 24 hours.

Use a higher resolution or change the query period to the last 24 hours.

4001 (HTTP 400)

Query: Cannot use "minutes" for periods greater than the last 24 hours.

Your request defined a time interval resolution of "minutes", which is available only for queries with periods spanning the last 24 hours.

Use a higher resolution or change the query period to the last 24 hours.

4002 (HTTP 400)

Query: Cannot use "hours" for periods greater than the last 30 days.

Your request defined a time interval resolution of "hours", which is available only for queries with periods spanning the last 30 days.

Use a higher resolution or change the query period to the last 30 days.

4003 (HTTP 400)

Query: Invalid relative time interval.

Your request defined an invalid relative time interval.

Provide a valid relative time interval before requesting again.

4004 (HTTP 400)

Query: Missing query JSON object.

Your query must contain at least one query JSON object.

Fix your query syntax.

4005 (HTTP 400)

Query: Must contain "between" parameter for event columns.

Your request with a event column doesn't contain the between parameter.

Provide the between parameter for the event columns.

4006 (HTTP 400)

Query: Missing "type" parameter.

When creating a saved query, the type parameter is missing.

Provide the type parameter with a valid query type.

4007 (HTTP 400)

Query: Incorrect operator usage.

Your query contains an operator that has been mistakenly used.

Check the operators syntax.

4008 (HTTP 400)

Query: Column is not active or does not exist.

Your query contains a column that is not active in the database or does not exist at all.

Check your active columns before requesting again.

4009 (HTTP 400)

Query: Missing parameter.

Your request didn't include any parameter to a given column. Note that all event column must have a parameter besides between.

Provide at least one parameter in the column before requesting again.

4010 (HTTP 400)

Query: Missing "<parameter-name>" parameter.

Your request didn't provide a parameter required by the query being executed. For instance, this happens when querying aggregation without the query parameter.

Provide the required parameter.

4011 (HTTP 400)

Query: Must contain parameter besides "between" for event column.

Your request to a event column didn't include any parameter besides between.

Provide one parameter besides between, such as equals, gt, gte, lt or lte.

4012 (HTTP 400)

Query: Parameter "range" must have two integer values.

Your request contains a range parameter without exactly two integer values.

Provide range with two integer values.

4013 (HTTP 400)

Query: Exceeded maximum number of columns.

Your query exceeded the maximum number of columns allowed in a single request, according to its limits.

Reduce the number of columns.

4014 (HTTP 400)

Query: Invalid query. Must have at least one column.

Your query didn't provide one column to work on.

Provide at least one column before requesting again.

4015 (HTTP 400)

Query: "query" parameter must be a list of aggregation conditions.

Your query to an aggregation query contains a query parameter whose value isn't a list of aggregation conditions.

Provide query as a list of aggregation conditions.

4016 (HTTP 400)

Query: "contains" parameter must be a list of string values.

Your query to a top values query contains a contains parameter that isn't a list of strings.

Provide contains in a list format.

4017 (HTTP 400)

Query: Parameter "<parameter-name>" should be used with event column.

Your query contains a parameter <parameter-name> that has been mistakenly used with a attribute column.

Check the parameters syntax.

4018 (HTTP 400)

Data extraction: Parameter "columns" can only be used with attribute columns, not event columns.

Your request to a data extraction query is using the columns parameter containing a event column name among its values.

Replace the event column being used by an attribute column.

4019 (HTTP 400)

Query: Exceeded maximum number of IDs for exists query.

Your exists query contains more entity IDs than allowed.

Reduce the number of entity IDs in a single query.

4020 (HTTP 400)

Query: Only one filter can be used.

Your filtered aggregation query contains more than one filter.

Remove one of the filters.

4021 (HTTP 400)

Query: Missing "name" parameter when creating saved query.

Your request to create a saved query is missing the name parameter.

Provide a valid saved query name value.

4022 (HTTP 400)

Query: Saved query already exists with the same "name" value.

Your request to create a saved query contains a name value that already belongs to another saved query.

Provide a different saved query name value.

4023 (HTTP 400)

Query: Saved query does not exist.

Your request to execute a saved query uses a query name that doesn't belong to any of your saved queries.

Provide a name of an existing saved query.

4024 (HTTP 400)

Query: Invalid "type" value for saved queries.

Your request to execute a saved query provided a query type in type that isn't valid.

Provide valid query type in the type parameter.

4025 (HTTP 400)

Query: Missing "ids" parameter.

Your exists query doesn't contain the ids parameter.

Provide a valid ids parameter.

4026 (HTTP 400)

Query: Invalid query format. Must be a list.

Your request provided a query that isn't a list.

Provide a query in a list format.

4027 (HTTP 400)

Query: Invalid value for parameter "interval". Must be either "months", "weeks", "days", "hours", "minutes" or "seconds".

Your request provided an invalid interval value.

Provide a valid interval value.

4028 (HTTP 400)

Data extraction: Invalid type for "limit" parameter. Must be a positive integer value.

Your request with data extraction queries defined the limit parameter with a non-positive integer value.

Define limit with a positive integer value.

4029 (HTTP 400)

Data extraction: Invalid value for "page-token" parameter. Must be a valid string value.

Your request defined page-token with a non-string value or a string with invalid value.

Provide page-token with a valid string value. See pagination in data extraction for more details.

4030 (HTTP 400)

Data extraction: Exceeded maximum of 10 values in the "columns" parameter.

Your request with data extraction queries defined more than 10 columns to be returned in a single request.

Provide columns parameter with less than 10 values.

4031 (HTTP 400)

Query: Invalid value for "ids" parameter. Cannot be empty.

Your exists query defined the ids parameter with an empty list.

Provide ids parameter with a non-empty list of entity IDs.

4032 (HTTP 400)

Query: Invalid "query" parameter usage for saved query. Cannot be used with "count/entity/total" query type.

Your request to create a saved query cannot contain the query parameter if the type is count/entity/total.

Remove the query parameter from the request.

4033 (HTTP 400)

Query: Invalid type for "cache-period" parameter for saved query. Must be an integer value greater than or equal to 5 seconds.

Your request to create a saved query defined the cache-period parameter with a non-integer value or a value less than 5.

Provide cache-period with an integer value greater than or equal to 5.

4034 (HTTP 400)

Query: Invalid value in "name" value for saved query. Must contain only alphanumeric ("a-zA-Z0-9") or "-" characters.

Your request to create a saved query defined the name parameter with a value containing characters other than alphanumeric a-zA-Z0-9 or -.

Provide a valid name value.

4036 (HTTP 400)

Query: Your request exceeded the maximum number of queries.

Your request contains more queries in a single request than allowed.

Check the limits and reduce the number of queries per request.

4037 (HTTP 400)

Query: Invalid "<operator-name>" operator usage. Cannot be used with "<endpoint-name>" endpoint.

Your query contains an operator <operator-name> that cannot be used with the endpoint <endpoint-name>.

Check the operators usage before trying again.

4038 (HTTP 400)

Query: Invalid "<parameter-name>" parameter usage. Cannot be used with "<endpoint-name>" endpoint.

Your query contains an parameter <parameter-name> that cannot be used with the endpoint <endpoint-name>.

Check the parameters usage before trying again.

4039 (HTTP 400)

Query: Invalid "<parameter-name>" parameter usage. Cannot be used with "<type-name>" data type.

Your query contains an parameter <parameter-name> that cannot be used with the given column type <type-name>.

Check the parameters usage before trying again.

4040 (HTTP 400)

Query: Invalid "<column-name>" column usage. Cannot be used with "<endpoint-name>" endpoint.

Your query contains a column type <column-name> that cannot be used with the endpoint <endpoint-name>, such as attribute column with a count event query.

Remove any invalid column from the request before trying again.

4041 (HTTP 400)

Query: Invalid value in "name" value for saved query. Must contain between 1 and 64 characters.

Your request to create a saved query defined the name parameter with a value containing more than 64 characters.

Provide a valid name value with 64 characters or less.

4042 (HTTP 400)

Query: "<parameter-name>" parameter must be a list of string values, for type query "<query-type>".

Your request to create a saved query should have the <parameter-name> parameter defined as a list of string values.

Provide a list of string values to <parameter-name>

4043 (HTTP 400)

Query: Missing "<parameter-name>" parameter.

Your query request didn't provide the required <parameter-name> parameter

Provide a valid value for <parameter-name> parameter.

4044 (HTTP 400)

Query: Date in "<parameter-name>" parameter must be in ISO 8601 format ("YYYY-MM-DD" or "YYYY-MM-DDThh:mm:ssTZ").

Your request defined a date not in YYYY-MM-DD or YYYY-MM-DDThh:mm:ssTZ format for the parameter <parameter-name>.

Provide a valid date before requesting again.

4045 (HTTP 400)

Query: Invalid aggregation metric "<metric-name>".

Your request is using an invalid aggregation metric <metric-name>.

Replace the invalid aggregation metric by a valid one.

4046 (HTTP 400)

Query: Aggregation metric "<metric-name>" cannot be used with "<column-name>" column.

Your request is using an aggregation metric <metric-name> with a non-supported data type in the column <column-name>.

Replace the column being used by a supported one for the given metric.

4047 (HTTP 400)

Query: Invalid value for "<parameter-name>" parameter. Cannot be empty.

Your query defined a parameter <parameter-name> with an empty string.

Provide a valid non-empty string for the parameter.

4048 (HTTP 400)

Query: Invalid value for "<parameter-name>" parameter. Exceeded maximum number of <max-values> values.

Your query defined a parameter <parameter-name> with more than <max-values> values.

Reduce the number of values defined in the <parameter-name> parameter.

4049 (HTTP 400)

Query: Invalid "<parameter-name>" parameter.

Your request contained a parameter <parameter-name> that is not valid.

Remove or correct the wrong parameter.

4050 (HTTP 400)

Query: "minfreq" parameter must be an integer greater than 0 and less or equal to 10,000.

Your request contained a minfreq parameter with a non-integer value, less than or equal to 0 or greater than 10,000.

Provide an integer value to minfreq greater than 0 and less or equal to 10,000.

4051 (HTTP 400)

Query: Invalid number of values to be returned in "<column-name>" column. Must be an integer between 1 and 1,000.

Your request to execute a top values or aggregation query provided a number of values to be returned that is invalid. It can happen if the value isn't an integer, less than 1 or greater than 1,000.

Provide valid number of values to be returned.

4052 (HTTP 400)

Data extraction: The value for the "limit" parameter should be less or equal than 100 on data_extraction/total.

Your request on /data_extraction/result/total or /data_extraction/score/total provided a invalid limit value. It can happen if your limit is greater than 100.

Provide a limit between 0 and 100.


Table Errors

Error Code
Error Description
Possible Causes
Solution

5000 (HTTP 400)

Table: Invalid API name "<table-name>".

When creating a table, you defined API name with a value containing characters other than alphanumeric a-z0-9 and -.

Define API name with only alphanumeric a-z0-9 and - characters.

5001 (HTTP 400)

Table: Invalid table name.

When creating a table, you defined name with a value containing characters other than alphanumeric a-zA-Z0-9 and -.

Define name with only alphanumeric a-zA-Z0-9 and - characters.

5002 (HTTP 400)

Table: Invalid description.

When creating a table, you defined description with a value containing invalid characters ' or ".

Define description removing ' and " characters.

5003 (HTTP 400)

Table: Exceeded maximum name length.

You tried to create a table with a very large name (more than 64 characters)

Shorten the table name and try again

5004 (HTTP 400)

Table: Exceeded maximum API name length.

You tried to create a table with a very large API name (more than 64 characters)

Shorten the table API name and try again

5005 (HTTP 400)

Table: Exceeded maximum description length.

You tried to create a table with a very large description (more than 256 characters)

Shorten the table description and try again

5006 (HTTP 400)

Table: Table already exists.

You tried to create a table using the name of an already existing table.

Use the already existing table or change the name.

5007 (HTTP 400)

Table: Missing "<parameter-name>" parameter.

Your request to create a new table requires you to define <parameter-name> parameter.

Define the missing parameter and try again.

5008 (HTTP 400)

Table: Table does not exist.

You tried to operate over a non existing table.

Create the missing table or use an existing table.


API Errors