Endpoint response schemas
Use the field reference on each endpoint page to understand the payload before building your integration. The same definitions are published as JSON Schema and embedded in OpenAPI.
Validate the payload you actually receive
The schemas below describe optional 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.
Reviewed definitions document fields checked against a response shaper. Observed definitions describe captured shapes; a missing field in a capture does not mean that the endpoint can never return it. Neither category is an exhaustive field guarantee or a live availability test.
// 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
}Published endpoint coverage
634 public payload definitions are listed below: 183 reviewed against response shapers and 451 derived from observed response shapes. These are schema definitions, not a count of currently available operations. Check the endpoint catalogue for current registration, availability and prices. Examples are illustrative and abbreviated. MCP discovery supplies response_schema_provenance (reviewed or observed) and a null response_schema where no field contract is published.
Endpoint references are linked only where a current catalogue entry was found. An unlinked name still has a downloadable schema; it does not establish that retrieval is offered.
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.