Benchmark Email · Schema
Contact
An email contact (subscriber) in Benchmark Email.
Email MarketingCampaignsContactsAutomationTransactional EmailMarketingListSegmentationReportingDeliverabilitySending DomainsEmail TemplatesWebhookAgent Ready
Properties
| Name | Type | Description |
|---|---|---|
| ContactID | integer | Unique identifier for the contact. |
| string | Email address of the contact. | |
| FirstName | string | First name of the contact. |
| LastName | string | Last name of the contact. |
| Status | string | Subscription status of the contact. |
| SubscribeDate | string | Date and time when the contact subscribed. |
| UnsubscribeDate | string | Date and time when the contact unsubscribed, if applicable. |
| CustomFields | object | Custom field values for the contact. |
JSON Schema
{
"$schema": "http://json-schema.org/draft-07/schema#",
"$id": "https://raw.githubusercontent.com/api-evangelist/benchmark-email/main/json-schema/contact.json",
"title": "Contact",
"description": "An email contact (subscriber) in Benchmark Email.",
"type": "object",
"properties": {
"ContactID": {
"type": "integer",
"description": "Unique identifier for the contact."
},
"Email": {
"type": "string",
"format": "email",
"description": "Email address of the contact."
},
"FirstName": {
"type": "string",
"description": "First name of the contact."
},
"LastName": {
"type": "string",
"description": "Last name of the contact."
},
"Status": {
"type": "string",
"enum": ["Active", "Unsubscribed", "Bounced", "DNC"],
"description": "Subscription status of the contact."
},
"SubscribeDate": {
"type": "string",
"format": "date-time",
"description": "Date and time when the contact subscribed."
},
"UnsubscribeDate": {
"type": "string",
"format": "date-time",
"description": "Date and time when the contact unsubscribed, if applicable."
},
"CustomFields": {
"type": "object",
"additionalProperties": {
"type": "string"
},
"description": "Custom field values for the contact."
}
},
"required": ["Email"]
}
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/contact"
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.