<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: carrierone</title>
    <description>The latest articles on DEV Community by carrierone (@carrierone).</description>
    <link>https://dev.to/carrierone</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3829793%2F9f34d373-d134-4f70-b9ab-d18edc673645.jpeg</url>
      <title>DEV Community: carrierone</title>
      <link>https://dev.to/carrierone</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/carrierone"/>
    <language>en</language>
    <item>
      <title>Getting SEC EDGAR Filings via API Without Scraping</title>
      <dc:creator>carrierone</dc:creator>
      <pubDate>Tue, 09 Jun 2026 19:01:10 +0000</pubDate>
      <link>https://dev.to/carrierone/getting-sec-edgar-filings-via-api-without-scraping-3cjh</link>
      <guid>https://dev.to/carrierone/getting-sec-edgar-filings-via-api-without-scraping-3cjh</guid>
      <description>&lt;h2&gt;
  
  
  Getting SEC EDGAR Filings via API Without Scraping
&lt;/h2&gt;

&lt;p&gt;When working on financial applications that require access to real-time data from SEC filings like 10-Ks and 10-Qs, the traditional approach of web scraping can be both time-consuming and error-prone. Fortunately, there are APIs available that allow developers to fetch this information without having to scrape the SEC’s website manually.&lt;/p&gt;

&lt;h3&gt;
  
  
  Problem
&lt;/h3&gt;

&lt;p&gt;The SEC EDGAR system requires manual updates for filings like quarterly reports and financial statements. This means that if you want real-time access to these documents, you would need to constantly check their website or use a service that continually monitors new submissions. However, this approach is not feasible for many developers due to the time constraints and potential inaccuracies in data retrieval.&lt;/p&gt;

&lt;h3&gt;
  
  
  Solution: Using an API
&lt;/h3&gt;

&lt;p&gt;One effective solution is to utilize an API designed specifically for accessing SEC EDGAR filings. This eliminates the need for manual web scraping and provides a more reliable way to get real-time updates on new filings. For example, you can use &lt;code&gt;api.verilexdata.com/api/v1/sec/sample&lt;/code&gt; as your endpoint.&lt;/p&gt;

&lt;p&gt;Here’s a simple Python code snippet that demonstrates how to fetch data from this API:&lt;/p&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;
python
import requests

