Logic API
Logic API
Design REST APIs over Dataverse without code, publish them as versions, and let web and mobile apps call them.
Logic API lets functional consultants build the REST API that a portal, a mobile app or a partner system uses to work with Dataverse data. Instead of asking backend developers to hand-code endpoints, you describe what the API exposes in API Studio: which tables, which fields, which Dataverse actions, which queries, and who may call each one. Logic API turns that description into working HTTP endpoints.
Because the API is configured next to the Dataverse customizations it depends on, the people who know the data model best own the API, and it stays in step with the model as it changes.
How it works: design, then publish
Section titled “How it works: design, then publish”Every API has one editable Draft. You design in the draft, then publish it as a numbered version such as 1.0 or 1.1. Published versions are read-only; they are what callers use. To change the API again, you start a new draft from a published version.
flowchart TD A[Design the draft<br/>in API Studio] --> B[Fix issues<br/>and save] B --> C[Publish as<br/>1.0, 1.1, 2.0 …] C --> D[API host serves<br/>the version] D --> E[Apps call<br/>the endpoints] C -. new draft from a version .-> A
What an API is made of
Section titled “What an API is made of”| Building block | What it gives callers |
|---|---|
| Modules | Groups of endpoints for one business area, such as Sales or Service. The module name is the first segment of every address in it. |
| Entities | The Dataverse tables a module exposes. Each entity gets its own Read, Create, Update, Delete, Upload, Download and Process actions. |
| Process actions | Dataverse actions you expose as endpoints, either bound to a record of an entity, or standalone in a module. |
| Queries | Read-only endpoints that return one record, a list, or pages of records across tables. |
| Option sets | Choice lists that apps load to fill drop-downs, with labels in the caller’s language. |
| Context | The Roles and User properties that describe the caller, used in access checks. |
| Access control | Per action and query: an authorization policy (who may call it) and a precondition (when it may run). |
Where it fits
Section titled “Where it fits”- Designers work in API Studio, inside the Logic Fabric API Builder app.
- A published version is served by an API host that your organization runs. The host reads the published API from Dataverse; see Install and host Logic API.
- Pipelines publish drafts and export OpenAPI schemas with the Logic Fabric CLI.