Table 812 "API Overview Buffer"
Base Application · Microsoft.API
Across versions
- BC23-28not present
- BC29added
- BC30unchanged
Neighbourhood 2 connected objects and pages
Base Application · Microsoft.API · BC29-30 · source at ea08af5e · facts from BC29
Learn documents this table through its pages: Page 812 “API Overview” (1 Learn page).
Properties
| Property | Value |
|---|---|
| Access | Internal |
| TableType | Temporary |
| DataClassification | SystemMetadata |
Fields
Explanation: the field’s ToolTip in the code; without one, the ToolTip of a page control bound to the field (marked via the page); without that, its Caption (marked caption) when that differs from the name.
| No. | Name | Type | Explanation | Notes |
|---|---|---|---|---|
| 1 | Entry No. | Integer | — | |
| 2 | Description | Text[250] | Specifies the name of the API page or query. via Page 812 “API Overview” | |
| 3 | Object Type | Option | Specifies whether the API is implemented as an API page (read and write operations), an API query (read-only set of data), or an API codeunit (operations exposed as unbound actions). via Page 812 “API Overview” | OptionCaption: ,Page,Query,Codeunit |
| 4 | Object ID | Integer | Specifies the object ID of the underlying API page or query. Use this when troubleshooting integrations together with a developer. via Page 812 “API Overview” | |
| 5 | Entity Name | Text[250] | Specifies the entity that the API exposes. The entity name appears in the API URL and helps identify the originating solution. via Page 812 “API Overview” | |
| 6 | API Publisher | Text[40] | Specifies the publisher segment of the API URL. The publisher identifies who owns the API and is part of the route used by external systems. via Page 812 “API Overview” | |
| 7 | API Group | Text[40] | Specifies the group segment of the API URL. Use the API group to scope integrations to a related set of endpoints. via Page 812 “API Overview” | |
| 8 | API Version | Text[250] | Specifies the version segment of the API URL. Choosing the right version ensures compatibility when integrating with external systems. via Page 812 “API Overview” |
Keys
- Key1: Entry No. (clustered)
- Key2: API Publisher, API Group, Description
Pages and codeunits on this table
- Page 812 “API Overview” (source table)
Recent changes
- 2026-08-20 #10008 [MCP] Add codeunit APIs as MCP tools in MCP configuration (main, BC30, feature)
- 2026-07-14 #9194 Add API Overview page (page 812) (main, BC30, feature, added)
Ask your agent
Procedure bodies are not stored here (D10). For a procedure body or the calls of one procedure, ask bc-code-atlas (external, by Stefan Maron, MIT; default corpus w1-28), which the bc-observatory plugin connects: bcatlas_resolve_node(object_type: "table", object_name: "API Overview Buffer"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.