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

Noyo Member Transactions API

The Member Transactions API from Noyo — 7 operation(s) for member transactions.

Noyo Member Transactions API is one of 64 APIs that Noyo publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

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

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

Requests are made against the base URL https://fulfillment.noyo.com.

7 operations 7 paths 35 schemas 7 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Base URL
https://fulfillment.noyo.com
Resource Areas
1

Paths & Operations 7

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

Member Transactions 7
GET
/api/v1/member_requests/{request_id}/member_transactions
Get a list of all Member Transactions
getMemberTransactionsByMemberRequestList 3 params → 200
GET
/api/v1/member_transactions
Get a list of all Member Transactions
getMemberTransactionsList 11 params → 200
GET
/api/v1/member_transactions/{transaction_id}
Get a single Member Transaction
getMemberTransaction 1 param → 200
GET
/api/v1/member_transactions/{transaction_id}/case
Get a Case for a Member Transaction
getMemberTransactionCase 1 param → 200
GET
/ui/v1/member_requests/{request_id}/member_transactions
Get a list of all Member Transactions by Member Request
uiGetMemberTransactionsByMemberRequestList 4 params → 200
GET
/ui/v1/member_snapshots/member_transaction/{transaction_id}
Gets member snapshot currently associated with a transaction
getUIMemberSnapshotByMemberTransaction 1 param → 200404
GET
/ui/v1/member_transactions/public
Get a list of all Member Transactions
uiGetMemberTransactionListPublic 9 params → 200

Schemas 35

The contract defines 35 schemas that model the data the API accepts and returns. The most detailed are UIMemberTransactionResult (16 properties), MemberTransactionResult (15 properties), InboundMemberSnapshotPerson (13 properties), OutboundMemberSnapshot (12 properties). Each schema is shown below with its type and property counts.

PaginatedMemberTransactionResult
object
2 properties 2 required
InboundMemberSnapshotAddress
object
6 properties 4 required
InboundMemberSnapshotCoverage
object
9 properties 3 required
GroupResult
object
9 properties 5 required
Meta
object
4 properties 3 required
MemberTransactionLabelPublicResult
object
8 properties 7 required
InboundMemberSnapshotEmploymentDates
object
5 properties 1 required
InboundMemberSnapshotPersonDisability
object
3 properties
CarrierFulfillmentStatus
object
3 properties 2 required
InboundMemberSnapshotSalary
object
4 properties
InboundMemberSnapshotOmittedCoverage
object
3 properties
InboundMemberSnapshotEmployee
object
7 properties 2 required
InboundMemberSnapshotEvent
object
4 properties 4 required
OutboundMemberSnapshot
object
12 properties 9 required
UIMemberTransactionResult
object
16 properties 11 required
InboundMemberSnapshotPersonContact
object
7 properties
LabelPublicResult
object
6 properties 5 required
InboundMemberSnapshotPCPDetails
object
1 property 1 required
InboundMemberSnapshotPersonTobacco
object
4 properties
MemberSnapshotDB
object
7 properties 2 required
MemberTransactionResult
object
15 properties 11 required
InboundMemberSnapshotPerson
object
13 properties 6 required
InboundMemberSnapshotCOBRADetails
object
5 properties 3 required
InboundMemberSnapshotPrimaryCareProvider
object
9 properties 2 required
InboundMemberSnapshotEnrolledMember
object
9 properties 3 required
MemberTransactionUIResult
object
4 properties
CaseResultPublic
object
8 properties 7 required
InboundMemberSnapshotPersonDetails
object
5 properties
PaginatedMemberTransactionUIResult
object
2 properties 2 required
InboundMemberSnapshotPersonAmericanIndian
object
2 properties
InboundMemberSnapshotOmittedCoverageCustom
object
1 property
InboundMemberSnapshotDependent
object
6 properties 2 required
StatusDetailResult
object
2 properties 2 required
OutboundMemberSnapshotCreatedMember
object
3 properties 2 required
InboundMemberSnapshotEmployment
object
5 properties 3 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

noyo-member-transactions-api-openapi.yml Raw ↑

Other APIs Noyo publishes across the network.

Noyo Carrier Mapped Field API
Noyo Carrier Sync API
Noyo Carriers API
Noyo Cases API
Noyo Condition API
Noyo Connection Eligibility API
Noyo Dependent API
Noyo Differences API
Noyo Discrepancies API
Noyo Eligibility Rules API
Noyo Employee API
Noyo Export API
Where this information came from

This is an independent, third-party profile of Noyo Member Transactions 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.