FREQ=DAILY;BYHOUR=4,5,6,7,8,9,10,11,12,13,14,15,16,17,18;BYMINUTE=0,10,20,30,40,50;BYSECOND=0;
FREQ=MONTHLY;BYMONTHDAY=1,10,15;BYHOUR=5,10,15,20;BYMINUTE=15;
FREQ=YEARLY;INTERVAL=3;BYMONTH=3;BYDAY=2,22;
<Every Three years on May 2nd and 22nd >
BYYEARDAY
BYWEEKNO
BYMONTH
BYSETPOS
WKST
FREQ= “SECONDLY” / “MINUTELY” / “HOURLY” / “DAILY”/ “WEEKLY” / “MONTHLY” / “YEARLY”
hour = 1DIGIT / 2DIGIT ;0 to 23
weekday = “SU” / “MO” / “TU” / “WE” / “TH” / “FR” / “SA”
Mulesoft support API First development method by using API Designer and Exchange server. This feature help the organizations are define and publish standard and reusable API's.
As part of API first development strategy, we can define API's , get it reviewed by different LOB, stake holders and publish the final API for discovery and consumption.
This will help the organization to streamline the development process by reusing existing API's and speedup the delivery process.
Mulesoft provides API Designer to design and develop API definitions. API Designer will use RAML specifications to define an API.
API designer will provide mock service capabilities to test the API definition. We can use the Public endpoints to test the API definitions from Postman or Advanced Rest Client.
We can publish the API definition to Mulesoft Exchange server and this will create an API portal . API portal provides a console for documentation, mock service and sharing capabilities.
We can share the API definition with users within our organizations and with public users (Client applications) .
User can discover API definition , verify using mock service and consume the API for processing requests.
Follow below steps to access, design and develop API's using Mulesoft.
/submitIntegration :get:post:/{IntegrationRunId}:
