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 Money Movement API

The Money Movement API from 401GO — 10 operation(s) for money movement.

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

Tagged areas include Money Movement. 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 19 operations across 10 paths. It is described by OpenAPI 3.2.0, at version 1.0.0.

Requests are made against the base URL https://app.401go.com/api.

19 operations 10 paths 0 schemas 3 DELETE9 GET3 POST4 PUT

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 Money Movement 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 19

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

Money Movement 19
GET
/participants/{participant_id}/disbursements/
Participants disbursements list
participants_disbursements_list 3 params → 200401403
POST
/participants/{participant_id}/disbursements/
Participants disbursements create
participants_disbursements_create 1 param body → 201400401403
GET
/participants/{participant_id}/disbursements-info/
Participants disbursements info retrieve
participants_disbursements_info_retrieve 4 params → 200400401403
GET
/participants/{participant_id}/disbursements/{disbursement_id}/
Participants disbursements retrieve
participants_disbursements_retrieve 2 params → 200
PUT
/participants/{participant_id}/disbursements/{disbursement_id}/
Participants disbursements update
participants_disbursements_update 2 params body → 200400401403
DELETE
/participants/{participant_id}/disbursements/{disbursement_id}/
Participants disbursements destroy
participants_disbursements_destroy 2 params → 204400401403
GET
/participants/{participant_id}/loan-requests/
Participants loan requests list
participants_loan_requests_list 3 params → 200401403
POST
/participants/{participant_id}/loan-requests/
Participants loan requests create
participants_loan_requests_create 1 param body → 200400401403
GET
/participants/{participant_id}/loan-requests-info/
Participants loan requests info retrieve
participants_loan_requests_info_retrieve 1 param → 200401403
PUT
/participants/{participant_id}/loan-requests-signature/{loan_request_id}/
Participants loan requests signature update
participants_loan_requests_signature_update 2 params body → 200400401403
GET
/participants/{participant_id}/loan-requests/{loan_request_id}/
Participants loan requests retrieve
participants_loan_requests_retrieve 2 params → 200401403
PUT
/participants/{participant_id}/loan-requests/{loan_request_id}/
Participants loan requests update
participants_loan_requests_update 2 params body → 200400401403
DELETE
/participants/{participant_id}/loan-requests/{loan_request_id}/
Participants loan requests destroy
participants_loan_requests_destroy 2 params → 204400401403
GET
/participants/{participant_id}/money-movement-history/
Participants money movement history list
participants_money_movement_history_list 3 params → 200401403
GET
/participants/{participant_id}/rollovers/
Participants rollovers list
participants_rollovers_list 3 params → 200401403
POST
/participants/{participant_id}/rollovers/
Participants rollovers create
participants_rollovers_create 1 param body → 201400401403
GET
/participants/{participant_id}/rollovers/{rollover_id}/
Participants rollovers retrieve
participants_rollovers_retrieve 2 params → 200401403
PUT
/participants/{participant_id}/rollovers/{rollover_id}/
Participants rollovers update
participants_rollovers_update 2 params body → 200400401403
DELETE
/participants/{participant_id}/rollovers/{rollover_id}/
Participants rollovers destroy
participants_rollovers_destroy 2 params → 204400401403

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

401go-money-movement-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 Notifications API
401GO Participants API
401GO Retirement Planning API
Where this information came from

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