This list contains the government API cases collected, cleaned and analysed in the APIs4DGov study "Web API landscape: relevant general purpose ICT standards, technical specifications and terms".

The list does not represent a complete list of all government cases in Europe, as it is built to support the goals of the study and is limited to the analysis and data gathered from the following sources:

• The EU open data portal

• The European data portal

• The INSPIRE catalogue

• JoinUp: The API cases collected from the European Commission JoinUp platform

• Literature-document review: the API cases gathered from the research activities of the study performed till the end of 2019

• ProgrammableWeb: the ProgrammableWeb API directory

• Smart 2015/0041: the database of 395 cases created by the study ‘The project Towards faster implementation and uptake of open government’ (SMART 2015/0041).

• Workshops/meetings/interviews: a list of API cases collected in the workshops, surveys and interviews organised within the APIs4DGov

Each API case is classified accordingly to the following rationale:

• Unique id: a unique key of each case, obtained by concatenating the following fields: (Country Code) + (Governmental level) + (Name Id) + (Type of API)

• API Country or type of provider: the country in which the API case has been published

• API provider: the specific provider that published and maintain the API case

• Name Id: an acronym of the name of the API case (it can be not unique)

• Short description

• Type of API: (i) API registry, a set, catalogue, registry or directory of APIs; (ii) API platform: a platform that supports the use of APIs; (iii) API tool: a tool used to manage APIs; (iv) API standard: a set of standards related to government APIs; (v) Data catalogue, an API published to access metadata of datasets, normally published by a data catalogue; (vi) Specific API, a unique (can have many endpoints) API built for a specific purpose

• Number of APIs: normally only one, in the case of API registry, the number of APIs published by the registry at the 31/12/2019

• Theme: list of domains related to the API case (controlled vocabulary)

• Governmental level: the geographical scope of the API (city, regional, national or international)

• Country code: the country two letters internal code

• Source: the source (among the ones listed in the previous) from where the API case has been gathered

OpenWeb Ninja's Google Images Data (Google SERP Data) API provides real-time image search capabilities for images sourced from all public sources on the web.

The API enables you to search and access more than 100 billion images from across the web including advanced filtering capabilities as supported by Google Advanced Image Search. The API provides Google Images Data (Google SERP Data) including details such as image URL, title, size information, thumbnail, source information, and more data points. The API supports advanced filtering and options such as file type, image color, usage rights, creation time, and more. In addition, any Advanced Google Search operators can be used with the API.

OpenWeb Ninja's Google Images Data & Google SERP Data API common use cases:

• Creative Media Production: Enhance digital content with a vast array of real-time images, ensuring engaging and brand-aligned visuals for blogs, social media, and advertising.

• AI Model Enhancement: Train and refine AI models with diverse, annotated images, improving object recognition and image classification accuracy.

• Trend Analysis: Identify emerging market trends and consumer preferences through real-time visual data, enabling proactive business decisions.

• Innovative Product Design: Inspire product innovation by exploring current design trends and competitor products, ensuring market-relevant offerings.

• Advanced Search Optimization: Improve search engines and applications with enriched image datasets, providing users with accurate, relevant, and visually appealing search results.

OpenWeb Ninja's Annotated Imagery Data & Google SERP Data Stats & Capabilities:

• 100B+ Images: Access an extensive database of over 100 billion images.

• Images Data from all Public Sources (Google SERP Data): Benefit from a comprehensive aggregation of image data from various public websites, ensuring a wide range of sources and perspectives.

• Extensive Search and Filtering Capabilities: Utilize advanced search operators and filters to refine image searches by file type, color, usage rights, creation time, and more, making it easy to find exactly what you need.

• Rich Data Points: Each image comes with more than 10 data points, including URL, title (annotation), size information, thumbnail, and source information, providing a detailed context for each image.

APISCRAPY offers comprehensive California legal data, including court data, litigation records, attorney information, and legal datasets for other states such as Texas, New York, Florida, Illinois, and more. Our AI-driven web scraping tool simplifies data extraction and integration, transforming complex legal data into ready-to-use APIs.

With APISCRAPY, you gain access to precise state-based legal data for lawyers, law data, and USA legal data, enabling seamless workflows and actionable insights. Our solution guarantees 50% cost savings compared to traditional methods, with flexible pricing tailored to your needs.

Key Benefits:

