Skip to main content

Sources

Discover available sources before creating a task. Listing returns the documented public source IDs in reference order, with one entry per source. Previously authorized IDs remain usable for direct schema reads and task creation. Catalog listing and schema reads require no authentication:

bash
curl 'https://api.datablist.com/v1/sources'


curl 'https://api.datablist.com/v1/sources/instagram-source'

Each definition contains @id, settingsSchema, outputSchema, and execution limits. Send @id as sourceId, validate settings against the returned schema, and use the output schema to understand generated objects. Sources have no inputSchema.

cost describes pricing in plain text, such as 1 credit per 150 URLs parsed. It is null when unavailable. This is pricing guidance rather than a numeric amount or spending guarantee; use the task's credits.used for actual usage.

The output schema lists known fields, but results can include extra fields before they appear in the catalog. Keep those fields when reading results.

Conditional settings and outputs​

Some fields have an enableOnSetting rule explaining when they apply. For example, scrapingType==followers,false applies in followers mode or when the setting is unset.

Fields stay listed when their condition is inactive. If you build a settings form, use the same rules as enrichments.

Conditions control which settings to show, not validation. Output conditions never remove fields from results. Extra settings are accepted. Sources have no input rows, so they have no conditional input requirements.

Documented sources​

Each source has different settings and outputs. Check its current definition and allow extra response fields. Read credits.used on the task for actual usage; the number of objects alone does not tell you the cost.