How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

The Administration for Children and Families v1 API

The v1 API from The Administration for Children and Families — 35 operation(s) for v1.

The Administration for Children and Families v1 API is one of 5 APIs that The Administration for Children and Families publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include v1. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 47 operations across 35 paths, and defines 17 schemas. It is described by OpenAPI 3.2.0, at version v1.

Requests are made against a single base URL, https://tanfdata.acf.hhs.gov/.

47 operations 35 paths 17 schemas 1 DELETE32 GET4 PATCH8 POST2 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
v1
Base URL
https://tanfdata.acf.hhs.gov/
Authentication
HTTP Basic
Resource Areas
1

Authentication & Security 1

The Administration for Children and Families v1 API declares 1 security scheme for authenticating requests. It accepts HTTP basic authentication (Basic). By default, every request must be authenticated.

Paths & Operations 47

Across 35 paths, the API surfaces 47 operations — 1 DELETE, 32 GET, 4 PATCH, 8 POST, 2 PUT. Each is listed below with its method, path, parameters, and response codes.

v1 47
GET
/v1/auth_check
Handle get request and verify user is authorized.
v1_auth_check_list → 200
GET
/v1/change-request-logs/
ViewSet for change request audit logs.
v1_change-request-logs_list 1 param → 200
GET
/v1/change-request-logs/{id}/
ViewSet for change request audit logs.
v1_change-request-logs_read 1 param → 200
GET
/v1/change-requests/
ViewSet for user change requests.
v1_change-requests_list 1 param → 200
GET
/v1/change-requests/{id}/
ViewSet for user change requests.
v1_change-requests_read 1 param → 200
GET
/v1/data_files/
Override to handle the list request with url param validation.
v1_data_files_list 3 params → 200
POST
/v1/data_files/
Override create to upload in case of successful scan.
v1_data_files_create body → 201
GET
/v1/data_files/years
Handle get action for get list of years there are datafiles.
v1_data_files_years_list 1 param → 200
GET
/v1/data_files/years/{stt}
Handle get action for get list of years there are datafiles.
v1_data_files_years_read 2 params → 200
GET
/v1/data_files/{id}/
Data file views.
v1_data_files_read 1 param → 200
GET
/v1/data_files/{id}/download/
Retrieve a file from s3 then stream it to the client.
v1_data_files_download 1 param → 200
GET
/v1/data_files/{id}/download_error_report/
Generate and return the parsing error report xlsx.
v1_data_files_download_error_report 1 param → 200
GET
/v1/feature-flags/
Get the feature flag list from the cache if available, else fetch the queryset.
v1_feature-flags_list → 200
GET
/v1/feature-flags/{feature_name}/
Get the feature flag from cache if available, fallback to db.
v1_feature-flags_read 1 param → 200
GET
/v1/feedback/
Feedback viewset.
v1_feedback_list 1 param → 200
POST
/v1/feedback/
Create feedback with user.
v1_feedback_create body → 201
GET
/v1/feedback/{id}/
Feedback viewset.
v1_feedback_read 1 param → 200
PUT
/v1/feedback/{id}/
Update feedback.
v1_feedback_update 1 param body → 200
PATCH
/v1/feedback/{id}/
Feedback viewset.
v1_feedback_partial_update 1 param body → 200
DELETE
/v1/feedback/{id}/
Override the destroy method to disallow it.
v1_feedback_delete 1 param → 204
GET
/v1/login/
Handle decoding auth token and authenticate user.
v1_login_list → 200
POST
/v1/login/
Define methods for handling login request from login.gov.
v1_login_create body → 201
GET
/v1/logout
Destroy user session.
v1_logout_list → 200
POST
/v1/logs/
Pass request bodies to the system logger.
v1_logs_create → 201
GET
/v1/oidc/ams
Handle decoding auth token and authenticate user.
v1_oidc_ams_list → 200
POST
/v1/oidc/ams
Define methods for handling login request from HHS AMS.
v1_oidc_ams_create body → 201
GET
/v1/reports/
Report file views.
v1_reports_list 1 param → 200
POST
/v1/reports/
Report file views.
v1_reports_create body → 201
GET
/v1/reports/report-sources/
Report source views for batch uploading report files.
v1_reports_report-sources_list 1 param → 200
POST
/v1/reports/report-sources/
Create a new report source and trigger async processing.
v1_reports_report-sources_create body → 201
GET
/v1/reports/report-sources/{id}/
Report source views for batch uploading report files.
v1_reports_report-sources_read 1 param → 200
GET
/v1/reports/{id}/
Report file views.
v1_reports_read 1 param → 200
GET
/v1/reports/{id}/download/
Retrieve a file from s3 then stream it to the client.
v1_reports_download 1 param → 200
GET
/v1/roles/
GET for groups (roles).
v1_roles_list → 200
POST
/v1/security/event-token
Process incoming Security Event Token from Login.gov.
v1_security_event-token_create → 201
GET
/v1/security/get-token
Generate new token for the API user.
v1_security_get-token_list → 200
GET
/v1/stts/
Simple view to get all STTs.
v1_stts_list → 200
GET
/v1/stts/alpha
Simple view to get all STTs alphabetized.
v1_stts_alpha_list → 200
GET
/v1/stts/by_region
Simple view to get all regions and STTs, without pagination.
v1_stts_by_region_list → 200
GET
/v1/users/
User accounts viewset.
v1_users_list 1 param → 200
GET
/v1/users/profile/
Get the current user's profile.
v1_users_profile 1 param → 200
GET
/v1/users/request_access/
Update request.user with provided data, set accountapprovalstatus to 'Access Request'.
v1_users_request_access_read 1 param → 200
PATCH
/v1/users/request_access/
Update request.user with provided data, set accountapprovalstatus to 'Access Request'.
v1_users_request_access_partial_update body → 200
PATCH
/v1/users/update_profile/
Update the current user's profile through change requests.
v1_users_update_profile body → 200
GET
/v1/users/{id}/
Return a specific user.
v1_users_read 1 param → 200
PUT
/v1/users/{id}/
User accounts viewset.
v1_users_update 1 param body → 200
PATCH
/v1/users/{id}/
User accounts viewset.
v1_users_partial_update 1 param body → 200

Schemas 17

The contract defines 17 schemas that model the data the API accepts and returns. The most detailed are UserProfileChangeRequest (25 properties), DataFile (21 properties), UserProfile (19 properties), User (16 properties). Each schema is shown below with its type and property counts.

DataFile
object
21 properties 8 required
UserChangeRequest
object
6 properties 2 required
Group
object
3 properties 2 required
ReportSource
object
12 properties
User
object
16 properties
FeedbackAttachments
object
2 properties 2 required
STT
object
9 properties 1 required
UserProfileChangeRequest
object
25 properties 2 required
Permission
object
4 properties 2 required
Region
object
2 properties 2 required
FeatureFlag
object
4 properties 1 required
AuthToken
object
3 properties 2 required
ReportFile
object
11 properties 2 required
DataFileSummary
object
3 properties 1 required
Feedback
object
9 properties 1 required
UserProfile
object
19 properties 2 required
ChangeRequestAuditLog
object
6 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

the-administration-for-children-and-families-v1-api-openapi.yml Raw ↑

Other APIs The Administration for Children and Families publishes across the network.

TANF Data Portal
National Data Archive on Child Abuse and Neglect
ACF Data and Research Portal
The Administration for Children and Families plg_auth_check API
Where this information came from

This is an independent, third-party profile of The Administration for Children and Families v1 API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.