Extract and classify court data and litigation records for multiple states. Verified and accurate datasets for attorneys and legal professionals. Pre-built automation and real-time data delivery. Seamless integration with databases and BI tools, no coding required. Access free data samples to evaluate the quality of our services.

Whether you're focused on compliance, market research, or business intelligence, APISCRAPY provides reliable legal data solutions across the USA, ensuring accuracy, efficiency, and affordability. Contact us today for your California legal data and beyond!

Context

With the proliferation of online developer forums, developers share their opinions about the APIs they use. The plethora of such information can present challenges to the developers to get quick but informed insights about the APIs. To understand the potential benefits of such API reviews, we conducted a case study of opinions in Stack Overflow using a benchmark dataset of 4522 sentences. We observed that opinions about diverse API aspects (e.g., usability) are prevalent and offer insights that can shape developers’ perception and decisions related to software development.

Content

Motivated by the finding, we built a suite of techniques to automatically mine and categorize opinions about APIs from forum posts. First, we detect opinionated sentences in the forum posts. Second, we associate the opinionated sentences to the API mentions. Third, we detect API aspects (e.g., performance, usability) in the reviews. We developed and deployed a tool called Opiner, supporting the above techniques. Opiner is available online as a search engine, where developers can search for APIs by their names to see all the aggregated opinions about the APIs that are automatically mined and summarized from developer forums.

To learn more about the work please refer to the paper Automatic Mining of Opinions Expressed About APIs in Stack Overflow. If you want to learn how this tool was developed, read the previous paper by the author Opiner: An opinion search and summarization engine for APIs

The tool is available at http://sentimin.soccerlab.polymtl.ca:38080/opinereval/

Acknowledgements

We sincerely thank the anonymous reviewers for providing us valuable feedback to improve the paper. We are grateful to Prof Novielli for providing cues on how to train the SentiCR classifier, to run the Senti4SD classifier, and for kindly reviewing the contents of Section 8.1. We thank all the coders who participated in the development of the benchmark data and the evaluation of the algorithms. This work is partly supported by the Natural Sciences and Engineering Research Council of Canada (NSERC).

The dataset is collected from the git repository https://github.com/giasuddin/OpinionValueTSE created by the first author.

Inspiration

Future inspirations from this work can be an in-depth exploration of API aspects in the forum posts by leveraging the aspect detection and opinion mining infrastructure we have developed in Opiner. In addition, extending the benchmark to explore reviews from other programming languages (e.g, javascript, python, etc.) as well as other domains, such as, platform (e.g., ‘linux’), data structures (e.g., ‘hashmap’), build systems (e.g., ‘ant’), software project management system (e.g., ‘maven’), etc.

Canvas LMS includes a REST API for accessing and modifying data externally from the main application, in your own programs and scripts. This documentation describes the resources that make up the API. This API grants the same access rights as the user has as a canvas user. https://canvas.instructure.com/doc/api/index.html Schema All API access is over HTTPS, against your normal Canvas domain. All API responses are in JSON format. All integer ids in Canvas are 64 bit integers. All boolean parameters can be passed as true/false, t/f, yes/no, y/n, on/off, or 1/0. When using JSON format, a literal true/false is preferred, rather than as a string. For POST and PUT requests, parameters are sent using standard HTML form encoding (the application/x-www-form-urlencoded content type). POST and PUT requests may also optionally be sent in JSON format format. The content-type of the request must be set to application/json in this case. There is currently no way to upload a file as part of a JSON POST, the multipart form type must be used.

DASH is Harvard's digital repository for scholarly articles, theses and dissertatinos, and other Harvard-affiliate generated literature. Harvard Library makes the bibliographic data openly available for all uses, with a standard set of APIs.

The data.gov.ie API

Data.gov.ie is built using CKAN v2.2 (link is external), which provides a powerful API that allows developers to retrieve datasets, groups or other CKAN objects and search for datasets. There is full documentation (link is external) available for the CKAN API online.

Example API Calls

Get JSON-formatted lists of a site’s datasets or other CKAN objects: data.gov.ie/api/3/action/package_list data.gov.ie/api/3/action/tag_list Get a full JSON representation of a dataset, resource or other object: data.gov.ie/api/3/action/package_show?id=the-walled-towns-of-ireland data.gov.ie/api/3/action/tag_show?id=marine Search for packages or resources matching a query: data.gov.ie/api/3/action/package_search?q=museum data.gov.ie/api/3/action/resource_search?query=name:The%20Walled%20Towns%20of%20Ireland

