API Strategy
Sign in to Google to save your progress. Learn more
Does you API have a name?
If yes, provide the name bellow
Is your API Public or Private? *
Do you use APIs to expose internal micro services?
Clear selection
If your API is public, could you provide the link?
For how long (months) did you spend thinking about/developing the API prior to its launch (private/public)? *
For how long (months) now has the API been available (private/public)? *
Are you pleased with the API adoption/usage? *
Does your API come with a pricing model?
Clear selection
If No, are you considering it?
Clear selection
If your API is private, are you considering to open some parts of it?
Clear selection
Where do you document your API? *
Required
Do you use any of the API Standards to model your API (Swagger, RAML, etc.)? *
Do you model your API responses beforehand, or you just serve whatever the code creates? *
If you design in advance, which standards do you prefer (HAL, Hydra, JSON-Collection) ?
In your app you use:
Which languages do you favour while creating your API? *
Required
Is your API built in the same language as your main app?
Clear selection
Do you consider your API as a different system or export a functionality on top of the existing stack? *
Are you planning to continue this API? *
Are you planning to release new APIs? *
Useful Infographic - Where is your company  currently stated?
Choose your country
Submit
Clear form
Never submit passwords through Google Forms.
This content is neither created nor endorsed by Google. - Terms of Service - Privacy Policy

Does this form look suspicious? Report

Google Forms