[Music] in this video we'll provide a quick overview to building a custom graphql API on the platform deeper details and a demonstration are provided after this overview in the next few videos in the previous video we looked at the builtin Glide record query API which allows us to access any table so The Logical question is why do we need customer apis if we already have the table API the answer is that your data may need to come from multiple tables or be calculated and constructed dynamically a custom graphql API gives you the flexibility to control the inputs the processing and the outputs with Precision the major components of a graphql API are the API record which contains information about the schema authentication and authorization one or more resolvers and resolver mappings we'll be covering all of these in more detail in the next few videos for now we'll take a quick look at an example to do that we'll navigate to All System web services graphql graphql apis let's open the decision table record we can see some fields that are used to identify this API against incoming queries we also see the schema that defines what the client can request think of this as a dictionary of sorts that governs what's available and how to request it it's also used to generate the docs in the graphql Explorer in the security section we can see this API requires authentication and does not require any ACL authorization the related lists at the bottom include scripted resolvers these are bits of serers side JavaScript used to run specific actions such as retrieving or updating records the related list of graphql type resolvers are typically used for error handling and the resolver mappings connect the schema to the resolvers for example we may have a resolver to get a user record which can be used multiple times to get just a user or the details of the assigned to and manager fields of a different type within the schema let's move on to the next video to take a closer look at the schema