Integrations

Image Manipulation API

The Image Manipulation API provides a simple but efficient method of handling images stored in the system, and is integrated together with our content delivery network to ensure the best performance. width or w Specifies the width of the image. If not also specifying the height, the image aspect ratio is preserved. height or h Specifies the height of the image. If not also specifying the width, the image aspect ratio is preserved. dpr The device pixel ratio makes it easier to specify higher DPI sizes. Default is 1. fit or f Affects the interpretation of width and hight, and all modes preserve the aspect ratio. Available options: - scale-down The image will be resized (shrunked) to fit fully within the given width or height. - contain The image will be resized (shrunked or enlarged) to be as large as possible within the given width/height. - cover The image will be resized (shrunked or enlarged) to fill the entire width/height, and may be cropped. - crop The image will be resized (shrunked) and cropped to fit within the area specified by width and height. This mode provides the same result as scale-down if the image is smaller than the given dimentions. For images larger than the given dimentions, it's the same as cover. The image will not be enlarged. quality or q Specifies the compression level for images in various formats. The most used values usually range between 50 (low quality, small file size) and 90 (high quality, large file size). Values between 1-100 accepted. Default is 85. webp WebP is a modern image format that provides very good lossless and lossy compression for images. This feature is only available for browsers with built in WebP support, but is backwards compatible with old browsers. The feature is enabled by default. To disable, set to off. sharpen or s Specifies the strength of the sharpening filter. Values between 1-10 accepted, recommended value is 0.5. overlay_url or ourl Specifies the absolute url used for the overlay. It can be any of the accepted file formats, including SVG. overlay_opacity or oo Specifies the opacity of the overlay. Values between 0 (transparent) and 1 (opaque) accepted. overlay_position or op Specifies the position of the overlay. Accepted values are center, top, bottom, left, right, top-left, top-right, bottom-left and bottom-right. Other positioning options will be ignored if this option is set. overlay_top or op Specifies the position of the overlay from the top. This option can't be used together with overlay_bottom. overlay_bottom or ob Specifies the position of the overlay from the bottom. This option can't be used together with overlay_top. overlay_left or ol Specifies the position of the overlay from the left. This option can't be used together with overlay_right. overlay_right or or Specifies the position of the overlay from the right. This option can't be used together with overlay_left. overlay_rotate Specifies the degrees to rotate the overlay. Accepted values are 90, 180 and 270. overlay_repeat The overlay image will be tiled to cover the entire area. Accepted values are x (tiled horizontally) or y (tiled vertically). It can also partially cover an image, when used together with a positioning value. signature or sign A signature is required in order to change any of these options in the URL. The signature should be generated as a sha256 hash, that consists of all the options and their values, together with a secret key available on your account. Requests without a valid signature will return a HTTP 403 Forbidden error.

Synchronize properties to your Facebook catalog

Utilizing the Facebook Catalog, real estate agents can publish property listings directly on your Facebook page and create targeted ads for higher conversion. This approach increases property exposure to a wider audience, and can also redirect traffic to your website. Before you begin - Create a Facebook Page for your business if you don't have one yet. - Create a business portfolio in Business Manager so you can assign your catalog to your business. Make sure you have full control of the business portfolio. Note: The Meta Business Account, sometimes called a Business Manager account, is being renamed to business portfolio. This change will appear gradually across Meta technologies. Create a catalog 1. Go to Commerce Manager. 2. Start creating your catalog: - If this will be your first catalog, click Get started. Select Create a Catalog and then click Get started. - If you already have at least one catalog, you'll see all your catalogs listed. Select + Add catalog to create a new one. 3. Select the catalog type Products and click Next. 4. Select the business portfolio that you want your catalog to belong to. To select a business portfolio, you must have full control of it. 5. Enter a name for your catalog. 6. Click Create. Upload property data from Estatebud to your catalog 1. Go to Commerce Manager and select your catalog. 2. Open the Catalog tab and go to Data sources. 3. Click Add items and select Data feed from the list. If needed, click Next. 4. Choose how to upload your file: Use a URL or Google Sheets: To obtain the XML feed from Estatebud, go to Admin → Integrations → Plugins → Facebook and copy the XML Feed URL. 5. Click Next. 6. In the pop-up window, name your data feed and select the default currency to use if any prices in your feed are missing a currency code. 7. Choose an hourly, daily or weekly upload schedule. We recommend to update your Facebook catalog every 6 hours, as this ensures your catalog receives your latest updates promptly. 8. Click Upload. You’ve uploaded a new data feed. Your feed now appears in Data sources. Click on it at any time to see an overview or manage its settings.

Synchronize leads from Zapier

Create a new Zap 1. Sign in to your account and go to My Zaps. 2. Click Create and select New Zap. 3. Select the trigger source (such as Facebook Lead Ads, if you want to sync leads from Facebook) and select the correct trigger event and form if necessary. 4. Change Action to Webhooks by Zapier. 5. Change Action event to POST and click Continue. 6. Set URL to the desired Estatebud API endpoint, such as https://v1.estatebud.com/v1/newDeal?pipeline_id=x&stage_id=y. Make sure to change the pipeline_id and stage_id to values that reflect your configuration. Please refer to the API documentation for a comprehensive documentation of all available endpoints. 7. Set Payload Type to json. 8. Modify the Data parameters to populate data from the selected trigger source. Only the required fields are necessary, but we recommend to populate all the data you have available. Please refer to the API documentation for a comprehensive documentation of the payload. name (required) = The name of the lead. email (required) = Lead email address. phone = Lead phone number. mobile = Lead mobile number. note = A note attached to the deal. title = A title of the deal. value = The anticipated value or budget of the lead. currency = The currency of the value (defaults to your account settings). property_id = Comma-separated list of property IDs, if applicable. 9. Make sure Wrap Request In Array is set to No. 10. Generate an API key from Estatebud via Admin → Integrations → API, use a helpful reference like "Zapier" to remember where the key is used. Add your API key as Basic Auth, prefixed by Bearer. Example: Bearer E3FYHCST3DTFQXKOPKPGLQMEIFQKNHL6. 11. Press continue to test the Zap to make sure data flows correctly, with the expected records being created in your CRM. Make sure your Zap is activated, so that it continues to synchronize data after you have completed the test procedure.