Discover the professional world – delve into detailed profiles and connections with Fusionbase's Person Search.
The Person Search Endpoint is a specialized tool designed for retrieving detailed personal profiles from official business registry sources. This powerful endpoint is essential for applications requiring in-depth information about individuals, particularly in business contexts, such as their roles in organizations, location, and professional relationships. It is a valuable resource for developers building applications for business intelligence, network analysis, or compliance purposes.
To search for an individual, a GET request is made to the Person Search Endpoint. This endpoint accepts the person's name or other identifiers as query parameters. It returns a JSON object with comprehensive personal data, extracted exclusively from official business registry sources.
Request Example:
It is important to URL encode the query parameter to ensure proper request formatting.
The API response is a JSON object with an array under the results key, where each entry represents a person entity. The response includes detailed personal information such as the Fusionbase entity ID, name, location, organizational affiliations, and more.
Here’s a simplified example based on the provided response:
results: An array of person entities matching the search query.
entity_type: Specifies the type of the entity, here "PERSON".
entity: Contains the detailed information about the person.
fb_entity_id: A unique identifier for the person within the Fusionbase Data Hub.
name: The individual’s name, including given and family names.
locations: Information about the person's location, such as home address.
relations: Details of the individual’s affiliations or roles in organizations, including position labels and related organization details.
source_id: The source identifier from which the data is derived.
score: A relevance score for the search result.
The Person Search Endpoint is a powerful tool for developers to access rich, verified personal data. The unique fb_entity_id enables developers to reference specific individuals consistently within the Fusionbase ecosystem. This capability is crucial for applications that require tracking of individual profiles over time, understanding their business network, or conducting due diligence. The endpoint's comprehensive data set provides a solid foundation for sophisticated applications requiring reliable and detailed personal information.
Navigate the corporate landscape – uncover comprehensive organizational data with Fusionbase's Organization Search.
The Organization Search Endpoint is a dynamic solution for searching organizational data and extracting specific business information. This endpoint is ideal for applications requiring detailed information about various organizations. It provides robust data for developers building applications that require comprehensive business information, such as company names, statuses, addresses, and registration details.
To search for an organization, a GET request is made to the Organization Search Endpoint. The endpoint accepts the organization's name or other identifying details as query parameters. In response, it returns a JSON object containing detailed information about the organization, including its status, address, registration details, and more.
Request Example:
Remember to URL encode the query parameter for proper request formatting.
The API returns a JSON object containing an array under the results key, each entry corresponding to a found organization. For a given query, the response includes details like the Fusionbase entity ID, organization status, address, and registration authority.
Here’s a simplified example based on the provided response:
results: Contains an array of organization entities matching the search query.
entity_type: Indicates the type of the entity, here "ORGANIZATION".
entity: Contains detailed information about the organization.
fb_entity_id: A unique identifier for the organization within Fusionbase Data Hub.
status: Indicates the current status of the organization (e.g., Active, Inactive).
display_address: The public address of the organization.
registration_authority_entity_name: The name of the authority under which the organization is registered.
display_name: The public name of the organization.
name: Official registered name of the organization.
source_key: A unique key from the data source.
score: A relevance score for the search result.
The fb_entity_id is vital for developers as it allows for consistent referencing of a specific organization within the Fusionbase ecosystem. This unique ID enables the retrieval of more detailed information and supports various operations, such as tracking changes in the organization's status or retrieving related financial or operational data. By leveraging this ID, developers can access a wealth of information to enrich their applications and analyses with in-depth organizational data.
Pinpoint Precision: Explore and Geocode with Ease
The Location Search Endpoint is your comprehensive solution for place searches and address geocoding, akin to the functionality of Google Maps Places Search. Whether you're plotting points of interest or transforming addresses into coordinated data, this endpoint delivers accurate, map-ready results. It's the developer's tool of choice for creating location-aware applications with high precision and reliability.
To geocode an address such as "Agnes-Pockels-Bogen 1, 80992 München", you would make a GET request to the Location Search Endpoint. The endpoint takes the address as a query parameter and returns a JSON object with the geocoded location details, including latitude and longitude coordinates.
Request Example:
Make sure to URL encode the query parameter to ensure the request is properly formatted.
Expected Response:
The API's response will be a JSON object containing an array under the results key. Each entry in this array corresponds to a found location. For the provided address, the response includes the Fusionbase entity ID, creation and update timestamps, the entity version, and external identifiers such as OpenStreetMap data. Most importantly, it contains the coordinate object with latitude and longitude keys, providing the precise geocoded location.
Here's a structured example based on the provided response:
The search result from the Fusionbase Location Search Endpoint provides a structured JSON object containing detailed information about the queried location. Here's how the result is organized and how it can be utilized:
results: This is an array that contains one or more location entities that match the search query. In the provided example, there is one matching location entity for the address "Agnes-Pockels-Bogen 1, 80992 München".
entity: Within each item in the results array, the entity object holds the data for thelocation. This includes unique identifiers, timestamps, and structured location information.
fb_entity_id: This is a crucial element as it uniquely identifies the location within the Fusionbase Data Hub. It's used to reference this specific location in subsequent API calls or to cross-reference within the Fusionbase ecosystem.
coordinate: The latitude and longitude values provide the geocoded coordinates of the address, which can be used for placing markers on a map, calculating distances, or other geospatial operations.
address_components: This array breaks down the address into individual components such as house_number, street, postal_code, city, state, and country. This granular information is useful for applications that need to process or display parts of an address separately.
formatted_address: A human-readable address string that combines all address components, suitable for display purposes.
The fb_entity_id is a key identifier that developers can utilize to maintain a durable reference to a specific location. It allows for the retrieval of extended details and facilitates the execution of further operations, such as resolving relations for the given location within the Fusionbase Data Hub. By leveraging this ID, developers can access related statistical indicators like household income, demographic distributions, or other socio-economic data points associated with that location, thus providing a richer and more detailed data narrative for applications and analyses.
Master the Fusionbase Data Hub Search API with our concise guide. Detailed instructions and examples ensure easy integration and powerful search use.
The Fusionbase Data Hub Search API is tailored for developers seeking to harness a wealth of data for various applications. This robust API simplifies access to a diverse range of data entities, each offering unique insights and opportunities for integration:
Data Streams: Access real-time and historical datasets encompassing areas like statistics, environmental data, and public records. Ideal for applications in analytics, trend monitoring, and data-driven decision-making.
Data Services: Discover APIs and services for data processing and analytics. These services are crucial for enhancing data quality, interpretation, and application in your projects.
Organizations: Explore detailed information about companies, going beyond mere registry data to include insights into business operations, market presence, and industry standing. This entity is invaluable for market analysis, competitive intelligence, and B2B solutions.
Persons: Access official records of individuals in professional contexts, specifically those associated with organizations. This data is essential for network analysis, professional background checks, and organizational research.
Locations: Utilize comprehensive geographical and locational data, useful for mapping, logistics planning, and geographical analysis.
Relations: Investigate the connections between different entities, providing a deeper understanding of organizational networks, geographical correlations, and data context.
Search Endpoints:
Fusion Search Endpoint: An AI-driven, comprehensive search across all entities, ideal for broad queries where user intent is analyzed and results are ranked accordingly. This endpoint is particularly useful when the search context is not entity-specific and a holistic view is desired.
Entity-Specific Endpoints:
Streams and Services Endpoint: Focuses on datasets and data-related services, suitable for applications needing specific data types or analytics services.
Organizations Endpoint: Dedicated to detailed company information, perfect for business intelligence and market research.
Persons Endpoint: Targets professional profiles and official records, ideal for background checks and professional network analysis.
Location Endpoint: For location-specific searches, offering detailed geographical data.
Relations Endpoint: Explores inter-entity connections, enhancing data context and network understanding.
Practical Application and Integration:
As a developer, you can expect the Fusionbase Data Hub Search API to be a reliable and comprehensive source for various types of data. Whether your project involves creating sophisticated market analysis tools, developing rich data visualizations, or integrating background information into professional networking platforms, this API provides the necessary data foundation.
The Fusionbase Data Hub is designed with the developer in mind, ensuring ease of integration, consistent data quality, and a wide range of data types to meet diverse application needs. By incorporating this API into your projects, you can significantly enhance your application's capabilities, offering users deeper insights and more valuable experiences.
Efficient, Targeted Data and Service Discovery
The Streams & Services Search Endpoint is a specialized API endpoint designed to streamline searches specifically for Data Streams and Data Services within the Fusionbase Data Hub. It efficiently narrows down results to these two categories, delivering precise data sets and related services. Perfect for developers who need to target their search for datasets, like statistics or environmental data, and services that complement data processing and analytics, providing a focused and detailed data selection.
GET https://api.fusionbase.com/api/v2/search/data?q=<QUERY>
| Name | Type | Description |
|---|---|---|
To assist with integrating the Streams & Services Search API into your application, we provide examples in various programming languages. Each example illustrates how to execute a properly encoded GET request to the API. Remember to replace <QUERY> with your URL-encoded search query and YOUR_API_KEY with the actual API key provided to you.
These code snippets provide a template for making a GET request to the Streams & Services Search endpoint of the Fusionbase Data Hub API. By encoding the query parameter, you ensure that the request is correctly formatted and can be processed efficiently by the API.
AI-Enhanced, Comprehensive Data Discovery
The Fusion Search Endpoint is an AI-enhanced API endpoint offering comprehensive searches across all Fusionbase Data Hub entities. It adeptly interprets user intent to deliver relevant, ranked results and, where applicable, knowledge graphs. Ideal for developers requiring an overarching, context-rich data overview.
GET https://api.fusionbase.com/api/v2/search/fusion?q={QUERY}
Search accross all Fusionbase data entities with a single query.
| Name | Type | Description |
|---|---|---|
The Fusion Search API response primarily consists of a results section, categorizing matched entities like organizations, persons, and streams with detailed information. When applicable, a knowledge_graph is included, offering direct answers to the query, and a ranks list details the relevance order of entity types.
To help you integrate the Fusion Search API into your application, we provide examples in various programming languages. Each example demonstrates how to make a properly encoded GET request to the API. Ensure you replace <QUERY> with your URL-encoded search query and YOUR_API_KEY with your actual API key.
Each code snippet is an example of how to call the Fusion Search API in a specific programming language, ensuring the query is correctly URL-encoded to maintain the integrity of the request.
q
String
This parameter accepts the user's search string, defining the specific data or information to be retrieved by the Data Search Endpoint.
q
String
This parameter accepts the user's search string, defining the specific data or information to be retrieved by the Fusion Search Endpoint.