Clover · Schema
Employee
Clover Employee resource. Schema derived from the Clover Platform REST API v3 reference.
RestaurantPoint-of-SalePaymentsRetailSMBHardware
Properties
| Name | Type | Description |
|---|---|---|
| id | string | Unique identifier |
| name | string | Full name of the employee |
| nickname | string | Nickname of the employee (shows up on receipts) |
| customId | string | Custom ID of the employee |
| string | Email of the employee (optional) | |
| inviteSent | boolean | Returns true if this employee was sent an invite to activate their account |
| claimedTime | integer | Timestamp of when this employee claimed their account |
| deletedTime | integer | Timestamp of when this employee was deleted |
| pin | string | Employee PIN (hashed) |
| unhashedPin | string | Employee PIN |
| role | string | Employee System Role |
| roles | array | |
| isOwner | boolean | Returns true if this employee is the owner account for this merchant |
| shifts | array | |
| payments | array | |
| orders | array | |
| employeeCards | array | |
| merchant | object |
JSON Schema
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"title": "Employee",
"description": "Clover Employee resource. Schema derived from the Clover Platform REST API v3 reference.",
"$id": "https://raw.githubusercontent.com/api-evangelist/clover/refs/heads/main/json-schema/platform-rest-api-employee-schema.json",
"type": "object",
"properties": {
"id": {
"type": "string",
"description": "Unique identifier",
"example": "9ABCDEF1234567"
},
"name": {
"type": "string",
"description": "Full name of the employee",
"example": "Example name"
},
"nickname": {
"type": "string",
"description": "Nickname of the employee (shows up on receipts)",
"example": "Example nickname"
},
"customId": {
"type": "string",
"description": "Custom ID of the employee",
"example": "9ABCDEF1234567"
},
"email": {
"type": "string",
"description": "Email of the employee (optional)",
"example": "merchant@example.com"
},
"inviteSent": {
"type": "boolean",
"description": "Returns true if this employee was sent an invite to activate their account",
"example": true
},
"claimedTime": {
"type": "integer",
"description": "Timestamp of when this employee claimed their account",
"example": 1718153645000
},
"deletedTime": {
"type": "integer",
"description": "Timestamp of when this employee was deleted",
"example": 1718153645000
},
"pin": {
"type": "string",
"description": "Employee PIN (hashed)",
"example": "example-pin"
},
"unhashedPin": {
"type": "string",
"description": "Employee PIN",
"example": "example-unhashedPin"
},
"role": {
"type": "string",
"description": "Employee System Role",
"enum": [
"OWNER",
"ADMIN",
"MANAGER",
"EMPLOYEE"
],
"example": "OWNER"
},
"roles": {
"type": "array",
"items": {
"type": "object"
},
"example": []
},
"isOwner": {
"type": "boolean",
"description": "Returns true if this employee is the owner account for this merchant",
"example": true
},
"shifts": {
"type": "array",
"items": {
"type": "object"
},
"example": []
},
"payments": {
"type": "array",
"items": {
"type": "object"
},
"example": []
},
"orders": {
"type": "array",
"items": {
"type": "object"
},
"example": []
},
"employeeCards": {
"type": "array",
"items": {
"type": "object"
},
"example": []
},
"merchant": {
"type": "object",
"example": {}
}
}
}
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/platform-rest-api-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.