How to use your website's data through the API

Every Genaya website owns a database (Dashboard > Data): the built-in Leads and Bookings tables plus the custom tables you or Genaya AI create. The public Genaya REST API reads and writes those records like any other resource, and Dashboard > API writes the reference for exactly this site so you never guess an id or a field key.

1. 1
   Create an access token

   The Create an access token button on the Authentication card opens Settings -> Developer, where an API key is minted with the scopes it may use. Reads need sites:read, writes sites:write; a key with no scopes has full access. The Developer API is included from Individual up; the trial gets one read-only test key with 500 requests in all. Copy the key once - it is shown once - and send it as a bearer token: Authorization: Bearer gny_live_xxx.

2. 2
   Read the endpoints per table

   Each table is one block: the schema table (every field with its key, label, type, the options of a choice field and whether it is required) and the endpoint list - list records, create a record, get, update, move to the trash and restore - each with Copy the curl. Above the tables sit the Authentication card (the scopes, the base URL, a curl and a JavaScript example with a bearer key) and the This website card with the site-level calls: list your websites and retrieve this one (name, public link, connected domain, status, page count, last published).

3. 3
   Copy for LLM

   Copy for LLM puts an OpenAPI 3.1 subset for this site on the clipboard - the site's own tables, fields and endpoints, nothing else - so you can paste it into an assistant or a code generator and get working calls on the first try. The full reference for every call is on developer.genaya.com (Open the reference next to it).

4. 4
   Write records

   Create sends values keyed by the table's field keys; the server checks every value against the field type (a required field must be present, a choice must be one of its options). Update is partial - only the keys you send change. Delete is a 30-day trash with Restore. Lists page forward with starting_after. Send an Idempotency-Key on a create so a retried request never makes two records.