More information at https://data.gov.ie/developers

Analysis of ‘List of government APIs’ provided by Analyst-2 (analyst-2.ai), based on source dataset retrieved from http://data.europa.eu/88u/dataset/45ca8d82-ac31-4360-b3a1-ba43b0b07377 on 11 January 2022.

--- Dataset description provided by original source is as follows ---

This list contains the government API cases collected, cleaned and analysed in the APIs4DGov study "Web API landscape: relevant general purpose ICT standards, technical specifications and terms".

The list does not represent a complete list of all government cases in Europe, as it is built to support the goals of the study and is limited to the analysis and data gathered from the following sources:

• The EU open data portal

• The European data portal

• The INSPIRE catalogue

• JoinUp: The API cases collected from the European Commission JoinUp platform

• Literature-document review: the API cases gathered from the research activities of the study performed till the end of 2019

• ProgrammableWeb: the ProgrammableWeb API directory

• Smart 2015/0041: the database of 395 cases created by the study ‘The project Towards faster implementation and uptake of open government’ (SMART 2015/0041).

• Workshops/meetings/interviews: a list of API cases collected in the workshops, surveys and interviews organised within the APIs4DGov

Each API case is classified accordingly to the following rationale:

• Unique id: a unique key of each case, obtained by concatenating the following fields: (Country Code) + (Governmental level) + (Name Id) + (Type of API)

• API Country or type of provider: the country in which the API case has been published

• API provider: the specific provider that published and maintain the API case

• Name Id: an acronym of the name of the API case (it can be not unique)

• Short description

• Type of API: (i) API registry, a set, catalogue, registry or directory of APIs; (ii) API platform: a platform that supports the use of APIs; (iii) API tool: a tool used to manage APIs; (iv) API standard: a set of standards related to government APIs; (v) Data catalogue, an API published to access metadata of datasets, normally published by a data catalogue; (vi) Specific API, a unique (can have many endpoints) API built for a specific purpose

• Number of APIs: normally only one, in the case of API registry, the number of APIs published by the registry at the 31/12/2019

• Theme: list of domains related to the API case (controlled vocabulary)

• Governmental level: the geographical scope of the API (city, regional, national or international)

• Country code: the country two letters internal code

• Source: the source (among the ones listed in the previous) from where the API case has been gathered

--- Original source retains full ownership of the source dataset ---

This is a CSV file containing a listing of the top 60 articles published in the Journal of Digital Scholarship in the Humanities (JDSH, preciously LLC), as exported from the Altmetric Explorer tool on11 April 2017. The sheet has been manually annotated adding columns to indicate each article entry's corresponding License (column E) and Access Type (column F). License and Access Type data was crosschecked manually by accessing each article online individually. The file also contains data obtained from the Open Access Button API. The article DOIs as obtained from the Altmetric Explorer were run through the Open Access Button API on 15 May 2017 in order to discover if any of the published articles had open versions available. Any resulting links when available, were added to column O. Columns O and P also include additional information, when available, about the type of content available via the Open Access Button. Joe McArthur from the Open Access Button ran the first initial search for open surrogates of this dataset through the Open Access Button API. Ernesto Priego then manually crosschecked each entry and limited the final dataset to the top 60 articles (of 82). Please note that the Altmetric data for the JDSH is likely to have changed by now, though not too significantly. Altmetric scores have not been included in this file but the order of the entries correspond to the order in the data initially exported from the Altmetric Explorer (from most mentions to fiewer mentions, with a minimum of 1 mention). This dataset is part of the author and collaborator's ongoing research on open access and institutional repository uptake in the digital humanities. The data included in this file allows users to quickly quantify the number of JDSH articles published with open licenses, number of currently 'free', paywalled or open access articles. The data shared here also allows users to see which of the articles and/or their metadata (according to the Open Access Button API) have been deposited in institutional repositories. The data presented is the result of the specific methods employed to obtain the data. In this sense this data represents as much a testing of the technologies employed as of the actual articles' licensing and open availability. This means that data in columns L-P reflect the data available through the Open Access Button API at the moment of collection. It is perfectly possible that 'open surrogates' of the articles listed are available elsewhere through other methods. As indicated above data in columns E-F was obtained and added manually. Article DOI's were accessed manually from a computer browser outside/without access to university library networks, as the intention was to verify if any of the articles were available to the general public without university library network/subscription credentials.This deposit is part of a work in progress and is shared openly to document ongoing work and to encourage further discussion and analyses.

