Skip to main content
POST
/
technologies
/
lookup
Look up a technology
curl --request POST \
  --url https://api.pubrio.com/technologies/lookup \
  --header 'Content-Type: application/json' \
  --header 'pubrio-api-key: <api-key>' \
  --data '
{
  "domain_search_id": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
  "domain": "pubrio.com",
  "linkedin_url": "https://www.linkedin.com/company/pubrio",
  "domain_id": 123,
  "profile_id": 123
}
'
{
  "data": [
    {
      "category_id": 1,
      "technologies": [
        {
          "icon": "Google Ads.svg",
          "name": "Google Ads",
          "tag_id": 4580,
          "version": null,
          "website": "https://ads.google.com/",
          "location": "pubrio.com",
          "logo_url": "https://buckets.pubrio.com/technology-logo/NDU4MGIyOXNtYjhheGdvb2dsZS1hZHM=.jpg",
          "last_detected": null,
          "first_detected": "2023-01-07T06:40:56.597287"
        }
      ],
      "category_name": "Advertising"
    },
    "..."
  ]
}

Documentation Index

Fetch the complete documentation index at: https://docs.pubrio.com/llms.txt

Use this file to discover all available pages before exploring further.

Authorizations

​
pubrio-api-key
string
header
required

A unique API token that represents the actions you perform through the API and the corresponding permissions and operations. You can create it through the Settings section.

Body

application/json
​
domain_search_id
string<uuid>
required

A unique identifier for the company search operation.

​
domain
string

A company domain used for company search operations. If we receive a URL such as www.pubrio.com or https://docs.pubrio.com/, the system will convert it to pubrio.com for processing.

Example:

"pubrio.com"

​
linkedin_url
string

The fully formed URL of the LinkedIn company profile. URL begin with http and contain linkedin.com/company/

Example:

"https://www.linkedin.com/company/pubrio"

​
domain_id
integer

A unique identifier for the domain search operation.

​
profile_id
integer

Optional. An identifier for the user profile (workspace) making the request. This is no longer required as the API key already includes your workspace information. If provided, it helps in associating the lookup with a specific user, allowing for data retrieval and credit tracking.

Check out user details endpoints under the Profile tab for more information.

Response

Successful response containing company technology details.

​
data
object

Response info depends on specific endpoint.