Discover/Ohiosos API
live

Ohiosos APIbsportal.ohiosos.gov

Search and retrieve Ohio UCC financing statements by debtor name or filing number. Full party details, addresses, and amendment history via 3 endpoints.

This API takes change requests — .
Endpoint health
monitored
get_filing_details
search_by_debtor
search_by_filing_number
Checks pendingself-healing
Endpoints
3
Updated
2h ago

What is the Ohiosos API?

The Ohio Secretary of State UCC API exposes 3 endpoints for querying Uniform Commercial Code financing statements filed in Ohio. You can search by debtor name (organization or individual) via search_by_debtor, look up a specific financing statement with search_by_filing_number, and retrieve complete party details plus the full amendment and continuation history with get_filing_details. Responses include filing dates, lapse dates, debtor addresses, and secured party information.

This call costs5 credits / call— charged only on success
Try it
City to filter results by.
Last name of the individual debtor. Required when debtor_type is 'individual'.
First name of the individual debtor. Only used when debtor_type is 'individual'.
Whether the debtor is an organization or individual.
Middle name of the individual debtor. Only used when debtor_type is 'individual'.
When true, includes active filings plus those lapsing within a year. When false (default), returns only active filings.
Organization name to search for. Required when debtor_type is 'organization'.
api.parse.bot/scraper/318ac4ad-2267-45fa-b76c-d97fc3bb4d08/<endpoint>
Ready to send
Fill in the parameters and hit sign in to send to see live response data here.
Call it over HTTPgrab a free API key at signup
curl -X GET 'https://api.parse.bot/scraper/318ac4ad-2267-45fa-b76c-d97fc3bb4d08/search_by_debtor?debtor_type=organization&organization_name=Acme' \
  -H 'X-API-Key: $PARSE_API_KEY'
All endpoints · 3 totalmissing one? ·

Search Ohio UCC filings by debtor name. Supports both organization and individual debtor searches. For organizations, provide organization_name. For individuals, provide last_name and optionally first_name and middle_name. Returns a flat list of all matching filings with summary information including filing number, dates, type, and party names. The API returns all matching results in a single response with no server-side pagination. Results include entity_id which can be passed to get_filing_details for complete party and history information.

Input
ParamTypeDescription
citystringCity to filter results by.
last_namestringLast name of the individual debtor. Required when debtor_type is 'individual'.
first_namestringFirst name of the individual debtor. Only used when debtor_type is 'individual'.
debtor_typestringWhether the debtor is an organization or individual.
middle_namestringMiddle name of the individual debtor. Only used when debtor_type is 'individual'.
include_lapsingbooleanWhen true, includes active filings plus those lapsing within a year. When false (default), returns only active filings.
organization_namestringOrganization name to search for. Required when debtor_type is 'organization'.
Response
{
  "type": "object",
  "fields": {
    "total": "integer count of returned filings",
    "filings": "array of filing summary objects with filing_number, filing_date, lapse_date, filing_type, entity_id, debtors, and secured_parties"
  },
  "sample": {
    "data": {
      "total": 1,
      "filings": [
        {
          "debtors": [
            "The Acme Company"
          ],
          "entity_id": 4922935,
          "lapse_date": "04/22/2029",
          "filing_date": "04/22/2019",
          "filing_type": "Original",
          "filing_number": "OH00230022650",
          "secured_parties": [
            "Commercial Credit Group Inc. on behalf of itself and on behalf of all Affiliates of CCI"
          ]
        }
      ]
    },
    "status": "success"
  }
}

About the Ohiosos API

Searching UCC Filings

The search_by_debtor endpoint accepts either an organization_name or an individual debtor's last_name, first_name, and middle_name, controlled by the debtor_type parameter. An optional city filter narrows results geographically. By default, only active filings are returned; setting include_lapsing to true also includes filings scheduled to lapse within the next year. Each result in the filings array carries a filing_number, filing_date, lapse_date, filing_type, an entity_id, and summary arrays for debtors and secured_parties.

Lookup by Filing Number

search_by_filing_number takes a financing statement number directly (for example, OH00230022650) and returns the same filing summary shape as the debtor search. This is useful when you already hold a reference number from another data source and need to verify its current status or retrieve the entity_id required to pull full details.

Full Filing Details and History

get_filing_details accepts the entity_id returned by either search endpoint and returns the complete record. This includes the filing's status, filing_type, filing_date, and lapse_date, plus fully addressed debtors and secured_parties arrays — each entry provides a name, relationship_type, street address fields, and a pre-formatted full_address string. The filing_history array lists every registered amendment, continuation, termination, or assignment tied to that financing statement, with each entry showing its registered_date, document_name, reference_number, submission_id, and status.

