POST any JSON document to a named API endpoint. No schema to define, no table to create. VividEcho stores it and assigns an ID. That's the whole setup step — there's no console screen where you draft a schema first and no migration to run before your app can start writing data.
VividEcho organizes documents into collections — named buckets like products, orders, or customers. You don't provision one ahead of time; the moment you save your first document into products, that collection exists. Collection names are case-insensitive, so products and Products refer to the same place, but the field names and values inside your documents are case-sensitive. Because there's no schema, two documents in the same collection are free to carry different fields — you can add a field to your app's data model without touching any server-side definition.
A create is a plain POST to /api/{collection} with your JSON body. You never supply the record's id yourself — VividEcho assigns a unique one on creation and hands it back so you can fetch, update, or delete that exact record later. By default the response just confirms the new id; if you'd rather get the full stored document back in the same round trip, add ?echo=true to the request.
If a field like an email address needs to stay unique per record, post to the field/value form of the URL instead of the bare collection — for example /api/users/email/someone@example.com. VividEcho checks for an existing record with that field value among your own records and rejects the request as a conflict rather than creating a duplicate.