# US 2024/0394248 A1 · Datasource introspection user interface for graphql api schema and resolver generation

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2024/0394248 A1
- Document ID: US20240394248A1
- Status: Published application
- Kind: A1
- Application number: 18/322,352
- Filed: 2023-05-23
- Published: 2024-11-28
- Earliest claimed: 2023-05-23
- Assignees: Oracle International Corporation
- Applicants: Oracle International Corporation
- Inventors: Naveen Pilli; Gordon Yorke; Andrei Korostelev; Arun Kiran Patro
- Web page: https://patentgrep.com/patent/US20240394248A1

## CPC

- G06F 16/2423: {Interactive query statement specification based on a database schema}
- G06F 16/211: {Schema design and management}
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

A technique is disclosed for creating a GraphQL Application Programing Interface (API) schema by introspecting various different types of backend datasources. The technique includes receiving a selection of a datasource type to create a GraphQL API schema and introspecting the selected datasource type to determine a set of individual elements associated with the selected datasource type. The technique involves outputting the set of individual elements associated with the selected datasource type via a User Interface (UI) screen of a computer system. The technique further includes receiving a selection of one more individual elements associated with the selected datasource type via a UI screen of the computer system. The technique includes generating a GraphQL API schema comprising a set of objects and a set of resolver functions based on the selected elements and presenting the GraphQL API schema via a UI screen associated with the computer system.

## Claims

### Claim 1

A method comprising:
receiving, by a GraphQL Application Programming Interface (API) design system implemented using one or more computing systems, a selection of a datasource type to create a GraphQL Application Programing Interface (API) schema;
introspecting, by the GraphQL Application Programming Interface (API) design system, the selected datasource type to obtain metadata associated with the selected datasource type, wherein the metadata comprises to determine a set of individual elements associated with the selected datasource type;
outputting, by the GraphQL Application Programming Interface (API) design system, the set of individual elements associated with the selected datasource type via a set of one or more User Interface (UI) screens associated with the GraphQL Application Programming Interface (API) design system;
receiving, by the GraphQL Application Programming Interface (API) design system, a selection of one or more individual elements from the set of individual elements associated with the selected datasource type via the set of one or more UI screens;
outputting, by the GraphQL Application Programming Interface (API) design system, via the set of one or more UI screens, a set of object types and a set of object fields associated with the set of object types based on the selected one or more individual elements;
outputting, by the GraphQL Application Programming Interface (API) design system, via the set of one or more UI screens, a GraphQL API schema for the selected datasource type, the GraphQL API schema comprising the set of object types, the set of object fields associated with the set of object types and a set of resolver functions associated with the set of object types; and
providing, by the GraphQL Application Programming Interface (API) design system, the GraphQL schema for the selected datasource type and the set of resolver functions, via the set of one or more UI screens associated with the computer system.

### Claim 2 (depends on 1)

The method of claim 1, wherein the selected datasource type is a relational database.

### Claim 3 (depends on 2)

The method of claim 2, wherein introspecting, by the GraphQL Application Programming Interface (API) design system, the selected datasource type comprises introspecting the relational database to determine a set of individual elements associated with the relational database.

### Claim 4 (depends on 3)

The method of claim 3, wherein the set of individual elements associated with the relational database comprise a set of one or more tables within the relational database, a set of one or more columns associated with the set of one or more tables and a set of one or more operations supported by the set of one or more tables and the set of one or more columns.

### Claim 5 (depends on 1)

The method of claim 1, wherein outputting, by the GraphQL Application Programming Interface (API) design system, the set of individual elements associated with the selected datasource type comprises outputting a set of one or more tables associated with a relational database and a set of one or more columns associated with the set of one or more tables via the set of one or more UI screens, wherein the selected datasource type is the relational database.

### Claim 6 (depends on 1)

The method of claim 1, wherein receiving, by the GraphQL Application Programming Interface (API) design system, a selection of one or more individual elements from the set of individual elements associated with the selected datasource type comprises receiving a selection of one or more tables associated with a relational database, wherein the selected datasource type is the relational database.

### Claim 7 (depends on 6)

The method of claim 6, further comprising receiving, by the GraphQL Application Programming Interface (API) design system, a selection of one or more columns associated with the one or more tables and receiving a selection of one or more operations supported by the one or more tables via the set of one or more UI screens.

### Claim 8 (depends on 1)

The method of claim 1, wherein the selected datasource type is a relational database and wherein outputting, by the GraphQL Application Programming Interface (API) design system, the GraphQL API schema for the selected datasource type comprises outputting the GraphQL API schema for the relational database.

### Claim 9 (depends on 1)

