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 Plan Mapping Rule API

The Plan Mapping Rule API from Noyo — 3 operation(s) for plan mapping rule.

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

Tagged areas include Plan Mapping Rule. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 5 operations across 3 paths, and defines 6 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.

5 operations 3 paths 6 schemas 1 DELETE2 GET1 POST1 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://fulfillment.noyo.com
Resource Areas
1

Paths & Operations 5

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

Plan Mapping Rule 5
GET
/api/v1/group_mappings/{group_mapping_id}/plan_mapping_rules
Get Plan Mapping Rules for a Group Mapping
getPlanMappingRulesForGroupMapping 1 param → 200
POST
/api/v1/group_mappings/{group_mapping_id}/plan_mapping_rules
Create a new Plan Mapping Rule
createNewPlanMappingRule 1 param body → 201
GET
/api/v1/plan_mapping_rules/{plan_mapping_rule_id}
Get a Plan Mapping Rule
getPlanMappingRule 1 param → 200
DELETE
/api/v1/plan_mapping_rules/{plan_mapping_rule_id}/{version}
Delete a Plan Mapping Rule
deletePlanMappingRule 2 params → 204
PUT
/api/v1/plan_mapping_rules/{plan_mapping_rule_id}/{version}
Edit a Plan Mapping Rule
editPlanMappingRule 2 params body → 200

Schemas 6

The contract defines 6 schemas that model the data the API accepts and returns. The most detailed are PlanMappingRuleDetails (14 properties), PlanMappingRuleResult (6 properties), Meta (4 properties), PaginatedPlanMappingRuleResult (2 properties). Each schema is shown below with its type and property counts.

PlanMappingRuleDetails
object
14 properties
PaginatedPlanMappingRuleResult
object
2 properties 2 required
Meta
object
4 properties 3 required
PlanMappingRuleCreateRequest
object
1 property 1 required
PlanMappingRuleResult
object
6 properties 6 required
PlanMappingRuleEditRequest
object
1 property 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

noyo-plan-mapping-rule-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 Plan Mapping Rule 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.