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

401GO Retirement Planning API

The Retirement Planning API from 401GO — 3 operation(s) for retirement planning.

401GO Retirement Planning API is one of 10 APIs that 401GO publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Retirement Planning. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, a getting-started guide, and authentication docs.

This API exposes 4 operations across 3 paths. It is described by OpenAPI 3.2.0, at version 1.0.0.

Requests are made against a single base URL, https://app.401go.com/api.

4 operations 3 paths 0 schemas 3 GET1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Base URL
https://app.401go.com/api
Authentication
API Key, HTTP Bearer
Resource Areas
1

Authentication & Security 2

401GO Retirement Planning API declares 2 security schemes for authenticating requests. An API key is passed in the header as Authorization (knoxApiToken). It accepts HTTP bearer tokens (oauth2).

  • knoxApiToken — Token-based authentication with required prefix "Token"
  • oauth2 — OAuth 2.0 Bearer based with an existing token. Enter a token retrieved via the regular OAuth flow elsewhere.

Paths & Operations 4

Across 3 paths, the API surfaces 4 operations — 3 GET, 1 POST. Each is listed below with its method, path, parameters, and response codes.

Retirement Planning 4
GET
/participants/{participant_id}/advisor-models/
participants_advisor_models_retrieve 1 param → 200
POST
/participants/{participant_id}/advisor-models/
participants_advisor_models_create 3 params body → 200400404401403
GET
/participants/{participant_id}/retirement-planning-defaults/
Get the defaults used for the estimation. Note that the defaults returned may not be valid for getting an estimate, for example if age retirementage.
participants_retirement_planning_defaults_retrieve 1 param → 200401403
GET
/participants/{participant_id}/retirement-planning-estimate/
Estimate a participant's projected balance and target savings for retirement. Will use the defaults as defined from the retirement-planning-defaults unless an override is given. Can only be used if t…
participants_retirement_planning_estimate_list 14 params → 200400401403

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

401go-retirement-planning-api-openapi.yml Raw ↑

Other APIs 401GO publishes across the network.

401GO Affiliates & Firms API
401GO Beneficiaries API
401GO Companies & Plans API
401GO Contributions & Payroll API
401GO Documents API
401GO Investments & Portfolios API
401GO Money Movement API
401GO Notifications API
401GO Participants API
Where this information came from

This is an independent, third-party profile of 401GO Retirement Planning 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.