# US 2025/0094257 A1 · Zero code metadata-driven dynamic api

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

- Number: US 2025/0094257 A1
- Document ID: US20250094257A1
- Status: Published application
- Kind: A1
- Application number: 18/815,469
- Filed: 2024-08-26
- Published: 2025-03-20
- Earliest claimed: 2022-03-11
- Assignees: ADP, Inc.
- Applicants: ADP, Inc.
- Inventors: Vijayanand Veeraraghavan; Mogana Rangan Dhathreeswaran
- Web page: https://patentgrep.com/patent/US20250094257A1

## CPC

- G06F 9/547: {Remote procedure calls [RPC]; Web services}
- G06F 16/211: {Schema design and management}
- G06F 16/258: {Data format conversion from or to a database}
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

A method, apparatus, system, and computer program code for accessing data using a dynamic API. A computer system receives, from a requesting service, a request to access data contained in one or more data sets organized into a set of domains. The request is received according to a target schema of the requesting service. The computer system identifies an endpoint configuration for a domain that provides access to the data that was requested. The endpoint configuration is generated from an API description describing the target schema that is published by the domain. The computer system decorates the endpoint configuration with additional information identified from metadata documents corresponding to the data set. The A computer system translates the request into a common schema, and retrieving the data from the domain according to the common schema.

## Claims

### Claim 1

A method for accessing data using a dynamic API, the method comprising:
receiving, by a computer system, from a requesting service, a request to access data contained in one or more data sets organized into a set of domains, wherein the request is received according to a target schema of the requesting service;
identifying, by the computer system, an endpoint configuration for a domain that provides access to the data that was requested, wherein the endpoint configuration is generated from an API description describing the target schema that is published by the domain;
decorating, by the computer system, the endpoint configuration with additional information identified from metadata documents corresponding to the data set;
translating, by the computer system, the request into a common schema; and
retrieving, by the computer system, the data from the domain according to the common schema.

### Claim 2 (depends on 1)

The method of claim 1, further comprising:
in response to retrieving the data, translating the data from the common schema to the target schema; and
sending a response to the requesting service, wherein the response includes the data that was translated into the target schema.

### Claim 3 (depends on 1)

The method of claim 1, wherein identifying the endpoint configuration further comprises:
identifying a header in the request; and
matching the header to the endpoint configuration according to a reduce function that matches the header to an OpenAPI document.

### Claim 4 (depends on 1)

The method of claim 1, wherein decorating the endpoint configuration further comprises:
identifying an object map for the domain, where in the object map correlates data between the target schema and the common schema;
identifying a query set for the domain; and
generating a SQL request based on the endpoint configuration, the object map, and the query set.

### Claim 5 (depends on 4)

The method of claim 4, where in retrieving the data further comprises:
forwarding the SQL request to a data API; and
retrieving the data from the data API according to the SQL request.

### Claim 6 (depends on 1)

The method of claim 1, further comprising:
generating a controller instance for the domain, including:
identifying the API description published by the domain describing the target schema; and
generating the controller instance from a controller template and the API description.

### Claim 7 (depends on 6)

The method of claim 6, where in the API description is an OpenAPI document that specifies the data sets that are available in the domain and RESTful operations that can be called on the data sets.

### Claim 8

A computer system comprising:
a hardware processor; and
a dynamic API controller in the computer system for accessing data, wherein the dynamic API controller executes program code to perform a method of:
receiving, from a requesting service, a request to access data contained in one or more data sets organized into a set of domains, wherein the request is received according to a target schema of the requesting service;
identifying an endpoint configuration for a domain that provides access to the data that was requested, wherein the endpoint configuration is generated from an API description describing the target schema that is published by the domain;
decorating the endpoint configuration with additional information identified from metadata documents corresponding to the data set;
translating the request into a common schema; and
retrieving the data from the domain according to the common schema.

### Claim 9 (depends on 8)

The computer system of claim 8, wherein the dynamic API controller further executes program code to perform the method further comprising:
in response to retrieving the data, translating the data from the common schema to the target schema; and
sending a response to the requesting service, wherein the response includes the data that was translated into the target schema.

### Claim 10 (depends on 8)

The computer system of claim 8, wherein identifying the endpoint configuration further comprises:
identifying a header in the request; and
matching the header to the endpoint configuration according to a reduce function that matches the header to an OpenAPI document.

### Claim 11 (depends on 8)

The computer system of claim 8, wherein decorating the endpoint configuration further comprises:
identifying an object map for the domain, where in the object map correlates data between the target schema and the common schema;
identifying a query set for the domain; and
generating a SQL request based on the endpoint configuration, the object map, and the query set.

### Claim 12 (depends on 11)

The computer system of claim 11, where in retrieving the data further comprises:
forwarding the SQL request to a data API; and
retrieving the data from the data API according to the SQL request.

### Claim 13 (depends on 8)

The computer system of claim 8, wherein the dynamic API controller further executes program code to perform the method further comprising:
generating a controller instance for the domain, including:
identifying the API description published by the domain describing the target schema; and
generating the controller instance from a controller template and the API description.

### Claim 14 (depends on 8)

The computer system of claim 8, wherein the API description is an OpenAPI document that specifies the data sets that are available in the domain and RESTful operations that can be called on the data sets.

### Claim 15

A computer program product comprising:
a computer readable storage media; and
program code, stored on the computer readable storage media, for accessing data using a dynamic API, that when executed, instruct a computer system to perform a method of:
receiving, from a requesting service, a request to access data contained in one or more data sets organized into a set of domains, wherein the request is received according to a target schema of the requesting service;
identifying an endpoint configuration for a domain that provides access to the data that was requested, wherein the endpoint configuration is generated from an API description describing the target schema that is published by the domain;
decorating the endpoint configuration with additional information identified from metadata documents corresponding to the data set;
translating the request into a common schema; and
retrieving the data from the domain according to the common schema.

### Claim 16 (depends on 15)

The computer program product of claim 15, further comprising:
in response to retrieving the data, translating the data from the common schema to the target schema; and
sending a response to the requesting service, wherein the response includes the data that was translated into the target schema.

### Claim 17 (depends on 15)

The computer program product of claim 15, wherein identifying the endpoint configuration further comprises:
identifying a header in the request; and
matching the header to the endpoint configuration according to a reduce function that matches the header to an OpenAPI document.

### Claim 18 (depends on 15)

The computer program product of claim 15, wherein decorating the endpoint configuration further comprises:
identifying an object map for the domain, where in the object map correlates data between the target schema and the common schema;
identifying a query set for the domain; and
generating a SQL request based on the endpoint configuration, the object map, and the query set.

### Claim 19 (depends on 18)

The computer program product of claim 18, wherein retrieving the data further comprises:
forwarding the SQL request to a data API; and
retrieving the data from the data API according to the SQL request.

### Claim 20 (depends on 15)

The computer program product of claim 15, further comprising:
generating a controller instance for the domain, including:
identifying the API description published by the domain describing the target schema; and
generating the controller instance from a controller template and the API description.

### Claim 21

(canceled)
