{
"success": true,
"count": 5,
"state": "TX",
"source": "NPPES",
"results": [
{
"source": "NPPES",
"npiNumber": "1851585871",
"personName": "Mr. ARNOLD SMITH Jr.",
"firstName": "ARNOLD",
"lastName": "SMITH",
"credential": "RNFA",
"licenseType": "RN",
"taxonomyDescription": "Registered Nurse, Registered Nurse First Assistant",
"taxonomyCode": "163WR0006X",
"taxonomyLicense": "685166",
"taxonomyState": "TX",
"status": "Active",
"enumerationDate": "2007-09-03",
"lastUpdated": "2007-09-03",
"city": "KERRVILLE",
"state": "TX",
"postalCode": "780285329",
"sex": "M",
"allTaxonomies": [
{
"code": "163WR0006X",
"description": "Registered Nurse, Registered Nurse First Assistant",
"license": "685166",
"state": "TX",
"primary": true
}
],
"note": "NPI status reflects NPI enrollment, not license status."
},
{
"source": "NPPES",
"npiNumber": "1518887140",
"personName": "CYNTHIA JO SMITH",
"firstName": "CYNTHIA",
"lastName": "SMITH",
"credential": "MSN, RN",
"licenseType": "RN",
"taxonomyDescription": "Registered Nurse, Diabetes Educator",
"taxonomyCode": "163WD0400X",
"taxonomyLicense": "533892",
"taxonomyState": "TX",
"status": "Active",
"enumerationDate": "2026-07-15",
"lastUpdated": "2026-07-15",
"city": "TEXARKANA",
"state": "TX",
"postalCode": "755032372",
"sex": "F",
"allTaxonomies": [
{
"code": "163WD0400X",
"description": "Registered Nurse, Diabetes Educator",
"license": "533892",
"state": "TX",
"primary": true
}
],
"note": "NPI status reflects NPI enrollment, not license status."
},
{
"source": "NPPES",
"npiNumber": "1306494810",
"personName": "JOANNE ELAINE SMITH",
"firstName": "JOANNE",
"lastName": "SMITH",
"credential": "AGPCNP-BC",
"licenseType": "NP",
"taxonomyDescription": "Nurse Practitioner, Gerontology",
"taxonomyCode": "363LG0600X",
"taxonomyLicense": "AP143250",
"taxonomyState": "TX",
"status": "Active",
"enumerationDate": "2019-08-28",
"lastUpdated": "2025-05-29",
"city": "SAN ANTONIO",
"state": "TX",
"postalCode": "78232",
"sex": "F",
"allTaxonomies": [
{
"code": "163WH1000X",
"description": "Registered Nurse, Hospice",
"license": "729919",
"state": "TX",
"primary": false
},
{
"code": "363LG0600X",
"description": "Nurse Practitioner, Gerontology",
"license": "AP143250",
"state": "TX",
"primary": true
}
],
"note": "NPI status reflects NPI enrollment, not license status."
},
{
"source": "NPPES",
"npiNumber": "1003627019",
"personName": "MARGARET SMITH",
"firstName": "MARGARET",
"lastName": "SMITH",
"credential": null,
"licenseType": "RN",
"taxonomyDescription": "Registered Nurse, Diabetes Educator",
"taxonomyCode": "163WD0400X",
"taxonomyLicense": "1066379",
"taxonomyState": "TX",
"status": "Active",
"enumerationDate": "2025-01-17",
"lastUpdated": "2025-01-17",
"city": "WINTERS",
"state": "TX",
"postalCode": "795676417",
"sex": "F",
"allTaxonomies": [
{
"code": "163WD0400X",
"description": "Registered Nurse, Diabetes Educator",
"license": "1066379",
"state": "TX",
"primary": true
}
],
"note": "NPI status reflects NPI enrollment, not license status."
},
{
"source": "NPPES",
"npiNumber": "1609698125",
"personName": "SHARON SMITH",
"firstName": "SHARON",
"lastName": "SMITH",
"credential": "RN BSN",
"licenseType": "RN",
"taxonomyDescription": "Registered Nurse, General Practice",
"taxonomyCode": "163WG0000X",
"taxonomyLicense": "596951",
"taxonomyState": "TX",
"status": "Active",
"enumerationDate": "2024-10-28",
"lastUpdated": "2024-10-28",
"city": "KERRVILLE",
"state": "TX",
"postalCode": "780285819",
"sex": "F",
"allTaxonomies": [
{
"code": "163WG0000X",
"description": "Registered Nurse, General Practice",
"license": "596951",
"state": "TX",
"primary": true
}
],
"note": "NPI status reflects NPI enrollment, not license status."
}
]
}
curl --location --request GET 'https://zylalabs.com/api/13726/nurse+license+verification+api/31460/verify+nurse+license' --header 'Authorization: Bearer YOUR_API_KEY'
After signing up, every developer is assigned a personal API access key, a unique combination of letters and digits provided to access to our API endpoint. To authenticate with the Nurse License Verification API simply include your bearer token in the Authorization header.
| Header | Description |
|---|---|
Authorization
|
Required
Should be Bearer access_key. See "Your API Access Key" above when you are subscribed.
|
No long-term commitment. Upgrade, downgrade, or cancel anytime. Free Trial includes up to 50 requests.
(Save 2 months with annual billing 🎉)
The API returns detailed information about nursing licenses, including practitioner name, credential, license type, license number, state, NPI number, city, and status. For Florida, it includes deep state board verification with official status and expiration dates.
Key fields in the response include `personName`, `credential`, `licenseType`, `npiNumber`, `status`, `city`, `state`, and `taxonomyDescription`. These fields provide essential details about the nurse's qualifications and licensing status.
Users can search by last name, first name, or license number. Additionally, they can filter results by license type (RN, LPN, NP, APRN) to customize their data requests effectively.
The response data is structured in a JSON format, containing a success flag, count of results, and an array of results. Each result includes detailed fields about the practitioner, making it easy to parse and utilize.
The data is sourced from official federal and state databases, including the NPI registry. For Florida, the API employs deep state board verification to ensure accuracy and reliability.
Typical use cases include verifying the credentials of nursing professionals for employment, ensuring compliance with regulations, and conducting background checks for healthcare providers.
Users can utilize the returned data to confirm a nurse's licensing status, assess qualifications, and ensure they meet state-specific requirements. The structured format allows for easy integration into applications or reports.
Data accuracy is maintained through regular updates from official sources and deep verification processes, especially for Florida licenses. This ensures that users receive the most current and reliable information available.
To obtain your API key, first sign in to your account and navigate to the API you want to use. From the API's Pricing section, choose a plan and complete the subscription process. Once subscribed, return to the API page and you will see your API Access Key displayed at the top of the documentation page. You can use this key to authenticate your requests.
You can’t switch APIs during the free trial. If you subscribe to a different API, your trial will end and the new subscription will start as a paid plan.
The free trial lasts for 7 days and allows you to make up to 50 API requests.
No, the free trial is available only once, so we recommend using it on the API that interests you the most. Most of our APIs offer a free trial, but some may not include this option.
Yes. If the API offers a free trial, you will see a "Free 7-Day Trial" option in its Pricing section. The trial lasts for 7 days and allows up to 50 API requests, enabling you to evaluate the API before subscribing to a paid plan.
Zyla API Hub is like a big store for APIs, where you can find thousands of them all in one place. We also offer dedicated support and real-time monitoring of all APIs. Once you sign up, you can pick and choose which APIs you want to use. Just remember, each API needs its own subscription. But if you subscribe to multiple ones, you'll use the same key for all of them, making things easier for you.
You can monitor your API usage through the response headers included with every request:
x-zyla-api-calls-monthly-used: Shows the total number of API requests you have used during the current billing period.
x-zyla-api-calls-monthly-remaining: Shows the number of API requests you have remaining for the current billing period.
Yes, you can cancel your subscription at any time. Simply go to the Pricing section of the API you're subscribed to and click the "Unsubscribe" button.
Please note that upgrades, downgrades, and cancellations take effect immediately. Once your subscription is canceled, access to the service will end immediately, regardless of any remaining API calls in your quota.
Please have a look at our Refund Policy: https://zylalabs.com/terms#refund