TomTom's Safety Related Traffic Information (SRTI) API is a webservice that delivers anonymized non-personal raw data on hazardous situations directly collected by TomTom's own applications. The content of the API includes anonymized, non-personal, crowd-sourced data from drivers using TomTom's AmiGO application that reports 'hazards' and 'broken down car' incidents on the road. In accordance with EU Regulation 886/2013 this data is accessible to other users and can be integrated in other applications to improve road safety conditions. The access and use of this data are laid out in our terms and conditions. The service delivers safety messages for the area of the European Union in the form of a RESTful web service. The content contains information based on sensor or end-user feedback.

GSA Auctions offers Federal personal property assets ranging from common place items (such as office equipment and furniture) to more select products like scientific equipment, heavy machinery, airplanes, vessels and vehicles. GSA Auctions’ online capabilities allow GSA to offer assets located across the country to any interested buyer, regardless of location. GSA Auctions API is a public GET API. The Auction listings will be delivered to the user in two formats. One is JSON and the other one is XML. The auction listings delivered thru the API contains the auction listings from all the participating agencies.

This portal is intended to serve as a means to access all available NMED data via secure Application Programming Interface (API).

To access our data, we require that you register with the portal.

You can browse the titles and a short description of our available APIs before registering.

Anyone who registers will be provided access to all of NMED’s public APIs.

Members of the regulated community served by NMED, as well as partner agencies and other official entities, can, during registration, request an elevated account that provides access to certain protected data APIs. Such requests will need to register using an official email account and potentially provide other means of verification before these account requests are approved.

Once registered, you will be able to fully explore and consume our collection of APIs, and access Open API Specification documentation that will help you understand, learn, and leverage those APIs for your purposes.

We hope you enjoy your visit to the NMED Open Data Portal and return many times.

RIDB is a part of the Recreation One Stop (Rec1Stop) project, initiated as a result of a government modernization study conducted in 2004. Rec1Stop provides a user-friendly, web-based resource to citizens, offering a single point of access to information about recreational opportunities nationwide. The web site represents an authoritative source of information and services for millions of visitors to federal lands, historic sites, museums, and other attractions/resources. Recreation Information Database (RIDB) Application Programming Interface (API) is provided for the purpose of accessing RIDB API endpoints which contain information for federal recreation areas, facilities, campsites, tours, and permits. Federal agencies provide and are responsible for the quality of data contained in the RIDB. Some data may be missing or incomplete. For example, some latitudes and longitudes may be blank. Please be mindful of this when searching for something in particular or applying proximity (radius) filters. Resources in this dataset:Resource Title: RIDB.recreation.gov. File Name: Web Page, url: https://ridb.recreation.gov/ RIDB is a part of the Recreation One Stop (Rec1Stop) project, initiated as a result of a government modernization study conducted in 2004. Rec1Stop provides a user-friendly, web-based resource to citizens, offering a single point of access to information about recreational opportunities nationwide. The web site represents an authoritative source of information and services for millions of visitors to federal lands, historic sites, museums, and other attractions/resources.

Weather API Market size was valued at USD 367.38 Million in 2024 and is projected to reach USD 664.06 Million by 2032, growing at a CAGR of 7.62% from 2026 to 2032.

Global Weather API Market Overview

A Weather API (Application Programming Interface) is a digital tool that allows applications, websites, and software platforms to access real-time and forecasted weather data from meteorological sources. These APIs provide information on temperature, humidity, precipitation, wind speed, air quality, and severe weather alerts, enabling seamless integration into various applications. The significance of Weather APIs lies in their ability to enhance decision-making across multiple industries, including agriculture, transportation, aviation, and disaster management. Businesses utilize these APIs for predictive analytics, improving operational efficiency and safety. Consumers benefit from accurate weather updates for travel planning and outdoor activities.

A system is identified by constructing logical boundaries around a set of processes, communications, storage, and related resources. The elements within these boundaries constitute a single system requiring a security plan. Each element of the system must (1) be under the same direct management control, (2) have the same function or mission objective, (3) have essentially the same operating characteristics and security needs, and (4) reside in the same general operating environment. This service produces a list of FISMA Systems that belong to DHS Components.

