Reseller Identification and Validation API POE
Implementation
1.Introduction :
This document provides guidance for configuring the Reseller Identification and Validation API.
Connectivity: Details on how to establish and maintain connections with the API.
Message Specifications: Definition of the specific message formats and protocols used in communication.
Test Client Programs: Guidance on available testing tools and client programs for development and validation.
By following the guidance within this document, distributors can ensure a smooth and efficient integration with Cisco's Reseller Identification and Validation services.
1.1 Overview
The API Implementation Guide focuses on enabling distributors to seamlessly interact and integrate with Cisco. It covers functionalities that allow for searching, managing reseller mapping information, and downloading lists of global denied and verification-required resellers.
1.2 Audience
The intended audience for this document is Business Analysts, IT Engineers, and Technical Architects who are involved in the integration project. Other stakeholders who wish to understand business and/or technical aspects of integration may also use the document as a reference
1.3 Scope
The scope of this document is limited to Cisco’s Reseller Identification and Validation API. It can be used for searching, managing reseller mapping information.
1.4 Pre-Requisites
• It is assumed that the reader has some familiarity with Cisco’s Distribution Finance platform through either formal or informal training and/or demonstration.
• The credentials to access Reseller Identification and Validation API must have been previously established. Please contact your Partner Solutions representative for assistance if they are yet to be established.
2. Reseller Identification and Validation API End Points
The Reseller Identification and Validation API has five End Point Resources
- searchReseller
- gdvrResellers
- addRseller
- updateReseller
- deleteReseller
- getSourceNames
2.1 Search Reseller
The Search Reseller endpoint allows you to search for an existing distributor to Cisco's 2T partner mapping information. Clients can filter results using various attributes provided in the request body, and the results are returned in a paginated format.This endpoint facilitates the discovery of specific resellers by offering customizable search functionality. By providing different attributes in the request body, users can narrow down the search results to meet their specific criteria. The response is paginated to offer an organized and manageable view, allowing for a minimum of 500 and a maximum of 1000 records per page.
This service returns a response based on the source profile mapped to the CCO ID used to request access to the API. The CCO ID must be mapped to at least one source profile. Once mapped, the service retrieves the master source profile for the CCO ID and provides results for all theaters and source profiles under that master source profile.
Parameters:
theaterCode
: (string, required) An input parameter that is mandatory for this service.- Other parameters: (optional) Additional parameters may be included in the request, as needed.
Refer to the sections "Request Attributes" and "Response Attributes" for more detailed information on request, response attributes, formats and examples.
Pagination:
The response is paginated, and the response header includes links to the previous and next pages for the given input request body. This ensures easy navigation through large sets of data.
Note: Ensure that the CCO ID used for requesting access to the API is mapped to at least one source profile in DCA Application to receive the appropriate response. Please reach out to appropriate theater support mailer to have the source profile mapped to the CCO ID .
disti-emea-dca-support@external.cisco.com , disti-latam-dca-support@external.cisco.com or disti-usa-dca-support@external.cisco.com
2.2 Global Denied And Verification Required Resellers
This endpoint allows distributors to retrieve the Global Denied and Verification Required Resellers List. Clients can filter the results using various attributes provided in the request body, and the results are returned in a paginated format. This facilitates the discovery of specific global denied and verification required resellers by offering customizable search functionality. By providing different attributes in the request body, users can narrow down the search results to meet their specific criteria. The response is paginated, allowing for a minimum of 500 and a maximum of 1000 records per page.
The service returns a response based on the source profile mapped to the CCO ID used to request access to the API. The CCO ID must be mapped to at least one source profile. Once mapped, the service retrieves the master source profile for the CCO ID and provides results for all theaters and source profiles under that master source profile.
Note: Ensure that the CCO ID used for requesting access to the API is mapped to at least one source profile in DCA Application to receive the appropriate response. Please reach out to appropriate theater support mailer to have the source profile mapped to the CCO ID .
disti-emea-dca-support@external.cisco.com , disti-latam-dca-support@external.cisco.com or disti-usa-dca-support@external.cisco.com
2.3 Add Reseller
This endpoint allows distributors to add Disti Validated Reseller Account Numbers and Sold To Names for Cisco's 2T Resellers. Clients can add up to a maximum of 100 records in a single request.Details:
This service returns a response based on the source profile mapped to the CCO ID used to request access to the API. The CCO ID must be mapped to at least one source profile. Once mapped, the service retrieves the master source profile for the CCO ID and provides results for all theaters and source profiles under that master source profile.
Note: Ensure that the CCO ID used for requesting access to the API is mapped to at least one source profile in DCA Application to receive the appropriate response. Please reach out to appropriate theater support mailer to have the source profile mapped to the CCO ID .
disti-emea-dca-support@external.cisco.com , disti-latam-dca-support@external.cisco.com or disti-usa-dca-support@external.cisco.com
2.4 Update Reseller
This endpoint allows distributors to update Disti Validated Reseller Account Numbers and Sold To Names for Cisco's 2T Resellers. Clients can add up to a maximum of 100 records in a single request.Details:
This service returns a response based on the source profile mapped to the CCO ID used to request access to the API. The CCO ID must be mapped to at least one source profile. Once mapped, the service retrieves the master source profile for the CCO ID and provides results for all theaters and source profiles under that master source profile.
Note: Ensure that the CCO ID used for requesting access to the API is mapped to at least one source profile in DCA Application to receive the appropriate response. Please reach out to appropriate theater support mailer to have the source profile mapped to the CCO ID .
disti-emea-dca-support@external.cisco.com , disti-latam-dca-support@external.cisco.com or disti-usa-dca-support@external.cisco.com
2.5 Delete Reseller
This endpoint allows distributors to delete Disti Validated Reseller Account Numbers and Sold To Names for Cisco's 2T Resellers. Clients can add up to a maximum of 100 records in a single request.Details:
This service returns a response based on the source profile mapped to the CCO ID used to request access to the API. The CCO ID must be mapped to at least one source profile. Once mapped, the service retrieves the master source profile for the CCO ID and provides results for all theaters and source profiles under that master source profile.
Note: Ensure that the CCO ID used for requesting access to the API is mapped to at least one source profile in DCA Application to receive the appropriate response. Please reach out to appropriate theater support mailer to have the source profile mapped to the CCO ID .
disti-emea-dca-support@external.cisco.com , disti-latam-dca-support@external.cisco.com or disti-usa-dca-support@external.cisco.com
2.6 Get Source Names
This endpoint facilitates the retrieval of a collection of source names linked to a specified CCO ID, providing distributors with a streamlined mechanism to access the detailed associations necessary for leveraging the API to its fullest extent.
This service returns a response based on the source profile mapped to the CCO ID used to request access to the API. The CCO ID must be mapped to at least one source profile. Once mapped, the service retrieves the master source profile for the CCO ID and fetches
all the Source Names under that master source profile.
3.Technical Specifications
This section contains the technical specifications for the Reseller Identification and Validation API Services.
The Reseller Identification and Validation API is published via Mulesoft API Gateway.
3.1 Communication Protocol
Cisco supports the NextGen web services through Mule API Gateway. The document is sent over an https call.
3.2 Authentication & Authorization
To access and interface with this API, partners/distributors need:
- A valid Cisco user ID (CCO ID)
- Registered application with Cisco’s MuleSoft Anypoint API portal Please refer the section "Access Request Steps" to request Access to this API. Please refer "Mocking Service Section": to try the API
- The CCO ID used to register the application in Cisco’s MuleSoft Anypoint API portal must have access to DSV Application and at least one source profile id is mapped to the CCO ID.3.2.1 Authentication
This API utilizes OAuth 2.0 for secure authentication. Clients must obtain an access token from the authorization server by following the standard OAuth 2.0 authorization code flow. Once obtained, the access token must be included in the Authorization header of each API request, using the Bearer scheme. Failure to provide a valid token will result in a 401 Unauthorized response.
Upon successful authentication, the API verifies authorization using the Bearer Token, which is tied to the CCO ID registered during the application setup. The API checks if the CCO ID has the necessary access permissions for the requested data. If the CCO ID is not mapped to any source profiles, an Unauthorized error is returned. If the CCO ID is mapped to a source profile, the API retrieves all corresponding source profiles across all theaters based on the existing mapping for that CCO ID and returns the relevant data.
3.3 END Points :
POE
Resource | Method | Content Type | EndPoint URL | Description |
---|---|---|---|---|
/searchReseller | POST | application/json | https://apx-poe.cisco.com/dfm/services/api/v1/disti/reseller/searchReseller?page=1&limit=500 | Provides the Search Results for Resller Informaiton |
/gdvrResellers | POST | application/json | https://apx-poe.cisco.com/dfm/services/api/v1/disti/reseller/gdvrResellers?page=1&limit=500 | Provides the Global Denied and Verification Required Reseller List. |
/addReseller | POST | application/json | https://apx-poe.cisco.com/dfm/services/api/v1/disti/reseller/addReseller | Manage Reseller - Add Reseller Details. |
/updateReseller | POST | application/json | https://apx-poe.cisco.com/dfm/services/api/v1/disti/reseller/updateReseller | Manage Reseller - Update Reseller Details. |
/deleteReseller | POST | application/json | https://apx-poe.cisco.com/dfm/services/api/v1/disti/reseller/deleteReseller | Manage Reseller - Delete Reseller Details. |
/getSourceNames | GET | application/json | https://apx-poe.cisco.com/dfm/services/api/v1/disti/reseller/getSourceNames | Source Names - Get Mapped Source Names. |
3.4 Bearer Token
Token URL : https://id.cisco.com/oauth2/default/v1/token
Http Method: POST
x-www-form-urlencoded
- grant_type : client_credentials
- client_id : provide the client Id of registered application
- client_secret : provide the client Secret of registered application