> ## Documentation Index > Fetch the complete documentation index at: https://docs.m1amdocs.com/llms.txt > Use this file to discover all available pages before exploring further. # Merchant Initiated Subscription Update ## OpenAPI ````yaml /marketONE/MarketONEAPIs.yaml post /partnersub/v2/partnerSubscription/{id}/update/validate openapi: 3.0.1 info: title: MarketONE APIs description: > The MarketONE OpenAPIs provide a quick and easy way to access MarketONE features and your data. These APIs let Resellers (Service Providers) and Merchants work together to resell products and handle billing on a single platform. With an API key, you can authenticate and perform various tasks, like accessing and managing data. You can use an HTTP client in any programming language to send HTTP requests to MarketONE to create, edit, or delete data. The data you work with, like subscriptions or entitlements, are called resources, and each resource has its own endpoint (URL). The MarketONE OpenAPIs use built-in HTTP features, like HTTP authentication and HTTP verbs, which are easy for standard HTTP clients to understand. They also use HTTP response codes to indicate errors. All responses, including errors, are in JSON format, but our API libraries convert them into objects that are specific to the programming language you're using. You can also download the MarketONE OpenAPIs in a YAML file, which is easy to read and manage. For more information about the MarketONE OpenAPIs, see the [API Reference Guide for Merchants](https://docs.saas.amdocs.com/bundle/b_partnerAPIGuide/) and the [API Reference Guide for Resellers (Service Providers)](https://docs.saas.amdocs.com/bundle/b_aggregatorAPIGuide). ## Other MarketONE APIs Other MarketONE APIs, such as the [Reseller (CSP) Adapter OpenAPIs](https://docs.saas.amdocs.com/bundle/MarketONECSPAdapter/page/index.html), the [Merchant (OTT) Service Callbacks](https://docs.saas.amdocs.com/bundle/MarketONEOTTServiceCallbacks/page/index.html), and the [Commerce Gateway OpenAPIs](https://docs.saas.amdocs.com/bundle/Amdocs_Media-Commerce-Gateway-Latest-resolved/page/index.html), are available to provide additional services for specific organizations. # Environments MarketONE provides two distinct environments for testing and production: - **Prodtest environment**: this is a pre-production environment allowing you to test your application with test data. Use server . - **Production environment**: this is the live environment for the real-world implementation of data. Use server . # HTTP Verbs The MarketONE OpenAPIs support the following HTTP verbs: - **GET**: Retrieve resources (as a list or single record fetch). - **POST**: Create new resources or update existing ones (overloading during create/update is permitted where specified). - **PUT**: Create a new resource or replace a resource with the request payload. - **DELETE**: Remove ownership or hierarchical association between certain resources. # Example ## Request Example ``` POST /v1/entitlement Content-Type: application/json { "account": { "id": "2922fbf1-1dc4-2293-9d0e-c9a46630ad6e" }, "subscriptionId": "ef1917b8-4a06-4595-9998-718799a33ed6", "productCodes": [ "Basic_Addon" ], "metadata": { "email": "j.smith@email.com" } } ``` ## Response Example ``` Response: 200 OK Content-Type: application/json [ { "partnerSubscriptionId": "80e08955-b0e9-4ba6-b882-b24230bfc703", "account": { "id": "0006fbf1-1ac4-4793-9d0e-c0a0080ad6e", "partnerCustomerId": "1bbbb3a5-0f05-4009-b4ae-b01f7eba7g" }, "subscriptionId": "ef1417b8-4a06-7775-8518-718714a33ed2", "externalPartnerSubscriptionId": "7d50531-31eb-45f9-91ce-6355250f5501", "partnerCode": "PRTNR", "productCode": "Basic_Addon", "createdDate": "2024-05-04T17:38:10.889", "updatedDate": "2024-05-04T17:38:11.160", "startServiceDate": "2024-05-04T17:38:10.889", "serviceStatus": "PROVISION-COMPLETE" } ] ``` # Status Codes MarketONE uses the following HTTP response codes to indicate the success or failure of an API request. | Code | Status | Description | | ------- | ------ | ------------------- | | **200** | OK | Everything worked as expected. | | **201** | OK | Everything worked as expected. | | **400** | Bad Request | The request was unacceptable, often due to missing a required parameter. Other possibilities include: