POST any JSON document to any named API and VividEcho persists it immediately. No schema, no migrations, no database setup. Full CRUD — create, read, update, and delete — is available the moment you make your first request. There's nothing to provision ahead of time and nothing to register before you start sending data.
VividEcho organizes documents into named collections — things like products, orders, or customers. You never create one in advance: the first time you save a document into a collection name, that collection starts existing. Different documents in the same collection don't need to share the same shape, since there's no schema enforcing consistency between them.
Collection names themselves are case-insensitive, so products and Products refer to the same collection, but the field names and values inside your documents are case-sensitive. Every document you create gets an id assigned automatically by VividEcho — you don't supply it, and you can't set it yourself when creating a record. That generated id is what you use afterward to fetch, update, or delete that exact document.
Once a collection exists, the full set of CRUD verbs work against it right away: GET to read, POST to create, PUT to replace, PATCH to partially update, and DELETE to remove. You can address a whole collection, a single document by its id, or a set of documents matched by a field's value — all through the same predictable URL shape.