13 FOCUSED GUIDES
REST API integration
Connect CRUD requests, filters and pagination, and interpret failures without guessing the contract.
Use get_project_api or the dashboard's generated OpenAPI contract for your project's exact data-plane routes. Machine keys and end-user tokens have different access models. Treat error status and JSON code together, keep credentials out of URLs, and test against disposable records before changing real data.
Plan request capacity →Make your first MCPBackend REST request
A first request should verify the actual project URL, table name and caller type with the smallest useful read.
Read the guide →PRACTICAL FIELD GUIDEFetch resolved, but the API returned an error
A fetch promise can resolve for an HTTP error response.
Read the guide →PRACTICAL FIELD GUIDEA 400 error names an unknown column
Unknown-column errors often indicate a mismatch between deployed client code and the current table schema.
Read the guide →PRACTICAL FIELD GUIDEUse supported REST filter operators
MCPBackend filter syntax supports defined operators rather than arbitrary SQL expressions.
Read the guide →PRACTICAL FIELD GUIDEMultiple REST filters combine with AND
Multiple supported filters narrow a result together rather than automatically creating an OR expression.
Read the guide →PRACTICAL FIELD GUIDEUnderstand contains search before using LIKE filters
A contains-style filter is different from a full-text search engine.
Read the guide →PRACTICAL FIELD GUIDEOffset pagination can shift when records change
Offset pagination selects a position in the current ordered result.
Read the guide →PRACTICAL FIELD GUIDEResponse count is not always the full table total
A returned count must be interpreted according to the API's response contract.
Read the guide →PRACTICAL FIELD GUIDEPATCH changes selected fields rather than replacing a row
A partial update sends only the fields being changed.
Read the guide →PRACTICAL FIELD GUIDEA successful DELETE returns no JSON body
A 204 response indicates successful completion without a response body.
Read the guide →PRACTICAL FIELD GUIDEA record returns 404: missing or not owned?
A 404 can represent a missing record or a record outside the end user's owner scope.
Read the guide →PRACTICAL FIELD GUIDEDistinguish 402 write caps from 429 request caps
MCPBackend quota errors identify different capacity boundaries.
Read the guide →PRACTICAL FIELD GUIDEA create request lost its response: avoid duplicate rows
A lost response does not establish whether a create request reached the server.
Read the guide →