Starting June 12, 2023, many Reddit communities (subreddits) began a protest where they "went dark" - by changing to private mode - as a protest in response to Reddit's plans to change its API access policies and fee structure. Supporters of the protest criticize the planned changes for being prohibitively expensive for 3rd party apps. Beyond 3rd party apps, there is significant concern that the API changes are a move by the platform to increase monetization, degrade the user experience, and eventually kill off other custom features such as the old.reddit.com interface, the Reddit Enhancement Suite browser extension, and more. Additionally, there are concerns that the API changes will impede the ability of subreddit moderators (who are all unpaid users) to access tools to keep their communities on-topic and free of spam. This dataset includes the "stickied" posts that appeared on 5,351 subreddits on June 11, 2023 and June 12, 2023 - including many subreddits announcing their plans to participate in the protest. These posts were scraped using a custom Python script that was written specifically for this purpose. Ironically, the script uses the PRAW (Python Reddit API Wrapper) library, requiring a valid Reddit API key. Accordingly, after the platform's new API pricing policy went into effect, it is no longer feasible for researchers to perform this type of web scraping without external funding support. Methods The list of subreddits was created from the ist of participating subreddits that had been collated in the /r/ModCoord subreddit. An initial Python script looks at three reddit posts and grabs the list of participating subreddits:

https://www.reddit.com/r/ModCoord/comments/1401qw5/incomplete_and_growing_list_of_participating/ https://www.reddit.com/r/ModCoord/comments/143fzf6/incomplete_and_growing_list_of_participating/ https://www.reddit.com/r/ModCoord/comments/146ffpb/incomplete_and_growing_list_of_participating/

It uses the requests library to get the HTTP response body. Then it uses re to search for links that look like r/iphone, e.g. what the list looks like in the post. Next it's just a bit of string cleanup and then writing to an output file. This script does not use the Reddit API at all. It's just basic HTTP requests. A second Python script then reads that list and uses the Reddit API to request information about current posts in each subreddit. The script creates a CSV file for each of the listed subreddits and creates a new row for each "stickied" post. There currently isn't any logic to try and detect which post is the one announcing the blackout; I simply saved all of them. Many subreddits did not have any stickied posts at all, and many stickied posts were not related to the blackout.

Context Intelligence: from text to actionable data. Extract meaning from unstructured text and put it in context with a simple API.

ENTITY EXTRACTION Find mentions of places, people, brands and events in documents and social media. Easily get additional data about the entities.

TEXT & CONTENT CLASSIFICATION Classify multilingual text into standard, pre-defined taxonomies or build your own custom classification scheme in minutes.

SENTIMENT ANALYSIS Identify whether the expressed opinion in short texts (like product reviews) is positive, negative, or neutral.

KEYWORDS / CONCEPTS EXTRACTION Automatically identify important, contextually relevant, concepts and key-phrases in articles and social media posts.

SEMANTIC SIMILARITY Compare two texts and compute their syntactic and semantic similarity. Understand when two texts are about the same subject.

ARTICLE EXTRACTION Extract clean text article from newspapers, blogs and other websites. Remove boilerplate and advertising and get the article full text and images.

Snapshot img

Active Pharmaceutical Ingredients Market Size 2025-2029

The active pharmaceutical ingredients market size is forecast to increase by USD 97.6 billion, at a CAGR of 7.1% between 2024 and 2029. The Active Pharmaceutical Ingredients (API) market is experiencing a significant shift in manufacturing scenarios, with an increasing trend towards outsourcing and contract manufacturing in developing countries. This paradigm change is driven by cost savings and improved access to specialized expertise and resources.

Major Market Trends & Insights

Asia dominated the market and accounted for a 51% share in 2023.
The market is expected to grow significantly in North America region as well over the forecast period.
Based on the Manufacturing Type, the captive APIs segment led the market and was valued at USD 124.10 billion of the global revenue in 2023.
Based on the Type, the innovative APIs segment accounted for the largest market revenue share in 2023.

Market Size & Forecast

Market Opportunities: USD 238.60 Billion
Future Opportunities: USD 97.6 Billion
CAGR (2024-2029): 7.1%
Asia: Largest market in 2023

