Zembra API Documentation

Zembra RESTful API supports common HTTP verbs and returns JSON-formatted responses with common HTTP status codes.

## Sections
• [Search and Get Pricing by Query String](https://docs.zembra.io/accommodation/search-and-get-pricing-by-query-string.md)
• [Get Pricing by Property ID](https://docs.zembra.io/accommodation/get-pricing-by-property-id.md)
• [Get Property Pricing by Date Range](https://docs.zembra.io/accommodation/get-property-pricing-by-date-range.md)
• [Get Account Summary](https://docs.zembra.io/account/get-account-summary.md)
• [Create Batch](https://docs.zembra.io/batch/create-batch.md): Instead of running parallel requests or looping over your records and submitting one request at a time, you can choose to submit up to 1,000 requests in bulk. The server will pre-validate the inputs and accept all valid requests from the batch. Every request included in the batch will be processed and its result stored and if applicable delivered to your listeners. You can always retrieve the output of each request individually. To prevent congestion, you can only submit 1 batch per minute. Same options from the original endpoint can be used. Example, for [POST] /batch/listing/details your payload will look like this [{"network": "google", "slug": "my-listing"}] . Below is the mapping of batch endpoints to regular endpoints: Batch Endpoint Original Endpoint /batch/listing/details [GET] /listing/{network} /batch/listing/find [GET] /listing/find /batch/listing/match [GET] /listing/match /batch/reviews [POST] /reviews /batch/reviews-trigger [PUT] /reviews /batch/social/details [POST] /social/{network}/{resource}/{slug} /batch/social/job [POST] /social/job/{network}/{resource}/{slug}/{content} /batch/social/subscription [POST] /social/subscription/{network}/{resource}/{slug}/{content}
• [Get Batch Status](https://docs.zembra.io/batch/get-batch-status.md)
• [Get Batch Entry Result](https://docs.zembra.io/batch/get-batch-entry-result.md)
• [Get Batch List](https://docs.zembra.io/batch/get-batch-list.md)
• [Listing Details](https://docs.zembra.io/listing/listing-details.md)
• [Listings Lookup](https://docs.zembra.io/listing/listings-lookup.md)
• [Listing Match](https://docs.zembra.io/listing/listing-match.md)
• [Create Review Job](https://docs.zembra.io/reviews/create-review-job.md): Creates a new job to pull review data from the requested review page. The response will also include the listing’s information. You can set your preferred level of monitoring: None (default): This means that monitoring will not be enabled, i.e. reviews will not maintained up to date. We will return a fresh snapshot of the reviews without sourcing from our cached data. Data retention is set to 5 days. The cost per job is 50 credits + 1 credit per returned review. With this type of monitoring, you can set a sizeLimit and/or dateLimit (whichever comes first) to limit the number of returned reviews and consequently the cost. This type of jobs cannot be set for auto-renewal. Basic : All the reviews are immediately made available once crawling is completed. Updates and fetching of new reviews is once every 30 days. The cost of this type of jobs is 75 credits + 3 credits per returned review. You can set this job to auto-renew. The cost of an auto-renewed job is 50 credits + 3 credits per returned new reviews. You do not get charged twice for an existing and previously returned review. You cannot set limits of any kind on this type of jobs. The original listing although it is included in the response, it is not guaranteed to be up to date. Edits, replies, deletions, restorations, and any changes affecting existing reviews are not guaranteed to be applied. The main purpose of this monitoring style is to ensure collecting new reviews on a monthly basis. This job remains active for 30 days. Regular : All the reviews are immediately made available once crawling is completed. Updates and fetching of new reviews is once a day. The cost of this type of jobs is 125 credits + 3 credits per returned review. You can set this job to auto-renew. The cost of an auto-renewed job is 75 credits + 3 credits per returned new reviews. You do not get charged twice for an existing and previously returned review. You cannot set limits of any kind on this type of jobs. The original listing although it is included in the response, it is not guaranteed to be up to date. Edits, replies, deletions, restorations, and any changes affecting existing reviews are not guaranteed to be applied. The main purpose of this monitoring style is to ensure collecting new reviews on a daily basis. This job remains active for 30 days. Full : The recommended monitoring level for online reputation management activities. The initial pull is processed through a priority queue to ensure minimum delay before delivery. Updates and fetching of new reviews are as frequent as the activity on the target listing with a guarantee of a maximum rest time of 8-12 hours (depends on the platform). The cost of this type of jobs is 150 credits + 1 credit per returned review. You can set this job to auto-renew. The cost of an auto-renewed job is 100 credits + 1 credit per returned reviews. You will be charged for all the reviews in each cycle because we are closely monitoring all the reviews. You will also receive updates for any affected existing review regardless of when it was initially pulled. You cannot set limits of any kind on this type of jobs. The original listing is kept up to date. This job remains active for 30 days. Please note that all jobs with any kind of monitoring enabled will cause the pull of the entire set of reviews. Having a track of the reviews is crucial for our monitoring and collision detection process. All monitoring jobs remain valid for 30 days. If you desire to change the monitoring level, you must cancel the existing job then create a new job with the new monitoring level. You will lose all the previous data and you will be charged again for the new job independently from the history. There cannot be two active jobs with monitoring enabled. If you use a different slug for the same listing it will result in the same job being returned and no new job will be created. The review fetching starts promptly after creation and data is made available a few seconds later. If you have an endpoint listening to our webhook callback, expect the signal to be issued within a few seconds from the original request.
• [Get Reviews](https://docs.zembra.io/reviews/get-reviews.md)
• [Update Review Job](https://docs.zembra.io/reviews/update-review-job.md)
• [Trigger Reviews Fetch](https://docs.zembra.io/reviews/trigger-reviews-fetch.md)
• [Delete Review Job](https://docs.zembra.io/reviews/delete-review-job.md)
• [Get Review Jobs List](https://docs.zembra.io/reviews/get-review-jobs-list.md)
• [Get Social Media Resource Details](https://docs.zembra.io/social-media/get-social-media-resource-details.md)
• [Create Social Media Job](https://docs.zembra.io/social-media/create-social-media-job.md)
• [Get Contents by job ID](https://docs.zembra.io/social-media/get-contents-by-job-id.md)
• [Get Social Media Jobs List](https://docs.zembra.io/social-media/get-social-media-jobs-list.md)
• [Get Contents by Slug](https://docs.zembra.io/social-media/get-contents-by-slug.md)
• [Create Social Media Subscription](https://docs.zembra.io/social-media/create-social-media-subscription.md)
• [Update Social Media Subscription by Slug](https://docs.zembra.io/social-media/update-social-media-subscription-by-slug.md)
• [Delete Social Media Subscription by Slug](https://docs.zembra.io/social-media/delete-social-media-subscription-by-slug.md)
• [Get Social Media Subscriptions List](https://docs.zembra.io/social-media/get-social-media-subscriptions-list.md)
• [Get Platforms Status](https://docs.zembra.io/status/get-platforms-status.md)