Restaurant365 · Schema
Employee
An employee record exposed by the Restaurant365 OData connector Employee view.
RestaurantAccountingInventoryInvoicesReportingOData
Properties
| Name | Type | Description |
|---|---|---|
| employeeId | string | |
| fullName | string | |
| firstName | string | |
| middleName | string | |
| lastName | string | |
| address1 | string | |
| address2 | string | |
| city | string | |
| state | string | |
| zipCode | string | |
| string | ||
| phoneNumber | string | |
| mobilePhone | string | |
| hireDate | string | |
| payrollID | string | |
| posid | string | |
| primaryLocation_id | string | |
| inactive | boolean | |
| createdBy | string | |
| createdOn | string | |
| modifiedBy | string | |
| modifiedOn | string |
JSON Schema
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"$id": "https://raw.githubusercontent.com/api-evangelist/restaurant365/main/json-schema/odata-connector-employee-schema.json",
"title": "Employee",
"description": "An employee record exposed by the Restaurant365 OData connector Employee view.",
"type": "object",
"properties": {
"employeeId": { "type": "string", "format": "uuid" },
"fullName": { "type": "string" },
"firstName": { "type": "string" },
"middleName": { "type": "string" },
"lastName": { "type": "string" },
"address1": { "type": "string" },
"address2": { "type": "string" },
"city": { "type": "string" },
"state": { "type": "string" },
"zipCode": { "type": "string" },
"email": { "type": "string", "format": "email" },
"phoneNumber": { "type": "string" },
"mobilePhone": { "type": "string" },
"hireDate": { "type": "string", "format": "date-time" },
"payrollID": { "type": "string" },
"posid": { "type": "string" },
"primaryLocation_id": { "type": "string", "format": "uuid" },
"inactive": { "type": "boolean" },
"createdBy": { "type": "string" },
"createdOn": { "type": "string", "format": "date-time" },
"modifiedBy": { "type": "string" },
"modifiedOn": { "type": "string", "format": "date-time" }
}
}
Work with this as data
Every JSON Schema here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for schemas
4 MCP tools reach this
find_json_schemasBrowse and filter every JSON Schema in the catalog.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
This JSON Schema
curl "https://apis.io/api/v1/json-schemas/odata-connector-employee"
All schemas
curl "https://apis.io/api/v1/json-schemas?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.