Reliability & maintenance

The Ohiosos API is a managed, monitored endpoint for bsportal.ohiosos.gov — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when bsportal.ohiosos.gov changes and a check fails, the API is automatically queued for repair and re-verified. It is built to keep working as the site underneath it changes.

This isn't an official bsportal.ohiosos.gov API — it's an independent, maintained REST wrapper over public data. Where the source has no official API (or only a limited one), Parse gives you a stable contract over a source that never promised one, and keeps it current. Need a new endpoint or field? You can revise it yourself in plain English and the agent rebuilds it against the live site in minutes — contributing the change back to the shared API is free.

Will this API break when the source site changes?+
It's built not to. Every endpoint is health-checked on a schedule with automated test probes. When the source site changes and a check fails, the API is automatically queued for repair and re-verified — that's the self-healing layer. Each API page shows when its endpoints were last verified. And because marketplace APIs are shared, any fix reaches everyone using it.
Is this an official API from the source site?+
No — Parse APIs are independent, managed REST wrappers over publicly available data. That is the point: where a site has no official API (or only a limited one), Parse gives you a maintained, monitored endpoint for that data and keeps it working as the site changes — so you get a stable contract over a source that never promised one.
Can I fix or extend this API myself if I need a new endpoint or field?+
Yes — and you don't have to wait on us. This API was generated by the Parse agent, which stays attached. Describe the change in plain English ("add an endpoint that returns reviews", "fix the price field") in the revise box on the API page or via the revise_api MCP tool, and the agent rebuilds it against the live site in minutes. Contributing the change back to the public API is free.
What happens if I call an endpoint that has an issue?+
Errors are machine-readable: a bad call returns a clean status with the list of available endpoints and a repair hint, so an agent (or you) can recover or trigger a fix instead of failing silently. Confirmed failures feed the automatic repair queue.
Common use cases
  • Monitor when a competitor's equipment or inventory becomes encumbered by a new UCC lien using search_by_debtor.
  • Verify the secured parties on a target company's assets before a commercial loan or acquisition using get_filing_details.
  • Pull amendment and continuation histories to track how a financing statement has changed over time via filing_history.
  • Automate lapse-date alerts by flagging filings where lapse_date falls within a defined window using the include_lapsing filter.
  • Cross-reference a known filing number from court records with full debtor addresses using search_by_filing_number then get_filing_details.
  • Build a due-diligence tool that lists all active UCC liens against an individual debtor by name and city.
  • Aggregate secured party data across multiple debtors to identify which lenders are most active in a particular Ohio city.
Pricing & limitsSee full pricing →
TierPriceCredits/monthRate limit
Free$0/mo2005 req/min
Hobby$30/mo1,00020 req/min
Developer$100/mo5,000100 req/min
Team$300/mo20,000300 req/min
Company$1,000/mo100,000500 req/min

Each endpoint has a fixed posted price per successful call — most fall between 1 and 10 credits — shown on this API's page before you run it. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.

Frequently asked questions
Does the Ohio Secretary of State provide an official developer API for UCC filings?+
No public developer API is documented or published by the Ohio Secretary of State. The UCC search portal at bsportal.ohiosos.gov is a web interface intended for manual use; this Parse API provides programmatic access to that data.
What does `get_filing_details` return beyond what the search endpoints provide?+
The search endpoints (search_by_debtor and search_by_filing_number) return summary-level data: filing number, dates, filing type, and abbreviated debtor and secured party listings. get_filing_details adds the full street address for every debtor and secured party, the filing status field, and the complete filing_history array — which includes every amendment, continuation, termination, or assignment event with its own registered_date, document_name, reference_number, and submission_id.
Can I search for UCC filings in other states besides Ohio?+
No. Coverage is limited to UCC filings recorded with the Ohio Secretary of State. You can fork this API on Parse and revise it to point at another state's UCC portal to add coverage for additional jurisdictions.
Does the API return lapsed or terminated filings?+
By default, both search endpoints return only active filings. Setting the include_lapsing boolean to true expands results to include active filings plus those lapsing within the next year. Filings that have already lapsed or been terminated are not currently returned by any endpoint. You can fork this API on Parse and revise it to add a dedicated endpoint for historical or terminated filings if that scope is needed.
Is there pagination support for large debtor name searches?+
The endpoints return a flat list of all matching filings along with a total integer count; no pagination parameters such as page number or offset are currently exposed. For common organization names this may produce large result sets. You can fork this API on Parse and revise it to add pagination parameters if your use case requires it.
Page content last updated . Spec covers 3 endpoints from bsportal.ohiosos.gov.
Related APIs in Government PublicSee all →