API teams 2018 Events
API teams 2018 Events
API Road Show – 03/18/2019
Date/Time: Monday, March 18, 2019 | 9:30am to 1:00pm ET
Location: Kimmel Center, KC 802, 8th fl, 60 Washington Sq. South, New York, NY 10012
9:30 AM API Portal Updates
10:15 AM Update from Mulesoft
11:00 AM API User Forum (Feedback)
11:30 AM Working Lunch
11:45 AM Interactive Working Sessions (Technical)
Presentation deck Link
List of available API’s are available on WordPress A-Z list of API’s. A link to API Portal or third party websites is provided from the A-Z list where the description, technical details and mock examples of these API’s can be found.
API Portal can be accessed using API Portal and based on your access levels you can either see Public & Private API’s or just Public API’s.
Currently most API’s are using Runtime version 3.9 but API’s can be deployed on prior versions up to 3.5 or latest version 4.0
Link to current version of Anypoint studio is available under resources section of this word press site, here is the direct link Developer-Workstation-Setup
Please refer to the above link for basic setup.
API End points are available in exchange section of API portal for each API. It also includes API details like input, output along with examples.
Three steps involved in API access
Functional Process – Fill out the Approval Form Link by selecting the required data elements needed and submit for Approval.
Once approval is obtained or while approval is obtained fill complete the next step
Technical Process – Refer to Technical Process Link for technical registration process.
The technical step of obtaining client_id and secret will be approved only if the Functional Process is approved.
The third and last step once the above two steps are approved is to get token
Token generation process – Follow the steps to get the token Token Generation Process Link, once token is obtained access the API by passing the token.
Access to form is enabled through SSO in service now, starting May 1st week all in NYU should be able to access the form.
The list below are some the estimates for API Intake and access provisioning, the below are pure estimates and could change depending on other priorities of API team
|Type of Request||Expected Time of Availability||Additional comments|
|ARB Approved – API Access Request||2 Weeks||Assuming any concerns Approves have are clarified.|
|ARB Not Approved – API Access Request||3 to 4 weeks||Depends on ARB Approval and all data owners questions get clarified|
|API Intake Form||No Specific time||Based on certain factors like priority of the project, number of requests received for the same API etc|
|Overall API provisioning ( End to End)||6 to 7 weeks||Assuming all above activities are initiated in parallel.|
Please refer to API Best Process Link for best practices around API’s.
Stand alone API’s can be tested using Postman, there are different options in postman, using which API’s can be tested with different data. Please refer to API Testing Link for more details on testing API’s
All API’s source code to be deployed on to mule soft will be stored in Gitlab which is integrated with Jenkins to do a continuous Integration and deployment.
Please refer to the link for API production deployment process. Production Migration Link
Foundational API’s are system level API’s, the usage of which is designed for multiple applications to consume the data as is or use with other Foundational API’s. One to Many integrations.
Integration API’s are API’s which are built as per the business needs of one particular application. These are point to point integrations and in most cases cannot be used for other integrations.
API first is the strategy followed but API’s should be created between two products if they are expected to be reusable and if the 2 products are enterprise level products.
Refer to the data governance process.