Properties
| Name | Type | Description |
|---|---|---|
| version | string | The build version string (CFBundleVersion) |
| uploadedDate | string | The date and time the build was uploaded |
| expirationDate | string | The date and time the build expires |
| expired | boolean | Whether the build has expired |
| minOsVersion | string | The minimum OS version required |
| lsMinimumSystemVersion | string | The minimum macOS system version |
| computedMinMacOsVersion | string | The computed minimum macOS version |
| iconAssetToken | object | Token for the build's icon asset |
| processingState | string | The processing state of the build |
| buildAudienceType | string | The audience type for the build |
| usesNonExemptEncryption | ['boolean', 'null'] | Whether the build uses non-exempt encryption |
JSON Schema
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"title": "BuildAttributes",
"type": "object",
"properties": {
"version": {
"type": "string",
"description": "The build version string (CFBundleVersion)"
},
"uploadedDate": {
"type": "string",
"description": "The date and time the build was uploaded"
},
"expirationDate": {
"type": "string",
"description": "The date and time the build expires"
},
"expired": {
"type": "boolean",
"description": "Whether the build has expired"
},
"minOsVersion": {
"type": "string",
"description": "The minimum OS version required"
},
"lsMinimumSystemVersion": {
"type": "string",
"description": "The minimum macOS system version"
},
"computedMinMacOsVersion": {
"type": "string",
"description": "The computed minimum macOS version"
},
"iconAssetToken": {
"type": "object",
"description": "Token for the build's icon asset"
},
"processingState": {
"type": "string",
"description": "The processing state of the build"
},
"buildAudienceType": {
"type": "string",
"description": "The audience type for the build"
},
"usesNonExemptEncryption": {
"type": "['boolean', 'null']",
"description": "Whether the build uses non-exempt encryption"
}
}
}
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/app-store-connect-build-attributes"
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.