ND Secretary of State API: Business Lookup Guide

North Dakota Secretary of State API: Complete Developer Guide

If you're building applications that require North Dakota business entity data, you need reliable access to Secretary of State records. OpenSOSData provides a REST API that connects directly to ND SOS databases, delivering real-time entity information without the friction of manual lookups or unreliable web scraping.

This guide covers everything you need to know about integrating the ND Secretary of State API into your application, from authentication to response parsing.

Why Use an API for ND Secretary of State Lookups?

The North Dakota Secretary of State maintains records on all registered business entities in the state. Manually querying their website doesn't scale. An API approach offers:

Programmatic access: Integrate lookups directly into your workflow without manual intervention
Real-time data: Query current business status, registered agents, and officer information on demand
Cost efficiency: Pay only for lookups you use at $0.0314 per request
Developer experience: Standard REST endpoint, JSON responses, comprehensive documentation
Caching: 7-day Redis cache reduces redundant requests and speeds up repeated lookups

What Data Does the ND Secretary of State API Return?

OpenSOSData retrieves the following fields for each North Dakota business entity:

Entity name (registered business name)
Entity type (LLC, Corporation, Partnership, etc.)
State ID number (unique identifier)
Current status (Active, Dissolved, etc.)
Formation date
Registered agent name and address
Principal business address
Officer names and titles

This data structure covers standard due diligence, KYC, and business intelligence workflows. The API returns structured JSON, making integration straightforward for most development stacks.

Pricing: North Dakota SOS API

OpenSOSData charges $0.0314 per lookup—a rate that reflects the mathematical constant Pi. There's no subscription, no monthly minimums, and no hidden fees.

Cost comparison:

OpenSOSData: $0.0314 per lookup
OpenCorporates: $0.10–$0.50 per lookup
Cobalt Intelligence: $0.50–$2.00 per lookup
Middesk: $1.00+ per lookup

To get started, you need a minimum wallet balance of $3.14 (which covers 100 lookups). No commitment, no contracts.

Quick Start: Making Your First ND Secretary of State API Call

Here's how to query a North Dakota business entity:

Step 1: Sign up at OpenSOSData

Visit https://opensosdata.com and join the waitlist. You'll receive API credentials and wallet setup instructions.

Step 2: Fund your wallet

Add a minimum of $3.14 to your account. This gives you 100 lookups to work with.

Step 3: Make a request

Use the endpoint POST https://api.opensosdata.com/v1/lookup with the following curl example:

curl -X POST https://api.opensosdata.com/v1/lookup \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "state": "ND",
    "entity_name": "Acme Corporation"
  }'

Step 4: Parse the JSON response

The API returns structured entity data. A successful response includes all registered information for the matching entity. If you need fresh data instead of cached results, add ?fresh=true to force a real-time scrape of the ND Secretary of State database.

API Response Structure

OpenSOSData returns JSON with the following schema:

{
  "entity_name": "Acme Corporation",
  "entity_type": "Corporation",
  "state_id": "1234567",
  "status": "Active",
  "formation_date": "2015-03-22",
  "registered_agent": {
    "name": "John Smith",
    "address": "123 Main St, Bismarck, ND 58501"
  },
  "principal_address": "456 Business Ave, Fargo, ND 58102",
  "officers": [
    {
      "name": "Jane Doe",
      "title": "President"
    },
    {
      "name": "Bob Johnson",
      "title": "Secretary"
    }
  ]
}

All fields are optional depending on what the Secretary of State has recorded for that entity.

Caching and Fresh Data

OpenSOSData maintains a 7-day Redis cache for all ND lookups. This means repeated requests for the same entity return instantly from cache, reducing latency and API costs.

If you need real-time data (for example, during an acquisition due diligence process), append ?fresh=true to your request. This bypasses the cache and performs a live scrape of the North Dakota Secretary of State database, ensuring you have the absolute latest information.

Use Cases for the ND Secretary of State API

KYC and compliance: Verify business registration status and registered agents during onboarding.

Due diligence: Retrieve officer information and formation dates for M&A workflows.

Risk assessment: Monitor business status changes across your portfolio of North Dakota entities.

B2B intelligence: Build business lookup tools or platforms that require ND entity data.

Vendor management: Automate verification that your vendors are properly registered in North Dakota.

State Coverage and Future Expansion

OpenSOSData currently covers 49 states and territories, including North Dakota. Coverage includes CA, UT, WY, DE, AK, MT, AR, TX, CO, IN, ME, MD, IA, LA, KY, GA, NH, OH, MI, MN, ND, NJ, NE, MO, PA, TN, WA, SC, WI, OR, SD, IL, ID, CT, AL, NC, FL, HI, VA, MA, RI, NY, VT, NV, NM, WV, AZ, PR, VI, DC, AS, OK, MS, and KS.

This means you can build multi-state lookups with a single API integration, using the same endpoint and authentication credentials across all covered jurisdictions.

Authentication and Security

OpenSOSData uses bearer token authentication. Include your API key in the Authorization header of every request:

Authorization: Bearer YOUR_API_KEY

All requests use HTTPS. Your API key should be treated like a password—store it in environment variables, not in version control.

Rate Limits and Best Practices

There are no published rate limits documented in our system, making OpenSOSData suitable for both small scripts and high-volume integrations. However, best practices include:

Use the 7-day cache whenever possible to reduce costs and latency
Batch requests when performing bulk lookups
Cache results on your end if you're querying the same entity multiple times per day
Use ?fresh=true sparingly—only when you need guaranteed real-time data

Integration Examples

The OpenSOSData REST API works with any programming language. Common integration patterns include:

Python: Use the requests library to make HTTP calls and parse JSON responses.

Node.js: Use fetch or axios to query the endpoint and handle async responses.

Go: Use the standard net/http package to construct POST requests.

Full code examples and SDKs are available in the OpenAPI documentation at https://opensosdata.com/openapi.yaml.

Troubleshooting Common Issues

No results found: Verify the entity name matches exactly what's registered with the ND Secretary of State. Try alternative spellings or search by state ID if available.

401 Unauthorized: Check that your API key is correct and included in the Authorization header.

Stale data: If you're seeing outdated information, use the ?fresh=true parameter to force a real-time lookup.

Insufficient wallet balance: Add funds to your account at https://opensosdata.com.

Why Choose OpenSOSData for ND Secretary of State Lookups?

OpenSOSData is built by developers for developers. We understand that reliability, affordability, and simplicity matter. At $0.0314 per lookup with no subscription required, you get direct access to North Dakota business data without the overhead of traditional business intelligence platforms.

The API is actively maintained, covers all major US states and territories, and integrates in minutes. For teams doing compliance work, KYC, or building business tools, OpenSOSData eliminates the friction of manual SOS lookups.

Get Started Today

Ready to integrate North Dakota Secretary of State data into your application? Head to https://opensosdata.com to join the waitlist, fund your wallet with a minimum of $3.14, and start making API calls.

Full API documentation is available at https://opensosdata.com/openapi.yaml. Questions? Check the docs or contact support directly through the platform.

Query North Dakota Secretary of State Data with OpenSOSData API