Data Service Response

🧩 What is the Data Response?

This section explains the structure of the response sent to your webhook after a successful bulk request is processed. Every Bulk Request you send to bulk.easyparser.com will return its results asynchronously to your specified callback_url.

While the structure of the response remains consistent, the content inside may differ depending on the operation type — e.g., SEARCH, DETAIL, OFFER, PRODUCT_SEARCH, and others.

triangle-exclamation

📌Data Availability Reminder

🔍 Understanding the Response

A typical webhook response includes the following top-level fields:

Field
Type
Description

success

Boolean

Indicates whether the request was successful.

data

Object

Contains the core payload and result content.

📦 data Object

Field
Type
Description

callback_url

String

The webhook URL to which the response is sent.

payload

Object

The original payload you submitted (e.g., ASINs or a search URL).

domain

String

Domain of the requested marketplace (e.g., .com, .de, .co.uk).

id

UUID

Unique identifier for this query.

operation

String

The type of operation executed (SEARCH, DETAIL, OFFER, etc.).

platform

String

Target platform code (e.g., AMZ).

status

String

Overall processing status (success, failed, etc.).

json_result

Object

Parsed result and metadata for the completed request.

🧩 Breakdown of json_result Object

This object holds the parsed response for the given operation and useful metadata about the process.

📄 result

Contains the raw extracted data based on the operation type (e.g., SEARCH, DETAIL, etc.). This is the core part users will consume. The structure of this section varies by operation. For example:

  • SEARCH: List of product search results

  • DETAIL: Detailed product information

  • OFFER: Offers and seller data

  • PRODUCT SEARCH: Contextual search results based on product keywords

...and more

circle-info

📌 For a quick overview of each operation’s result structure, including visual examples and deep links to detailed documentation, please refer to the Getting Startedarrow-up-right page.

📊 request_metadata

The request_metadata object provides contextual metadata about the request process, including pagination information, processing time (in milliseconds), and result counts. This data is especially useful for multi page or list based operations, such as SEARCH.

🧾 request_info

Technical details of the request, including HTTP status code, regional address (e.g., ZIP codes), any errors, and internal tracking IDs. Helpful for debugging or validating result integrity.

Field
Type
Description

status_code

Int

HTTP status code returned from the fetch process

address

Object

Shipping ZIP codes or location information (if applicable)

error_details

Array

List of any errors encountered during parsing

success

Boolean

Indicates whether the result was parsed successfully

id

UUID

Same query ID for tracking and re-fetching purposes

👉Example JSON Output

The following response is a sample result retrieved by making a Data Service Requestarrow-up-right using the id returned from a previous Bulk Service Requestarrow-up-right.

Please note that the structure of the json_result.result field may vary depending on the operation type (e.g., SEARCH, DETAIL, OFFER, PRODUCT LOOKUP, etc.). This portion contains the raw parsed data specific to the operation, while other fields such as request_metadata and request_info provide contextual and diagnostic information.

chevron-rightExample DETAIL Operation Responsehashtag

✅ Wrapping Up

You've now seen how to retrieve and interpret results using the Data Service, following a successful bulk submission. With the provided id, you can fetch the parsed content and start utilizing it in your application workflows.

To ensure a smooth integration:

  • Refer back to operation-specific documentation for interpreting the json_result contents.

  • Store results promptly, as response data is kept up to a maximum of 24 hours.

  • Stay mindful of your credit usage and response statuses to keep your requests optimized.

Need more details or examples? You can always revisit the Getting Startedarrow-up-right section or explore individual operation pages for deeper insights.

Happy parsing! 🚀

Last updated