AmeriCorps · Authentication Profile
Americorps Authentication
Authentication
AmeriCorps secures its APIs with apiKey across 1 declared security scheme, as derived from its OpenAPI definitions.
Federal-GovernmentNational ServiceVolunteerismCommunity DevelopmentCivic EngagementEducationDisaster ResponseEnvironmental Conservation
Methods: apiKey
Schemes: 1
OAuth flows:
API key in: header
Security Schemes
SocrataAppToken apiKey
· in: header (X-App-Token)
Source
Authentication Profile
generated: '2026-09-02'
method: searched
source: >-
https://dev.socrata.com/docs/app-tokens.html — the application-token reference the
AmeriCorps portal's API documentation link resolves to — reconciled with the
securitySchemes declared in openapi/_original/americorps-openapi.yml and verified by live
anonymous calls to data.americorps.gov on 2026-09-02.
docs: https://dev.socrata.com/docs/app-tokens.html
summary:
types:
- apiKey
api_key_in:
- header
anonymous_allowed: true
oauth2: false
openid_connect: false
mutual_tls: false
posture: >-
Optional-credential public API. Anonymous access is the DEFAULT and returns full data;
the credential is a throttling identity, not an authorization grant. Verified live:
GET https://data.americorps.gov/resource/fzpw-9z8s.json?$limit=1 returned 200 with data
and no credential presented.
schemes:
- name: SocrataAppToken
type: apiKey
in: header
parameter: X-App-Token
required: false
description: >-
Optional Socrata application token. Anonymous access is allowed, but requests without a
token draw from a shared per-IP pool and may be throttled.
what_it_grants: >-
Nothing additional. Per the platform documentation a token does not confer access to
any dataset an anonymous caller cannot already read — the AmeriCorps datasets are all
accessLevel "public". Its only effect is that tokened requests are not throttled unless
judged abusive.
obtain: >-
Register a free Socrata developer account and create an application token. No AmeriCorps
approval, contract or agency relationship is involved, and there is no cost.
legacy_alternatives:
- parameter: $$app_token
in: query
note: SODA 2.0 / 2.1 legacy form.
- parameter: app_token
in: query
note: SODA 1.0 legacy form.
sources:
- openapi/_original/americorps-openapi.yml
- https://dev.socrata.com/docs/app-tokens.html
discovery:
well_known_openid_configuration:
url: https://data.americorps.gov/.well-known/openid-configuration
status: 404
well_known_oauth_authorization_server:
url: https://data.americorps.gov/.well-known/oauth-authorization-server
status: 404
well_known_oauth_protected_resource:
url: https://data.americorps.gov/.well-known/oauth-protected-resource
status: 404
detail: >-
No authentication discovery document is served on either AmeriCorps host. An agent cannot
learn the auth model from the wire; it must read the docs or the OpenAPI.
non_public_surface:
note: >-
Private/unpublished Socrata assets return 403 rather than 404, but AmeriCorps exposes no
self-serve path to request access to one. The published contactPoint for the catalog is
Evaluation@americorps.gov (AmeriCorps Office of Research and Evaluation, from
https://data.americorps.gov/data.json).
Work with this as data
Every security artifact here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for security posture
4 MCP tools reach this
find_securityBrowse and filter every security artifact in the catalog.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
This security artifact
curl "https://apis.io/api/v1/security/americorps-authentication"
All security posture
curl "https://apis.io/api/v1/security?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.