Giraffe360 API: Projects, Media, Leads and Webhooks for Your Own Systems

Your company keeps its listings in a system of its own, and each new property gets a Giraffe360 shoot. The Giraffe360 API lets that system work with Giraffe360 directly. It can tell Giraffe360 about your listings, hear when a project matching one of them is ready, and fetch that project's media and the leads it brings in. Your system then has the photos, floor plans, tours and enquiries for each listing without anyone downloading them from the dashboard.

Before Your Developers Write Any Code

The documentation is public at developers.giraffe360.com, with every endpoint and examples of what it takes and returns, so your developers can plan the work before your account is connected. To call the API they need an authentication token for your account, which our customer success team issues when you ask. Each request then goes to api.giraffe360.com with that token in its Authorization header, after the word Bearer.

When a Listing Is Created on Your Side

With the token in place, the first step is to tell Giraffe360 about your listings. The External Listing API registers each one under your own reference ID, with its address, a building ID or a land ID, its floor and its number of rooms. A listing is active or inactive, and later your system can change that status.

In Giraffe360, your team links a project to one of those listings by entering its reference on the project, under Add integration and then External Listing, where your workspace offers it. Once the project has been matched and confirmed against your listing, a project-matched webhook tells your system, with the project's ID and your reference ID.

When the Project Is Ready

The next message comes when the shoot's content is done. A project-ready webhook fires once the project finishes processing, and your system can ask the Project API for that project. The answer holds its media as links: still photos and AI still photos, floor plans, 3D floor plans and AI floor plans, panoramas, virtual tours and videos, and the point clouds and merged point clouds where the project has point cloud access.

Virtual tours come in the version each was published as. That can be the standard tour, the one made for listing sites, or the gated tour that asks viewers to verify their email. Only published tours are returned, and the listing site and gated versions start unpublished, so publish the ones your listings use in the dashboard first. Your system can also list projects by camera, by a user's email or ID, or by a word in the project's name.

When a Buyer Gets in Touch

Once the tour is live, enquiries start to come back through the Lead API. It returns the leads from a project's virtual tours, its Property Website and your Agent Website, with each person's name, email, phone number and message, and the gated tour viewers who verified their email. Your system can ask for one project's leads, for one source or for a date range, or subscribe to the lead-created webhook and get each new lead's ID as it is created.

When Your Team Changes

Your team changes over time, and the API handles that side as well. The User API adds a user with a name, an email and the role basic or manager, updates their details, and deletes a user for good. It can't make anyone an admin or change an admin's role. The Camera API shows which users each camera has and assigns or unassigns them, and the Project API does the same for a project, where assigning a user can also give or take away the right to edit it.