Impacted Areas 78.0
Jul 02, 2026 • 2 minutes to readREST API v4 response changes
In Release 78.0, Caspio made REST API v4 responses more consistent and easier to work with. More responses now return their content inside the standard data wrapper, record update responses include the PK_ID of the updated records, and record IDs in table URL paths are typed as integers. If your integration used REST API v4 and relies on these responses, review the table below and update how your integration reads them.
| 77.0 and prior | 78.0 and after | |
| Bridge applications | ||
| GET /v4/bridgeApplications/{appId}/dataPages/{appKey}/deployment} | Returns the deployment code as a plain string. | Returns a JSON object. Read the deployment code from data.code. |
| Outgoing webhooks | ||
| GET /v4/outgoingWebhooks/{webhookId} PATCH /v4/outgoingWebhooks/{webhookId} with echo=true | Returns webhookId, name, status , and other webhook fields at the top level of the response. |
Returns the webhook fields inside data. |
| GET /v4/outgoingWebhooks/{webhookId}/events/{eventId} PATCH /v4/outgoingWebhooks/{webhookId}/events/{eventId} with echo=true | Returns eventId, type, objectId , and other event fields at the top level of the response. |
Returns the event fields inside data. |
| Tables and views | ||
| PUT and PATCH /v4/tables/{tableId}/records/{recordPkId} PUT and PATCH /v4/views/{viewId}/records/{recordPkId} | With echo=false, returns data with a null value. |
With echo=false, leaves out data and returns the record’s PK_ID as a string. Treat a missing data the same as null. |
| PATCH /v4/tables/{tableId}/records/bulk PATCH /v4/views/{viewId}/records/bulk | Returns the number of affected records. | Also returns PK_ID as an array of strings, one for each updated record. |
| GET, PUT, PATCH, and DELETE /v4/tables/{tableId}/records/{recordPkId} GET, PUT, and DELETE /v4/tables/{tableId}/records/{recordPkId}/attachments/{fieldName} | recordPkId is typed as a string. | recordPkId is typed as a 32-bit integer. In view record endpoints, it stays a string, because a view that joins several tables uses a comma-separated PK_ID. |
| Single and bulk PUT and PATCH on table and view records | Single and bulk PUT and PATCH on table and view records | Update responses include PK_ID. |
