Properties
| Name | Type | Description |
|---|---|---|
| Year | integer | The tax year for which the e-file is being processed. Must be a valid 4-digit year (e.g., 2024). |
| TaxType | string | Specifies the type of tax return being processed. 1040, 1041, 1065, 1120, 990, 5500, 709. |
| TaxReturnID | string | A 6-digit unique alphanumeric identifier for the specific tax return. This is also referred to as the Locator ID. |
| Jurisdiction | string | The state or local jurisdiction code where the tax is being filed. Example: AL for Alabama. Use the /v1/e-file-jurisdictions endpoint to retrieve valid codes. |
| EFileRequestType | string | Indicates the type of e-file request. This value is predefined for each jurisdiction. Example: Return. Use the /v1/e-file-jurisdictions endpoint to retrieve valid request types for each jurisdiction. |
JSON Schema
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"$id": "https://raw.githubusercontent.com/api-evangelist/thomson-reuters/main/json-schema/thomson-reuters-efile-request-schema.json",
"title": "EFileRequest",
"x-generated": "2026-10-20",
"x-method": "derived",
"x-generator": "derive-json-schema.py",
"x-source": "openapi/thomson-reuters-gosystem-e-file-api-openapi.yml#/components/schemas/EFileRequest",
"type": "object",
"properties": {
"Year": {
"format": "int32",
"type": "integer",
"description": "The tax year for which the e-file is being processed. Must be a valid 4-digit year (e.g., 2024)."
},
"TaxType": {
"type": "string",
"description": "Specifies the type of tax return being processed. 1040, 1041, 1065, 1120, 990, 5500, 709."
},
"TaxReturnID": {
"type": "string",
"description": "A 6-digit unique alphanumeric identifier for the specific tax return. This is also referred to as the Locator ID."
},
"Jurisdiction": {
"type": "string",
"description": "The state or local jurisdiction code where the tax is being filed. Example: AL for Alabama. Use the /v1/e-file-jurisdictions endpoint to retrieve valid codes."
},
"EFileRequestType": {
"type": "string",
"description": "Indicates the type of e-file request. This value is predefined for each jurisdiction. Example: Return. Use the /v1/e-file-jurisdictions endpoint to retrieve valid request types for each jurisdiction.",
"enum": [
"Return",
"Return2",
"Return3",
"Return4",
"Extension1",
"Extension2",
"Extension3",
"Extension4",
"Estimate",
"Estimate2",
"Estimate3",
"EXT_NY_IT204LL",
"RET_NY_IT204LL",
"Composite",
"Other",
"OtherExt",
"Withholding"
]
}
}
}
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/thomson-reuters-efile-request"
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.