Connector API Certification: What to expect

Connector API certification: main goals

 

The certification process is like a test run of a full cycle of your integration to confirm that your solution can make proper use of the Connector API.

 

Some criteria that is factored into the evaluation include:

 

• whether you are meeting the minimum functionality requirements outlined in Mews' Use cases (where applicable), and
• whether the endpoints are used with the appropriate frequency and relevant filters.

 

 

Steps to apply for the Connector API certification

 

1. Fill in the Certification form to kick off the certification process. The form asks you for more detailed technical and marketing information about the solution that you have built. Make sure to enter your Partner ID (looks like INT12345).
2. Once you've completed the form, Mews sends:
   1. An email containing a unique Access Token for the demo environment to test run your integration.
   2. Instructions to proceed with the certification process.

 

 

Connector API certification: actions required from partners

 

• Run the integration for 48 hours by pairing the Access Token provided in the email with the Demo Client Token you were already using in the Mews Demo.
• The integration should be run as if it is being used at a real property, from set up to the day-to-day activities.

 

 

Connector API certification: actions performed by the Mews Technical Partnerships team

 

After at least 48 hours or once sufficient data is generated against the Mews API, the Mews Technical Partnerships Team reviews the data and provides accurate feedback on:

 

• Whether the API endpoints used correspond to the logic/workflow you have described in the Certification form
• If applicable, whether the implementation flow corresponds to the use cases described in the Connector API documentation
• Whether there were any errors and/or if they were resolved in subsequent API calls
• Whether the endpoints are called at the frequency appropriate for its use
• Formatting of the API request
• Any particular filters used: as these may relate to the entity permissions assigned to you integration client profile on the production environment

 

Note: Make sure you allow sufficient time for running your integration against the Mews Demo Environment. API reviews, feedback, and potential bug fixes to the integration may take longer than expected.

 

 

Passing the Connector API certification

 

Once Mews confirms that all API activities are fine and no outstanding issues remain:

 

• You receive an email to confirm that the certification was successful.

• Mews creates an integration client profile for you in the Mews production environment. For this, you receive a separate email with a unique Client Token for operating the integration on the Production environment.

 

If your integration is intended only for one specific property or chain, Mews adds the integration to said property/chain, and the Access Token(s) specific to these properties are automatically sent to you.

 

If your integration is intended to be listed publicly in Mews Marketplace, Mews adds the integration to the Pilot property mentioned in the Certification form where the integration undergoes a Pilot stage of two weeks.

Once you have successfully run the integration at the pilot property for two weeks, respond to the Certification instructions email for a final review of your integration.

 

After a successful Pilot period, Mews lists your solution on the Mews website and in the Mews Marketplace.