Endpoint response schemas

Validate the payload you actually receive

The schemas below describe reviewed core fields of response.data, not the complete envelope. They use JSON Schema 2020-12. Field tables, illustrative examples, downloadable schemas and the corresponding OpenAPI 3.1 document share one definition.

Core fields are optional because sources can omit them. A type containing null also allows an explicit unknown value. Absence and null do not mean zero, false or an empty string. Nested objects have their own optional fields. Additional fields are allowed so an additive source field does not break your client.

Validation catches a known field with the wrong type. It does not prove freshness, completeness, availability or that a field your application needs was supplied. Add application-level checks for your own requirements, such as a usable post URL before requesting comments. Keep identifiers as strings, retain currency with money, and read each field’s units.

// npm install ajv
import Ajv2020 from 'ajv/dist/2020.js';
const schemaResponse = await fetch(
  'https://www.monocrawl.com/schemas/tiktok/profile.json'
);
if (!schemaResponse.ok) throw new Error('Schema unavailable');
const validate = new Ajv2020({ strict: false }).compile(await schemaResponse.json());
// response is the parsed envelope from your API request.
if (response.success && !validate(response.data)) {
  console.error(validate.errors); // field paths, not credentials or raw payloads
}

Reviewed endpoint coverage

68 endpoint payloads across 13 platforms are covered below, including social, professional-network, developer, app-store and commerce data. Examples are fictional and abbreviated. Endpoints outside this list retain the common envelope reference; these schemas do not claim to validate their payloads or every optional source extension. MCP discovery returns a null response_schema for endpoints without a reviewed field contract.

Keep a compatible schema snapshot

Save the schema version you validate against with your integration. New optional fields are additive; your parser should preserve or ignore unknown properties. Test representative populated, null and missing-field fixtures. Review changes before updating a pinned schema and follow the versioning policy.

For errors and accounting, use the response envelope. For partial, legs, warnings and cursor behavior, use pagination and caching. A valid payload can still contain a partial result.