What We Do

DataParse specializes in parsing data from websites for our users. We collect, structure, and deliver data in a ready-to-use format.

We have ready-made parsers available, and we also build custom parsers tailored to each client's specific task.

  • Ready parsers: access to existing sources after agreement.
  • Custom parser: if the needed source isn't available, we build it specifically for your task.
  • Support: we assist with launch and help integrate the API into your workflow.
In short: you describe your task, we provide access to the needed parser and set up data delivery.

How It Works

The process is simple: you contact us, we create an account and grant access to the needed parsers by agreement.

  1. Your request You contact us, provide your name, email, and describe in detail what data you need.
  2. Account creation We create an account for you and provide credentials so you can log into your dashboard.
  3. Terms agreement After agreement, we grant access to the specific parser you need.
  4. Other parsers visibility In your dashboard you can see other parsers we have, but without access to them.
  5. Access expansion Access to other parsers is also granted after separate agreement.
Important: parser access rights are assigned individually for each client and managed in your account.

API Request: PHP

Below is a minimal PHP example for calling GET /api/v1/parse only.

  • parser is passed as the parser name, not an ID.
  • Query parameter values are encoded via http_build_query.
  • For integration, api_token, parser, and region are sufficient.

API Request: Node.js

The example below shows only the GET /api/v1/parse call without additional endpoints.

  • Only the public parser call is used.
  • parser — a string with the parser name.
  • region is passed as a separate query parameter.

API Request: TypeScript

TypeScript version of the same GET /api/v1/parse call.

  • The parser parameter type is string.
  • The function returns HTTP status and JSON response.
  • No login or service endpoints in the example.
Recommendation: pass the parser name as a human-readable string.

API Request: NestJS

NestJS service example for a direct GET /api/v1/parse request.

  • The method accepts apiToken, parserName, and region.
  • Only parsing parameters are passed in the request.
  • Other endpoints are not used in the example.
Best practice for NestJS: add timeout and retry for network resilience.

API Request: React

A simple React hook for calling GET /api/v1/parse.

  • The call is made with a single parse function.
  • parserName is passed as a string.
  • State stores only the status and request result.

API Request: Vue 3

Composable for a single GET /api/v1/parse call.

  • The parse method accepts apiToken, parserName, and region.
  • Returns status and response body.
  • Login and other calls are absent from the example.
Best practice for Vue: validate that apiToken, parserName, and region are filled before making the request.

API Request Example

Below is a minimal call example made by a user with a personal api_token. The parser parameter contains the parser name.

Successful response example:

Access error response example:

Important: the token is unique for each user and only works within the agreed access scope.

Access & Restrictions

For each user we issue a separate account and individual API token. Parser access is configured on a per-client basis.

  • 1 free trial month: initial access is provided free for a limited period.
  • Access only to agreed parsers: only the parser connected to you is available.
  • Other parsers visible in dashboard: but without call access until separately agreed upon.
  • Access expansion: additional parsers and terms are connected after agreement with our team.

Privacy Policy

We process only the data necessary for registration, granting access, and supporting the service.

By using the website and API, you agree to data processing within this policy and applicable legislation.

  • What we collect: name, email, API service logs (time, status, technical request parameters), support request history.
  • Why: to create an account, grant parser access, ensure stable API operation and client support.
  • Retention period: only for the duration required for service delivery and legal obligations.
  • Third-party sharing: we do not share data with third parties except as required by contract or law.
  • User rights: request clarification, update, or deletion of data unless it contradicts mandatory legal requirements.
  • Cookies: we use technical cookies for authorization and proper interface operation.

For privacy questions, data deletion, or processing restrictions, contact us through the feedback form.