The demand for APIs is further fueled by research and investment in biologics and biosimilars, as well as small and large molecule drugs for treating various conditions, including infectious diseases, genetic disorders, and mental health disorders like schizophrenia. However, this transition comes with challenges. High investment costs for setting up state-of-the-art manufacturing facilities and the risk of substantial losses due to regulatory non-compliance pose significant hurdles for market entrants.

Companies must navigate these challenges to capitalize on the opportunities presented by the evolving API market landscape. Strategic partnerships, continuous process improvement, and robust regulatory compliance are essential strategies for companies seeking to thrive in this dynamic market.

What will be the Size of the Active Pharmaceutical Ingredients Market during the forecast period?

Explore in-depth regional segment analysis with market size data - historical 2019-2023 and forecasts 2025-2029 - in the full report.
Request Free Sample

The active pharmaceutical ingredients (API) market continues to evolve, driven by advancements in biopharmaceutical manufacturing and technological innovations. Continuous manufacturing processes, such as those employing analytical chemistry methods and solid-state chemistry, are increasingly utilized for API production. Quality control testing, in-process controls, and downstream processing techniques ensure the production of high-quality APIs. In the realm of drug delivery systems, large molecule APIs and drug formulation processes are undergoing significant advancements. API purification techniques, including upstream processing and chemical synthesis methods, play a crucial role in ensuring the purity and efficacy of APIs. Furthermore, the integration of bioreactor technology and cell line development in the production of large molecule APIs is revolutionizing the industry. The contract APIs segment is the second largest segment of the manufacturing type and was valued at USD 100.50 billion in 2023.

Process intensification through microfluidic synthesis, flow chemistry, and peptide synthesis is another key trend in API manufacturing. Pharmaceutical synthesis, API characterization methods, and pharmaceutical process validation are essential components of the API development lifecycle. GMP compliance and the adoption of advanced technologies, such as crystallization techniques and process analytical technology, further enhance the industry's capabilities. For instance, a leading pharmaceutical company reported a 15% increase in API production efficiency through the implementation of continuous manufacturing processes and advanced analytical techniques. Industry growth is expected to reach 8% annually, driven by these technological advancements and the increasing demand for high-quality APIs.

How is this Active Pharmaceutical Ingredients Industry segmented?

The active pharmaceutical ingredients industry research report provides comprehensive data (region-wise segment analysis), with forecasts and estimates in 'USD billion' for the period 2025-2029, as well as historical data from 2019-2023 for the following segments.

Manufacturing Type

  Captive APIs
  Contract APIs


Type

  Innovative APIs
  Generic APIs


Synthesis Method

  Biotech APIs
  Synthetic APIs


Application

  Cardiovascular Diseases
  Oncology
  CNS and Neurology
  Orthopedic
  Endocrinology
  Pulmonology
  Gastroenterology
  Nephrology
  Ophthalmology
  Anti-Infectives
  Diabetes
  Respiratory Diseases
  Other


End-User

  Pharmaceutical Companies
  Biotechnology Companies
  Contract Research Organizations (CROs)
  Academic/Research Institutes


Potency

  High Potency APIs (HPAPIs)
  Low Potency APIs

The Heritage Council Victoria maintains a catalogue of the State's significant assets of heritage value protected under the Heritage Act 2017 which includes places, significant objects and shipwreck …Show full descriptionThe Heritage Council Victoria maintains a catalogue of the State's significant assets of heritage value protected under the Heritage Act 2017 which includes places, significant objects and shipwreck sites. The Victorian Heritage Database (VHD) is home to the Victorian Heritage Register listing these assets as well as the Victorian Heritage Inventory which lists all known historical archaeological sites in Victoria. The VHD API provides access to these resources. The VHD API is a read only restful API accepting only GET requests and returning only HAL formatted JSON responses. To access a specific version of this API you can either prefix every request with v/ or specify the required version in an Accept header. It is recommended you do this in order to prevent backward compatibility issues with future versions. Example 1 - https://api.heritagecouncil.vic.gov.au/v1/places Example 2 - Accept: application/vnd.vhd.v1+json

This dataset provides detail on how all assets on a domain are being used (e.g. views, downloads, API reads).

User activity is provided by date, asset uid, asset type, asset name, access type and user segment. Please see Site Analytics: Asset Access for more detail about these fields.

The dataset will reflect new Asset Access records within a day of when they occur.