Index

Search in book...
Toggle Font Controls
Create new playlist

Name your new playlist

Playlist description (optional)
Sign In

Email address

Password

Forgot Password?

or

Continue with Facebook

Continue with Google
Sign Up

Full Name

Email address

Confirm Email Address

Password

or

Continue with Facebook

Continue with Google

Previous Chapter

Chapter 9. Empowering your developers

List of Figures

Index

[SYMBOL][A][B][C][D][E][F][G][H][I][J][K][L][M][N][O][P][Q][R][S][T][U][V][W][Y]

SYMBOL

? character, 2^nd [ ] (square brackets), 2^nd, 3^rd { } (curly braces), 2^nd, 3^rd, 4^th */* characters & character = character $ character $.get function 200 HTTP status response message, 2^nd, 3^rd, 4^th 201 Created message, 2^nd 202 Item Marked for Deletion message 203 Object marked for deletion message 204 response message, 2^nd 301 Resource moved permanently message 302 Resource moved temporarily message 400 Malformed request message 401 Authentication failure message 403 Authorization failure message 404 Page not found message 405 Method not allowed message 409 HTTP response message 500 Server Error message

A

abstract functions Accept header acceptance criteria acceptance tests, mock server API Accept-Language header Access-Control-Allow Headers header Access-Control-Allow-Methods header Access-Control-Allow-Origin header activity stream, 2^nd Add API form Add New API option addressability, HTTP agile scrum board agile sprint, 2^nd agile/test-first development Akamai, 2^nd Akamai Billing Usage report all mode Amazon ampersand character antipatterns Anypoint portal, MuleSoft API Administration board API authorization API business value business goals customer/partner retention market dominance monetization usage metrics customer/partner retention market dominance monetization poor metrics usage use cases customer/partner retention mobile monetization usage API calls, mapping API Commons, 2^nd API Console interface API consoles API definition API design principles avoiding strict REST philosophy creating comprehensive data transfer scheme creating query language creating separate batching system expanding and including related resources avoiding surprises for users copying successful APIs focusing on developer experience communication and consistency documentation focusing on use cases application integration use cases mobile use case API endpoints, 2^nd API First case studies API as main product mobile First refactoring for API First strategic direction code consistency example of functional equality increased productivity internal and external access overview reasons for using setup troubleshooting API inspection, tools for Apiary, 2^nd api-docs endpoint Apigee application functions arrays authentication, 2^nd, 3^rd, 4^th authorization autocompletion auto-generated documentation

B

back-end systems, 2^nd, 3^rd, 4^th basepath baseUri batched-up calls batching system BDD (behavior-driven development) BeSpoke, 2^nd best practices, web services methods and idempotency nouns vs. verbs using right status codes blockers blogs Blueprint schema model body content, 2^nd, 3^rd boot2docker building blocks for developers reference applications sample code authentication libraries reference implementations and code samples tools and techniques API consoles command-line utilities business goals customer/partner retention market dominance monetization usage business values, 2^nd, 3^rd metrics customer/partner retention market dominance monetization poor metrics usage use cases customer/partner retention mobile monetization usage

C

cache purge case studies, API First API as main product mobile First refactoring for API First strategic direction Charles proxy application checkpoints, 2^nd Chrome Network tab Chrome, setting up for HTTP inspection client code generators client types code consistency code debugging code refactoring code-first development CodeGen engine command line, Heroku command-line call command-line utilities communication failures of LinkedIn Netflix Twitter strong and consistent consumes parameter content-delivery services Content-Length header Content-Type header Context.io, monetization use case CRUD (create, read, update, and delete), 2^nd, 3^rd, 4^th, 5^th cryptographic signing algorithms curl command, 2^nd, 3^rd, 4^th curly braces, 2^nd, 3^rd, 4^th customer/partner retention as business goal metrics for use cases automation/integration unique content

D

DDD (design-driven development. See DDD. DDD (design-driven development), 2^nd development planning development sprints kanban planning retrospective standups development strategies agile/test-first development behavior-driven development code-first development design-driven development waterfall development project management functional specification importance of schema model road-testing debugging, 2^nd decoupled code defensive coding DELETE method OpenAPI schema model RAML schema model delete_photo resource design layer design principles avoiding strict REST philosophy creating comprehensive data transfer scheme creating query language creating separate batching system expanding and including related resources avoiding surprises for users copying successful APIs focusing on developer experience communication and consistency documentation focusing on use cases application integration use cases mobile use case design-driven development designing API developer empowerment building blocks reference applications sample code tools and techniques communication failures of strong and consistent documentation reference documentation tutorials workflows overview support interactive noninteractive developer experience communication and consistency documentation pillars of. See also developer empowerment. developer keys Developer Tools section, Chrome developers marketing to supporting development sprints kanban planning retrospective standups development strategies agile/test-first development behavior-driven development code-first development design-driven development waterfall development diagnostic-tools script dig utility DigitalOcean <div> tag Docker container Docker, installing system via documentation, 2^nd, 3^rd reference documentation minimum requirements for providing opportunities to explore API tutorials workflows documenting workflows dollar sign character

E

EdgeGrid edges email alias email interaction endpoints, 2^nd, 3^rd, 4^th, 5^th equals sign character error handling, 2^nd estimates, 2^nd Etsy, 2^nd, 3^rd Events API expandable API external access, API First, 2^nd

F

Facebook, 2^nd, 3^rd FedEx, customer/partner retention Fiddler, 2^nd filtering data Fitbit, 2^nd, 3^rd Flickr API, 2^nd Flipboard formatting data forums fragile applications free trial calls Freebase FTD functional equality, API First functional specification

G

generators GET method OpenAPI schema model, 2^nd RAML schema model adding mock data response format Getting Started tutorial Git, installing system via GitHub, 2^nd, 3^rd Google Calendar graph web API, Facebook

H

hackathons hashes headers, 2^nd help desk application Heroku, 2^nd high-revenue customers Hootsuite host entry, 2^nd hosting platforms hosting providers, mock server API HTTP, 2^nd addressability body headers interactions parameters protocols, 2^nd requests responses sniffers, 2^nd, 3^rd status codes verbs HTTPie HTTPScoop, 2^nd, 3^rd

I

-i flag id attribute idempotency, 2^nd index.html file industry standards inefficient workflows info block initial calls Instagram API integrating systems interaction points interactive support internal access, API First Irresistible API

J

JSON (JavaScript Object Notation), 2^nd

K

kanban, 2^nd key-value pairs

L

LinkedIn, 2^nd, 3^rd, 4^th, 5^th links lists Location information

M

management functional specification importance of schema model mapping API calls mapping cases mapping terms Markdown, 2^nd, 3^rd, 4^th, 5^th market dominance as business goal metrics for marketing to developers mashups measuring calls methods HTTP, 2^nd idempotency and overview metrics choosing for customer/partner retention for market dominance for monetization for usage poor MGL (Metabase Query Language) minimum viable product. See MVP. mobile devices, 2^nd mobile First mobile interfaces mobile use case Mock API mock server, 2^nd modeling languages, 2^nd, 3^rd, 4^th modeling schemas models defined determining needs for resulting API resource methods top-level resources OpenAPI subresource methods tools and resources for top-level resource methods RAML adding methods adding mock data adding resources DELETE method GET response format PUT response format query parameters searching support tools for modular code monetization as business goal metrics for use cases Context.io SendGrid Twilio MuleSoft, 2^nd, 3^rd, 4^th multiple representations, reducing MusicBrainz MVP (minimum viable product)

N

native mobile application Netflix API application integration failures of communication market dominance, as business goal Network button, Chrome Network tab, Chrome, 2^nd Nginx Node.js, 2^nd nodes nonperformant applications nonsecure APIs nouns, vs. verbs

O

OAuth, 2^nd objects OpenAPI schema model subresource methods tools and resources for top-level resource methods GET POST organically grown APIs

P

parameters, 2^nd, 3^rd, 4^th partnerships, 2^nd PATCH method paths peers People API photo_id photosets.delete method PizzaToppings API, 2^nd platform providers platforms. See web APIs. plug-ins portals POST method OpenAPI schema model RAML schema model Preserve Log option, Chrome Procfile produces parameter productivity, increasing project management functional specification importance of schema model protocols HTTP, 2^nd, 3^rd, 4^th transaction web API PUT method OpenAPI schema model RAML schema model

Q

query string query support queryParameters section question mark character, 2^nd quick links

R

Rackspace RAML (RESTful API Modeling Language) schema model adding methods adding mock data adding resources DELETE method GET response format PUT response format query parameters searching support tools for read operation, 2^nd, 3^rd, 4^th README file, 2^nd redirect status codes reducing multiple representations refactoring code refactoring for API First reference documentation minimum requirements for providing opportunities to explore API reference implementations regression testing representations, reducing multiple request headers Request/Response tab resources object resources, RAML schema model response headers Response tab, Chrome REST (Representational State Transfer) avoiding strict REST philosophy creating comprehensive data transfer scheme creating query language creating separate batching system expanding and including related resources overview web services for restricting access retrospective road-testing, creating mock server API acceptance tests advanced hosting providers use cases Root of the Document section, RAML Runkeeper, 2^nd

S

safe mode sales-speak sample code schema models, 2^nd defined determining needs for resulting API resource methods top-level resources OpenAPI subresource methods tools and resources for top-level resource methods RAML adding methods adding mock data adding resources DELETE method GET response format PUT response format query parameters searching support tools for scrum SDKs (software development kits), 2^nd secure transactions SendGrid, monetization use case server error codes sharing icons and widgets signing library single-call interaction SmartBear SMS API industry SOAP (Simple Object Access Protocol), 2^nd social platforms software tests sorting data sprints kanban planning retrospective standups square brackets, 2^nd, 3^rd standard documentation Standish Group standups static data status codes, 2^nd, 3^rd, 4^th, 5^th stories strategies agile/test-first development behavior-driven development code-first development design-driven development waterfall development streamlining strict REST system style attribute subresources OpenAPI schema model RAML schema model success status codes support for developers, 2^nd building blocks reference applications sample code tools and techniques communication advantages to strong and consistent failures of strong documentation reference documentation tutorials workflows interactive noninteractive overview Swagger. See OpenAPI schema model. system integrations

T

tagging data telephony applications term mapping testing phase testing, mock server API acceptance tests advanced hosting providers use cases third-party applications third-party developers, 2^nd title field toppings API transaction protocol tricky mapping troubleshooting web API interactions defensive coding error handling tools for API inspection TTD (test-driven development) Tumblr, usage use case tutorials, 2^nd, 3^rd Twilio, 2^nd, 3^rd, 4^th Twitter API application integration failures of communication usage use case

U

unit tests unsupported workflows URI (uniform resource indicator) URL (uniform resource locator), 2^nd URL paths usage as business goal metrics for use cases Facebook Tumblr Twitter use cases, 2^nd application integration Netflix example Twitter example customer/partner retention automation/integration unique content defining mobile, 2^nd mock server API monetization Context.io SendGrid Twilio usage Facebook Tumblr Twitter user error codes user story User-Agent header

V

–v flag validating functionality Varnish VBox verbose output verbs HTTP vs. nouns version field versioning Video API VirtualBox

W

waterfall development web API business value business goals customer/partner retention market dominance monetization usage metrics customer/partner retention market dominance monetization poor metrics usage use cases customer/partner retention mobile monetization usage web API design principles avoiding strict REST philosophy creating comprehensive data transfer scheme creating query language creating separate batching system expanding and including related resources avoiding surprises for users copying successful APIs focusing on developer experience communication and consistency documentation focusing on use cases application integration use cases mobile use case web APIs common pitfalls of bad design lack of vision prioritizing developer experience creation process choosing metrics defining use cases design design-driven development determining business value industry standards supporting developers deciding whether needed developer experience using marketing to developers versioning installling integrating into web content APIs interaction between client and JSON and REST APIs, choosing using browser curl command HTTP sniffers web browser, Chrome web services best practices methods and idempotency nouns vs. verbs using right status codes HTTP fundamentals addressability body headers parameters status codes verbs HTTP traffic REST web services troubleshooting web API interactions defensive coding error handling tools for API inspection webapp subdirectory webhooks website application weight model, Withings widgets, 2^nd Wikipedia Wireshark workflows, 2^nd

Y

YAML (Yet Another Markup Language), 2^nd YouTube

..................Content has been hidden....................

You can't read the all page of ebook, please click here login for view all page.