def fetch_sec_filings():
    url = "https://api.verilexdata.com/api/v1/sec/sample"
    response = requests.get(url
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;

</description>
    </item>
    <item>
      <title>How to Query 9 Million US Healthcare Providers via API (NPI Registry)</title>
      <dc:creator>carrierone</dc:creator>
      <pubDate>Fri, 05 Jun 2026 19:01:09 +0000</pubDate>
      <link>https://dev.to/carrierone/how-to-query-9-million-us-healthcare-providers-via-api-npi-registry-54d8</link>
      <guid>https://dev.to/carrierone/how-to-query-9-million-us-healthcare-providers-via-api-npi-registry-54d8</guid>
      <description>&lt;h2&gt;
  
  
  How to Query 9 Million US Healthcare Providers via API (NPI Registry)
&lt;/h2&gt;

&lt;p&gt;When developing a healthcare application that requires integrating data from the National Provider Identifier (NPI) registry, having access to an accurate and up-to-date list of providers can be invaluable. The NPI registry contains unique identifiers for healthcare professionals in the United States, which is crucial for tasks such as prior authorization, provider directories, and FHIR-based applications.&lt;/p&gt;

&lt;p&gt;To get started with querying this dataset, you'll need to use a developer-friendly API that provides access to the NPI information. One such API endpoint is provided by &lt;code&gt;api.verilexdata.com&lt;/code&gt;, specifically at &lt;code&gt;/api/v1/npi/sample&lt;/code&gt;. This sample data can serve as a good starting point for developers looking to integrate NPI provider lookup functionalities into their applications.&lt;/p&gt;

&lt;h3&gt;
  
  
  Python Code Example: Querying the NPI Registry
&lt;/h3&gt;

&lt;p&gt;Here's a quick example of how you might use Python and an HTTP library like &lt;code&gt;requests&lt;/code&gt; to make a call to this API endpoint:&lt;/p&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;
python
import requests

# Define your NPI number or other search parameters here
npi_number = "1234567890"

# Construct the URL with your query parameters
url = f"https://api.verilexdata.com/api/v1/npi/sample?npi={npi_number}"

# Send a GET request to the API
response
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;

</description>
    </item>
    <item>
      <title>OTC Stock Shell Risk Scoring: How to Screen Penny Stocks Programmatically</title>
      <dc:creator>carrierone</dc:creator>
      <pubDate>Tue, 02 Jun 2026 19:01:02 +0000</pubDate>
      <link>https://dev.to/carrierone/otc-stock-shell-risk-scoring-how-to-screen-penny-stocks-programmatically-2ini</link>
      <guid>https://dev.to/carrierone/otc-stock-shell-risk-scoring-how-to-screen-penny-stocks-programmatically-2ini</guid>
      <description>&lt;h2&gt;
  
  
  OTC Stock Shell Risk Scoring: How to Screen Penny Stocks Programmatically
&lt;/h2&gt;

&lt;p&gt;When building retail trading tools or fintech apps that require screening OTC stocks for risk, it's crucial to identify shell companies. These are entities whose primary function is to raise funds and then divert those funds elsewhere without any substantial business activity. Identifying these can significantly reduce the likelihood of investment losses.&lt;/p&gt;

&lt;p&gt;Here’s a small Python example illustrating how you could use an API endpoint to scan OTC stock data for shell risk:&lt;/p&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;
python
import requests

def fetch_otc_data(api_key):
    url = "https://api.verilexdata.com/api/v1/otc/sample"

    headers = {
        'Authorization': f'Bearer {api_key}',
        'Content-Type': 'application/json'
    }

    response = requests.get(url, headers=headers)

    if response.status_code == 200:
        return response.json()
    else:
        raise Exception(f"Failed to fetch data: {response.text}")

# Replace with your actual API key
api_key = "YOUR_API_KEY"
otc_data = fetch_otc_data(api_key)

# Example of how you might filter for shell risk, though this is simplified:
def detect_shell_risk(data):
    # Placeholder logic - in a real scenario you'd want more sophisticated checks
    return True if data['status
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;

</description>
    </item>
    <item>
      <title>Federal Contract Award Data (USASpending) via API</title>
      <dc:creator>carrierone</dc:creator>
      <pubDate>Fri, 29 May 2026 19:01:09 +0000</pubDate>
      <link>https://dev.to/carrierone/federal-contract-award-data-usaspending-via-api-1bne</link>
      <guid>https://dev.to/carrierone/federal-contract-award-data-usaspending-via-api-1bne</guid>
      <description>&lt;h2&gt;
  
  
  Federal Contract Award Data (USASpending) via API
&lt;/h2&gt;

&lt;p&gt;When developing tools for federal procurement analytics or business development within the government sector, having access to contract award data is invaluable. The U.S. ASBESTOS Spending API, available at verilexdata.com, provides a gateway to this critical information.&lt;/p&gt;

&lt;h3&gt;
  
  
  Problem: Searching by Agency, Vendor, or NAICS Code
&lt;/h3&gt;

&lt;p&gt;Often, developers need to filter through contracts based on specific criteria such as the agency, vendor name, or North American Industry Classification System (NAICS) code. This filtering helps in understanding which contracts are awarded to whom and under what industry category.&lt;/p&gt;

&lt;h4&gt;
  
  
  Example of Python Code for Filtering Contracts by Agency:
&lt;/h4&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight python"&gt;&lt;code&gt;&lt;span class="kn"&gt;import&lt;/span&gt; &lt;span class="n"&gt;requests&lt;/span&gt;

&lt;span class="k"&gt;def&lt;/span&gt; &lt;span class="nf"&gt;get_contracts_by_agency&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;agency_code&lt;/span&gt;&lt;span class="p"&gt;):&lt;/span&gt;
    &lt;span class="n"&gt;url&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="sa"&gt;f&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;https://verilexdata.com/api/v1/contracts?agencies=&lt;/span&gt;&lt;span class="si"&gt;{&lt;/span&gt;&lt;span class="n"&gt;agency_code&lt;/span&gt;&lt;span class="si"&gt;}&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;
    &lt;span class="n"&gt;response&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="n"&gt;requests&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;get&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;url&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;

    &lt;span class="k"&gt;if&lt;/span&gt; &lt;span class="n"&gt;response&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;status_code&lt;/span&gt; &lt;span class="o"&gt;==&lt;/span&gt; &lt;span class="mi"&gt;200&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
        &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="n"&gt;response&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;json&lt;/span&gt;&lt;span class="p"&gt;()&lt;/span&gt;
    &lt;span class="k"&gt;else&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
        &lt;span class="nf"&gt;print&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="sa"&gt;f&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;Failed to fetch contracts. Status code: &lt;/span&gt;&lt;span class="si"&gt;{&lt;/span&gt;&lt;span class="n"&gt;response&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;status_code&lt;/span&gt;&lt;span class="si"&gt;}&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
        &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="bp"&gt;None&lt;/span&gt;

&lt;span class="c1"&gt;# Example usage
&lt;/span&gt;&lt;span class="n"&gt;contracts_by_dod&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="nf"&gt;get_contracts_by_agency&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="sh"&gt;'&lt;/span&gt;&lt;span class="s"&gt;DOD&lt;/span&gt;&lt;span class="sh"&gt;'&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;span class="k"&gt;if&lt;/span&gt; &lt;span class="n"&gt;contracts_by_dod&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
    &lt;span class="k"&gt;for&lt;/span&gt; &lt;span class="n"&gt;contract&lt;/span&gt; &lt;span class="ow"&gt;in&lt;/span&gt; &lt;span class="n"&gt;contracts_by_dod&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
        &lt;span class="nf"&gt;print&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;contract&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h4&gt;
  
  
  Using the API Endpoint: verilexdata.com
&lt;/h4&gt;

&lt;p&gt;By utilizing the&lt;/p&gt;

</description>
    </item>
    <item>
      <title>NOAA Weather Data API: Historical and Current Weather for Developers</title>
      <dc:creator>carrierone</dc:creator>
      <pubDate>Tue, 26 May 2026 19:00:59 +0000</pubDate>
      <link>https://dev.to/carrierone/noaa-weather-data-api-historical-and-current-weather-for-developers-4i9m</link>
      <guid>https://dev.to/carrierone/noaa-weather-data-api-historical-and-current-weather-for-developers-4i9m</guid>
      <description>&lt;h2&gt;
  
  
  NOAA Weather Data API: Historical and Current Weather for Developers
&lt;/h2&gt;

&lt;p&gt;For developers looking to integrate weather data into their applications—be it for trading algorithms, logistics optimization, agtech initiatives, or insurance underwriting—it's essential to have a reliable source of historical and current weather observations. One such resource is the NOAA (National Oceanic and Atmospheric Administration) weather API.&lt;/p&gt;

&lt;h3&gt;
  
  
  The Problem: Historical and Current Weather Data Integration
&lt;/h3&gt;

&lt;p&gt;Historical and current weather data can significantly impact decision-making in various industries. However, obtaining this data directly from sources like NOAA requires navigating through complex endpoints or interfaces. This complexity often results in inefficiencies and potential errors when integrating into applications. A streamlined solution could make the process much smoother.&lt;/p&gt;

&lt;h3&gt;
  
  
  Python Code Example for Accessing NOAA Weather Data
&lt;/h3&gt;

&lt;p&gt;Here’s a simple example of how you might access historical and current weather data using the API at &lt;code&gt;api.verilexdata.com/api/v1/weather/sample&lt;/code&gt;. Note that this endpoint is illustrative; actual endpoints may vary. This code snippet fetches both historical and current weather observations.&lt;/p&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;
python
import requests

def get_weather_data(station_id):
    url = f"https://api.verilexdata.com/api/v1/weather/{station_id}"
    headers = {
        "Content-Type": "application/json",
        # Add any required authorization or other headers here
    }

    response = requests.get(url, headers=headers)
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;

</description>
    </item>
    <item>
      <title>FRED and BLS Economic Indicator Data for Developers</title>
      <dc:creator>carrierone</dc:creator>
      <pubDate>Fri, 22 May 2026 19:01:00 +0000</pubDate>
      <link>https://dev.to/carrierone/fred-and-bls-economic-indicator-data-for-developers-3938</link>
      <guid>https://dev.to/carrierone/fred-and-bls-economic-indicator-data-for-developers-3938</guid>
      <description>&lt;h2&gt;
  
  
  FRED and BLS Economic Indicator Data for Developers
&lt;/h2&gt;

&lt;p&gt;As a developer working on financial applications that require access to economic indicator data such as CPI, NFP, GDP, PCE, and unemployment rates, you might be looking for reliable sources of data. One popular source is the Federal Reserve Economic Database (FRED) from the St. Louis Fed in partnership with the Bureau of Labor Statistics (BLS). These services offer a wealth of economic indicators that can help power analytics or trading apps.&lt;/p&gt;

&lt;h3&gt;
  
  
  Problem: Accessing Real-Time Data
&lt;/h3&gt;

&lt;p&gt;If your app needs real-time data feeds for these indicators, FRED and BLS provide APIs through which you can fetch this information. However, using these APIs directly might require some knowledge of HTTP requests and parsing JSON responses. Here’s a quick Python example showing how to access the CPI (Consumer Price Index) data:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight python"&gt;&lt;code&gt;&lt;span class="kn"&gt;import&lt;/span&gt; &lt;span class="n"&gt;requests&lt;/span&gt;

&lt;span class="c1"&gt;# Replace YOUR_API_KEY with your actual API key if required
&lt;/span&gt;&lt;span class="n"&gt;api_key&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;YOUR_API_KEY&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;
&lt;span class="n"&gt;url&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="sa"&gt;f&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;https://api.verilexdata.com/api/v1/econ/stats?indicator=CPI&amp;amp;apikey=&lt;/span&gt;&lt;span class="si"&gt;{&lt;/span&gt;&lt;span class="n"&gt;api_key&lt;/span&gt;&lt;span class="si"&gt;}&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;

&lt;span class="n"&gt;response&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="n"&gt;requests&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;get&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;url&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;span class="k"&gt;if&lt;/span&gt; &lt;span class="n"&gt;response&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;status_code&lt;/span&gt; &lt;span class="o"&gt;==&lt;/span&gt; &lt;span class="mi"&gt;200&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
    &lt;span class="n"&gt;data&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="n"&gt;response&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;json&lt;/span&gt;&lt;span class="p"&gt;()&lt;/span&gt;
    &lt;span class="nf"&gt;print&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;data&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;span class="k"&gt;else&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
    &lt;span class="nf"&gt;print&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="sa"&gt;f&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;Error: &lt;/span&gt;&lt;span class="si"&gt;{&lt;/span&gt;&lt;span class="n"&gt;response&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;status_code&lt;/span&gt;&lt;span class="si"&gt;}&lt;/span&gt;&lt;span class="s"&gt; - &lt;/span&gt;&lt;span class="si"&gt;{&lt;/span&gt;&lt;span class="n"&gt;response&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;text&lt;/span&gt;&lt;span class="si"&gt;}&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h3&gt;
  
  
  Endpoint for FRED and B
&lt;/h3&gt;

</description>
    </item>
    <item>
      <title>DeFi Liquidation Signals and Whale Wallet Tracking via API</title>
      <dc:creator>carrierone</dc:creator>
      <pubDate>Tue, 19 May 2026 19:01:29 +0000</pubDate>
      <link>https://dev.to/carrierone/defi-liquidation-signals-and-whale-wallet-tracking-via-api-4c6i</link>
      <guid>https://dev.to/carrierone/defi-liquidation-signals-and-whale-wallet-tracking-via-api-4c6i</guid>
      <description>&lt;h2&gt;
  
  
  DeFi Liquidation Signals and Whale Wallet Tracking via API
&lt;/h2&gt;

&lt;p&gt;In the world of decentralized finance (DeFi), understanding liquidation signals and tracking whale wallet movements can be crucial for developers aiming to build more resilient smart contracts. This article will cover how you can access these insights through an API, specifically focusing on Aave, Compound, Morpho, and monitoring wallets with high transaction activity.&lt;/p&gt;

&lt;h3&gt;
  
  
  Understanding Liquidation Signals
&lt;/h3&gt;

&lt;p&gt;Liquidation occurs when a user's collateral value falls below the debt they have incurred, triggering the liquidator to seize their collateral. Monitoring such signals helps in setting up robust risk management strategies within your DeFi applications.&lt;/p&gt;

&lt;h4&gt;
  
  
  Python Code Example for Aave Lending Pool Contracts
&lt;/h4&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;
python
from web3 import Web3
import requests

def get_liquidation_signal(pool_address):
    url = f"https://api.verilexdata.com/liquidations?poolAddress={pool_address}"
    response = requests.get(url)

    if response.status_code == 200:
        return response.json()
    else:
        raise Exception(f"Failed to fetch data: {response.text}")

# Example usage
pool_addresses = ["0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48", "0xC0AEe6
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;

</description>
    </item>
    <item>
      <title>Polymarket Data API: Smart Money Tracking and Cross-Market Arbitrage</title>
      <dc:creator>carrierone</dc:creator>
      <pubDate>Fri, 15 May 2026 19:01:35 +0000</pubDate>
      <link>https://dev.to/carrierone/polymarket-data-api-smart-money-tracking-and-cross-market-arbitrage-k3m</link>
      <guid>https://dev.to/carrierone/polymarket-data-api-smart-money-tracking-and-cross-market-arbitrage-k3m</guid>
      <description>&lt;h2&gt;
  
  
  Polymarket Data API: Smart Money Tracking and Cross-Market Arbitrage
&lt;/h2&gt;

&lt;p&gt;If you're a prediction market trader looking to gain insights into smart money signals across different markets, Polymarket's data API can be an invaluable tool. The API provides stats on various markets, including cross-market arbitrage opportunities and microstructure details.&lt;/p&gt;

&lt;h3&gt;
  
  
  Problem
&lt;/h3&gt;

&lt;p&gt;Tracking smart money flows is crucial for traders aiming to identify profitable arbitrage opportunities across multiple prediction markets. However, manually sifting through numerous market pages or aggregators can be cumbersome and prone to errors. Polymarket's API streamlines this process by delivering real-time data directly into your application.&lt;/p&gt;

&lt;h3&gt;
  
  
  Small Python Code Example
&lt;/h3&gt;

&lt;p&gt;Here’s a simple example of how you might use the Polymarket Data API in Python to fetch stats for a specific market:&lt;/p&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;
python
import requests

def get_market_stats(api_key, market_id):
    url = f"https://api.verilexdata.com/api/v1/pm/stats/{market_id}"
    headers = {"Authorization": f"Bearer {api_key}"}

    response = requests.get(url, headers=headers)
    if response.status_code == 200:
        return response.json()
    else:
        raise Exception(f"Failed to fetch market stats: {response.text}")

# Replace 'your_api_key' with your actual API key
market_id = "123456
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;

</description>
    </item>
    <item>
      <title>USPTO Patent and Trademark Data via REST API</title>
      <dc:creator>carrierone</dc:creator>
      <pubDate>Tue, 12 May 2026 19:00:57 +0000</pubDate>
      <link>https://dev.to/carrierone/uspto-patent-and-trademark-data-via-rest-api-2m3a</link>
      <guid>https://dev.to/carrierone/uspto-patent-and-trademark-data-via-rest-api-2m3a</guid>
      <description>&lt;h2&gt;
  
  
  USPTO Patent and Trademark Data via REST API for Developers
&lt;/h2&gt;

&lt;p&gt;If you're a developer looking to build tools that leverage patent data for research, analytics, prior art searches, or trademark monitoring, the United States Patent and Trademark Office (USPTO) offers an excellent resource: their RESTful API. This API provides access to over 1.6 million USPTO grants through endpoints like &lt;code&gt;api.verilexdata.com/api/v1/patents/sample&lt;/code&gt;.&lt;/p&gt;

&lt;h3&gt;
  
  
  Problem: Building a Comprehensive IP Search Tool
&lt;/h3&gt;

&lt;p&gt;Imagine creating a tool that not only indexes the vast repository of patents but also allows users to search based on specific keywords, inventor names, or assignee details. The challenge here is finding an efficient way to integrate and process such large datasets.&lt;/p&gt;

&lt;h3&gt;
  
  
  Solution with Python
&lt;/h3&gt;

&lt;p&gt;To demonstrate how you can interact with this API in Python, let's write a simple script that fetches patent data using the &lt;code&gt;requests&lt;/code&gt; library:&lt;/p&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;
python
import requests

def get_patent_data(keyword):
    url = "https://api.verilexdata.com/api/v1/patents/sample"

    # Constructing the query string to filter by keyword
    params = {
        'keyword': keyword,
        'limit': 50,  # Limit results for demonstration purposes
        'sort_by': 'relevance'
    }

    response = requests.get(url
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;

</description>
    </item>
    <item>
      <title>Querying Federal Court Records (PACER) Programmatically</title>
      <dc:creator>carrierone</dc:creator>
      <pubDate>Fri, 08 May 2026 19:01:22 +0000</pubDate>
      <link>https://dev.to/carrierone/querying-federal-court-records-pacer-programmatically-2d42</link>
      <guid>https://dev.to/carrierone/querying-federal-court-records-pacer-programmatically-2d42</guid>
      <description>&lt;h2&gt;
  
  
  Querying Federal Court Records (PACER) Programmatically
&lt;/h2&gt;

&lt;p&gt;As legaltech developers, we often need to programmatically access and query federal court records. One of the primary sources for obtaining such data is PACER (Public Access to Court Electronic Records), which provides access to a vast array of case documents from across the United States.&lt;/p&gt;

&lt;h3&gt;
  
  
  Small Python Code Example
&lt;/h3&gt;

&lt;p&gt;Here’s a simple example using &lt;code&gt;requests&lt;/code&gt; library to fetch a document from PACER:&lt;/p&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;
python
import requests

def get_pacer_document(pacer_case_id, pacer_doctype, pacer_docnum):
    url = f"https://api.pacerpc.gov/api/v1/PDF/{pacer_case_id}/{pacer_doctype}/{pacer_docnum}"
    headers = {
        'X-PACER-KEY': '&amp;lt;YOUR_PACER_API_KEY&amp;gt;',  # Replace with your actual PACER API key
        'Accept': 'application/pdf'
    }

    response = requests.get(url, headers=headers)
    if response.status_code == 200:
        return response.content
    else:
        raise Exception(f"Failed to get document: {response.text}")

# Example usage
pacer_case_id = "1"
pacer_doctype = "Opinion"
pacer_docnum = "1"
document_content = get_pacer_document(pacer_case_id, pacer_do
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;

</description>
    </item>
    <item>
      <title>OFAC Sanctions Screening for Developers: How to Check Addresses and Names</title>
      <dc:creator>carrierone</dc:creator>
      <pubDate>Tue, 05 May 2026 19:01:26 +0000</pubDate>
      <link>https://dev.to/carrierone/ofac-sanctions-screening-for-developers-how-to-check-addresses-and-names-2gh1</link>
      <guid>https://dev.to/carrierone/ofac-sanctions-screening-for-developers-how-to-check-addresses-and-names-2gh1</guid>
      <description>&lt;h2&gt;
  
  
  OFAC Sanctions Screening for Developers: How to Check Addresses and Names
&lt;/h2&gt;

&lt;p&gt;Developing a KYC/AML compliance system requires thorough screening of potential users against various sanctions lists. One such list is the Office of Foreign Assets Control (OFAC) SDN (Specially Designated Nationals) list, which includes entities that are deemed high-risk by US Treasury due to their involvement in illicit activities.&lt;/p&gt;

&lt;p&gt;One way to integrate OFAC checks into your application is through an API endpoint provided by VeriLexData. The endpoint at &lt;code&gt;api.verilexdata.com/api/v1/sanctions/stats&lt;/code&gt; allows developers to screen addresses and names against the OFAC SDN list. Below is a simple Python example using this endpoint:&lt;/p&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;
python
import requests

def check_sanction(address_or_name):
    url = "https://api.verilexdata.com/api/v1/sanctions/stats"

    # Make sure the input is either an address or name (string)
    if not isinstance(address_or_name, str):
        raise ValueError("Input must be a string")

    # Prepare data to send
    payload = {"address": address_or_name}

    # Send POST request with the payload
    response = requests.post(url, json=payload)

    # Check if the API call was successful
    if response.status_code != 200:
        raise Exception("Failed
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;

</description>
    </item>
    <item>
      <title>Getting SEC EDGAR Filings via API Without Scraping</title>
      <dc:creator>carrierone</dc:creator>
      <pubDate>Fri, 01 May 2026 19:01:20 +0000</pubDate>
      <link>https://dev.to/carrierone/getting-sec-edgar-filings-via-api-without-scraping-1gml</link>
      <guid>https://dev.to/carrierone/getting-sec-edgar-filings-via-api-without-scraping-1gml</guid>
      <description>&lt;h2&gt;
  
  
  Getting SEC EDGAR Filings via API Without Scraping
&lt;/h2&gt;

&lt;p&gt;Working on financial applications often requires access to SEC filings such as 10-K, 10-Q, and 13-F reports. Historically, these documents have been obtained through scraping the SEC's EDGAR database, which can be time-consuming and prone to legal issues due to limitations in API usage.&lt;/p&gt;

&lt;p&gt;However, there is a more efficient way to access this data using an API. By leveraging an endpoint like &lt;code&gt;api.verilexdata.com/api/v1/sec/sample&lt;/code&gt;, you can fetch real-time filings without the hassle of scraping. This approach ensures your application stays compliant and streamlined.&lt;/p&gt;

&lt;h3&gt;
  
  
  Small Python Code Example
&lt;/h3&gt;

&lt;p&gt;Here’s a simple example in Python to get started:&lt;/p&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;
python
import requests

# Define API endpoint and parameters
url = "https://api.verilexdata.com/api/v1/sec/sample"
params = {
    'symbol': 'AAPL',  # Replace with the company symbol you're interested in
    'form_type': '10-K'  # You can also specify form type here, e.g., 10-Q
}

# Make a GET request to fetch data
response = requests.get(url, params=params)

# Check if the request was successful
if response.status_code == 200:
    # Process and use the response data as needed
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;

</description>
    </item>
  </channel>
</rss>
