Bubble

Delete a thing, via DELETE /api/1.1/obj/{typename}/{uid}. PERMANENT: Bubble's Data API offers no recycle bin and no undo, and the admin token disregards privacy rules, so nothing in the app stops this. Other things that LINK to the deleted one keep a reference that no longer resolves, which is worth checking before deleting a type other types point at. It answers 204 with an EMPTY body, so this reply says nothing about what happened -- confirm by asking for the thing again (404 afterwards) or by listing the type and checking the id is gone.

List things of a type, via GET /api/1.1/obj/{typename}. THIS IS THE LIST AND SEARCH TOOL and it is the only one: Bubble's Data API has no separate search endpoint, so filtering, sorting and paging all happen here. The reply is `{"response": {"results": [...], "cursor", "count", "remaining"}}` -- `count` is how many came back, `remaining` how many are left after them, so page by adding `count` to `cursor` until `remaining` is 0. Bubble returns at most 100 things per call. `constraints` is a STRINGIFIED JSON ARRAY of `{key, constraint_type, value}` objects, ANDed together -- for example `[{"key":"status","constraint_type":"equals","value":"open"}]`. The connection's admin token disregards privacy rules, so this returns every thing of the type rather than what any particular user would see, and every field of it. A type that is not exposed under Settings -> API answers `404 Type not found`.

Get a thing by its unique id, via GET /api/1.1/obj/{typename}/{uid}. The reply is `{"response": {...}}` carrying `_id`, `Created By`, `Created Date`, `Modified Date` and every data field of that thing. Use 'List things of a type' with a constraint when you have a field value rather than an id -- this route takes Bubble's `_id` and nothing else. An id that does not exist, or a type that is not exposed under Settings -> API, answers 404 with a body naming which; the admin token disregards privacy rules, so a 404 here is about existence rather than permission.

Change some fields on a thing, via PATCH /api/1.1/obj/{typename}/{uid}. THIS IS THE UPDATE TOOL -- use it rather than 'Replace every field on a thing', which empties everything you do not send. The body is a flat object of field name to value, and the keys should match the spelling a GET returns. Answers 204 with an EMPTY body, so this reply says nothing about the result: confirm with 'Get a thing by its unique id'. Not marked destructive -- the thing survives and only the named fields move -- but it writes to real data with an admin-equivalent token and privacy rules do not apply.

Create a thing, via POST /api/1.1/obj/{typename}. The body is a flat object of field name to value; `_id`, `Created Date` and `Modified Date` are set by Bubble and cannot be overridden, and a field left out takes the default configured on the type. Answers 201 `{"status": "success", "id": "..."}` -- that id is what every other tool here takes as `uid`. Creating a `user` is the special case: `Email` is required and `Password` optional, and this route creates the User WITHOUT returning an authentication token, so it cannot be used to sign anybody in. Use 'Create many things in one call' rather than looping this one for a batch.

Create many things in one call, via POST /api/1.1/obj/{typename}/bulk. THE BODY IS TEXT, NOT JSON: one complete JSON object per LINE, each with no newlines inside it, and the keys and values are exactly what 'Create a thing' takes. It is sent as `text/plain`, which the connector sets -- Bubble does not read this endpoint as JSON. PARTIAL SUCCESS IS THE NORMAL OUTCOME and this is the one thing to get right about it: the reply is one status LINE per input line, in order, each either `{"status":"success","id":"..."}` or an error for that line, and the call as a whole can answer 200 while individual lines failed. Read every line of the reply rather than the status code. Prefer this over looping 'Create a thing' for a batch.

Replace every field on a thing, via PUT /api/1.1/obj/{typename}/{uid}. DESTRUCTIVE, and it is the entry on this provider that surprises people: any field you do NOT give a value is emptied or reset to the type's default. The thing keeps its `_id` and its `Created Date`, and everything else you did not send is gone -- there is no undo and no recycle bin. Use 'Change some fields on a thing' unless you genuinely mean to blank the rest; reach for this only when you hold the complete record. Answers 204 with an EMPTY body, so confirm by reading the thing back.