Impacted Areas 73.0
Jul 02, 2026 • 2 minutes to readREST API Status Code Changes
In Release 73.0, Caspio expanded granular permissions across the REST API. Most of the changes below affect endpoints in both v2 and v3, which now return 403 Forbidden based on the caller’s object-level permissions. Additional updates correct status codes returned in specific scenarios, such as returning 404 Not Found when a referenced field does not exist.
If your integration relies on these responses, review the table below and update your permission settings and error-handling logic accordingly.
| Data import/export tasks | ||
| GET v2/tasks GET v3/dataImportExportTasks | 403 when “Enable access to all objects” is disabled. | 200 OK with list of readable tasks. |
| GET v2/tasks/{externalKey} GET v3/dataImportExportTasks/{externalKey} | 403 when “Enable access to all objects” is disabled. | 403 if no read permission for the task. |
| POST v2/tasks/{externalKey}/run POST v3/dataImportExportTasks/{externalKey}/run | 403 when “Enable access to all objects” is disabled. | 403 if no read permission for the task. |
| Bridge applications | ||
| PUT v2/applications/{externalKey}/datapages/{appKey}/deployment PUT v2/applications/{externalKey}/datapages/deployment PUT v3/applications/{externalKey}/datapages/{appKey}/deployment PUT v3/applications/{externalKey}/datapages/deployment | 403 when “Enable access to all objects” is disabled. | 403 if no deploy permission for the DataPages. |
| GET v2/applications/{externalKey}/datapages/{appKey}/deployment GET v3/applications/{externalKey}/datapages/{appKey}/deployment | 403 when “Enable access to all objects” is disabled. | 403 if no read permission for the DataPages. |
| GET v2/applications GET v3/applications | 403 when “Enable access to all objects” is disabled. | 200 with list of readable applications. |
| GET v2/applications/{externalKey} GET v3/applications/{externalKey} | 403 when “Enable access to all objects” is disabled. | 403 if no read permission for the application. |
| GET v2/applications/{externalKey}/datapages GET v2/applications/{externalKey}/datapages/{appKey} GET v3/applications/{externalKey}/datapages GET v3/applications/{externalKey}/datapages/{appKey} | 403 when “Enable access to all objects” is disabled. | 403 if no read permission for DataPages in the application. |
| Tables | ||
| POST /v2/tables/{tableName}/records POST /v3/tables/{tableName}/records | 400 InvalidDataforFormulaField. “Cannot perform operation because the values cause error in one or more formula fields.” | 201 |
| PUT /v2/tables/{tableName}/passwordFields/{passwordFieldName} PUT /v3/tables/{tableName}/passwordFields/{passwordFieldName} | -1 | 404 FieldNotFound. “Cannot perform operation because the following field(s) do not exist:[FieldName] “ |
| DELETE /v2/tables/{tableName}/passwordFields/{passwordFieldName} DELETE /v3/tables/{tableName}/passwordFields/{passwordFieldName} | 200 | 404 FieldNotFound. “Cannot perform operation because the following field(s) do not exist: [FieldName]” |
| GET /v3/tables/{tableName}/attachments/{attachmentFieldName} | 400 IncorrectQueryParameter. “Cannot perform operation because the query parameter is absent or invalid.” | 404 FileNotFound.”Cannot perform operation because the requested file does not exist.” |