Tribes Names Service
Description
The Tribes Names Service is the EPA tribal web service for non-geospatial systems. It automatically maintains accurate and current tribal information like current tribal names, BIA codes, and EPA Internal Identifiers. It enables systems and applications to automatically comply with the Tribal Identification Data Standard.
Data
Data provided by this service is regularly updated. Tribal names are obtained from BIA’s official list of federally recognized tribes that is published at least annually in the Federal Register. The Tribes Service applies a unique EPA Internal Identifier to each tribe. This ensures the correct identification of tribal partners and can be used to identify name changes over time. EPA Internal Identifiers are more reliable and available that BIA codes, which are not currently provided for Alaska Native entities and some American Indian entities
Technology
The Tribes Names Service application is hosted in EPA’s CDX Azure cloud environment. The services are available for public use and require no registration, authorization, or authentication tokens. The services are documented with OpenAPI specification and can be explored via Swagger UI.
The Tribes Names Service API is comprised of the following three services /api/v1/tribes, /api/v1/tribeDetails, and /api/v1/tribeDetails/{epaTribalInternalId}. These services can be used to lookup tribal information by query using the available parameters to provide responses in JSON format.
Access the Swagger UI page here!
Example Use Cases
Below is a list of example use cases that can be used as a reference to assist users with executing or implementing the TRIBES NAMES Services.
Note: This is a public application, and there is no authentication requirement to use these services. When attempting to add parameters into the Swagger, the User must select “Try it out” before entering information needed to execute a search.
Example Use Case 1: Get all Basic Tribal Data
This case can be used if the User wants to return all “Basic Tribal Data”, or if the User needs to view associated data for any/all “Tribal Names”, “BIA Codes”, “Tribal Name Start Date(s)”, “EPA Locations” and/or “Tribal Internal Id” information.
Request: GET /api/v1/tribes
Input: No parameters are defined for this case. This is an example of a null parameter. However, if the User wants to limit the search; entering a parameter is suggested. There are additional examples of defined parameters in “Example Use Case(s) 1 & 2”.
Output:
{
"biaTribalCodes": null,
"epaLocations": null,
"names": null,
"relationships": null,
"epaTribalInternalId": 100000001,
"currentName": "Absentee-Shawnee Tribe of Indians of Oklahoma",
"currentNameStartDate": "1982-11-24",
"currentNameEndDate": null,
"currentBIATribalCode": "820",
"currentBIARecognizedFlag": true,
"commentText": null
},…
Example Use Case 2: Get all Detailed Tribe information
Returning “Tribe Details” can be used to gather all Tribal data available in the service. Additionally, it can be used as a lookup reference for associated related data, unlike “Example User Case 1”.
The user can view specific Tribal information if a query parameter is set. For instance, if a User wanted to lookup information for a tribe where the BIA Tribal Code=584.
Request: GET /api/v1/tribeDetails?biaTribalCode=584
Input: BiaTribalCode=584
Output:
[
{
"biaTribalCodes": [
{
"code": "584",
"startDate": "1000-01-01",
"endDate": null,
"commentText": null
}
],
"epaLocations": [
{
"stateCode": "CA",
"stateName": "California",
"epaRegionName": "Region 9",
"startDate": "1000-01-01",
"endDate": null
}
],
"names": [
{
"name": "Aqua-Caliente Band of Cahuilla Indians (Palm Springs), Aqua Caliente Indian Reservation, California",
"startDate": "1000-01-01",
"endDate": "1982-11-24",
"commentText": null
},
{
"name": "Agua Caliente Band of Cahuilla Indians of the Agua Caliente Indian Reservation, Palm Springs, California",
"startDate": "1982-11-24",
"endDate": "1988-12-29",
"commentText": null
},
{
"name": "Agua Caliente Band of Cahuilla Indians of the Agua Caliente Indian Reservation, California",
"startDate": "1988-12-29",
"endDate": null,
"commentText": null
}
],
"relationships": [
{
"relativeEPATribalInternalId": null,
"relationshipTypeCode": null,
"relationshipTypeName": null,
"relationshipTypeDescription": null
}
],
"epaTribalInternalId": 100000002,
"currentName": "Agua Caliente Band of Cahuilla Indians of the Agua Caliente Indian Reservation, California",
"currentNameStartDate": "1988-12-29",
"currentNameEndDate": null,
"currentBIATribalCode": "584",
"currentBIARecognizedFlag": true,
"commentText": null
}
]
Example Use Case 3: Get Detailed Tribe Information by EPA Tribal Internal Id
A User can use this service if an “EPA Tribal Internal Id” is known. Note: EPA Tribal Internal Ids can be obtained after using either “Example Use Case 1” or “Example Use Case 2”.
Request: GET /api/v1/tribeDetails/100000002
Input: Query parameter= 100000002
Output:
[
{
"biaTribalCodes": [
{
"code": "584",
"startDate": "1000-01-01",
"endDate": null,
"commentText": null
}
],
"epaLocations": [
{
"stateCode": "CA",
"stateName": "California",
"epaRegionName": "Region 9",
"startDate": "1000-01-01",
"endDate": null
}
],
"names": [
{
"name": "Aqua-Caliente Band of Cahuilla Indians (Palm Springs), Aqua Caliente Indian Reservation, California",
"startDate": "1000-01-01",
"endDate": "1982-11-24",
"commentText": null
},
{
"name": "Agua Caliente Band of Cahuilla Indians of the Agua Caliente Indian Reservation, Palm Springs, California",
"startDate": "1982-11-24",
"endDate": "1988-12-29",
"commentText": null
},
{
"name": "Agua Caliente Band of Cahuilla Indians of the Agua Caliente Indian Reservation, California",
"startDate": "1988-12-29",
"endDate": null,
"commentText": null
}
],
"relationships": [
{
"relativeEPATribalInternalId": null,
"relationshipTypeCode": null,
"relationshipTypeName": null,
"relationshipTypeDescription": null
}
],
"epaTribalInternalId": 100000002,
"currentName": "Agua Caliente Band of Cahuilla Indians of the Agua Caliente Indian Reservation, California",
"currentNameStartDate": "1988-12-29",
"currentNameEndDate": null,
"currentBIATribalCode": "584",
"currentBIARecognizedFlag": true,
"commentText": null
}
]