The method of claim 1, wherein the selected datasource type is a Representational State Transfer (REST) Application Programing Interface (API) datasource.

### Claim 10 (depends on 9)

The method of claim 9, wherein introspecting, by the GraphQL Application Programming Interface (API) design system, the selected datasource type comprises introspecting the REST API datasource to determine a set of individual elements associated with the REST API datasource.

### Claim 11 (depends on 10)

The method of claim 10, wherein the set of individual elements associated with the REST API datasource comprise a set of one or more APIs associated with the REST API datasource, one or more query parameters associated with the set of one or more APIs and response information associated with the set of one or more APIs.

### Claim 12 (depends on 1)

The method of claim 1, wherein receiving, by the GraphQL Application Programming Interface (API) design system, the selection of one or more individual elements from the set of individual elements associated with the selected datasource type comprises receiving a selection of one or more APIs associated with a REST API datasource, wherein the selected datasource type is the REST API datasource.

### Claim 13 (depends on 1)

The method of claim 1, further comprising:
receiving, by the GraphQL Application Programming Interface (API) design system, a selection of an object type from the set of object types defined in the GraphQL API schema via the set of one or more UI screens;
receiving, by the GraphQL Application Programming Interface (API) design system, an indication to edit a resolver function associated with the selected object type; and
responsive to receiving the indication, presenting, by the GraphQL Application Programming Interface (API) design system, structural information associated with the selected object type.

### Claim 14 (depends on 13)

The method of claim 13, further comprising:
receiving, by the GraphQL Application Programming Interface (API) design system, a modification to the structural information associated with the selected object type;
based on the modification, editing, by the GraphQL Application Programming Interface (API) design system, the resolver function associated with the selected object type; and
publishing, by the GraphQL Application Programming Interface (API) design system, a modified GraphQL API schema via the set of one or more UI screens.

### Claim 15

A system comprising:
a memory; and
one or more processors configured to perform processing, the processing comprising:
receiving a selection of a datasource type to create a GraphQL Application Programing Interface (API) schema;
introspecting the selected datasource type to obtain metadata associated with the selected datasource type, wherein the metadata comprises a set of individual elements associated with the selected datasource type;
outputting the set of individual elements associated with the selected datasource type via a set of one or more User Interface (UI) screens associated with the system;
receiving a selection of one or more individual elements from the set of individual elements associated with the selected datasource type via the set of one or more UI screens;
outputting a set of object types and a set of object fields associated with the set of object types based on the selected one or more individual elements;
outputting a GraphQL API schema for the selected datasource type, the GraphQL API schema comprising the set of object types, the set of object fields associated with the set of object types and a set of resolver functions associated with the set of object types; and
providing the GraphQL schema for the selected datasource type and the set of resolver functions via the set of one or more UI screens.

### Claim 16 (depends on 15)

The system of claim 15 further comprising:
receiving a selection of an object type from the set of object types defined in the GraphQL API schema via the set of one or more UI screens;
receiving an indication to edit a resolver function associated with the selected object type; and
responsive to receiving the indication, presenting structural information associated with the selected object type.

### Claim 17 (depends on 16)

The system of claim 16 further comprising:
receiving a modification to the structural information associated with the selected object type;
based on the modification, editing the resolver function associated with the selected object type; and
publishing a modified GraphQL API schema via the set of one or more UI screens.

### Claim 18

A non-transitory computer-readable medium storing instructions executable by a computer system that, when executed by one or more processors of the computer system, cause the one or more processors to perform operations comprising:
receiving a selection of a datasource type to create a GraphQL Application Programing Interface (API) schema;
introspecting the selected datasource type to obtain metadata associated with the selected datasource type, wherein the metadata comprises, wherein the metadata comprises a set of individual elements associated with the selected datasource type;
outputting the set of individual elements associated with the selected datasource type via a set of one or more User Interface (UI) screens associated with the system;
receiving a selection of one or more individual elements from the set of individual elements associated with the selected datasource type via the set of one or more UI screens;
outputting, by the GraphQL Application Programming Interface (API) design system, a set of object types and a set of object fields associated with the set of object types based on the selected one or more individual elements;
outputting a GraphQL API schema for the selected datasource type, the GraphQL API schema comprising the set of object types, the set of object fields associated with the set of object types and a set of resolver functions associated with the set of object types; and
providing the GraphQL schema for the selected datasource type and the set of resolver functions via the set of one or more UI screens.

### Claim 19 (depends on 18)

The non-transitory computer-readable medium of claim 18, wherein the selected datasource type is a relational database.

### Claim 20 (depends on 18)

The non-transitory computer-readable medium of claim 18, wherein the selected datasource type is a Representational State Transfer (REST) Application Programing Interface (API) datasource.
