# US 11,909,640 B2 · Creating endpoints > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 11,909,640 B2 - Document ID: US11909640B2 - Status: Granted - Kind: B2 - Application number: 17/447,297 - Filed: 2021-09-10 - Published: 2021-12-30 - Granted: 2024-02-20 - Earliest claimed: 2018-07-24 - Assignees: Capital One Services, LLC - Applicants: Capital One Services, LLC - Inventors: Saurabh Gupte - Web page: https://patentgrep.com/patent/US11909640B2 ## CPC - H04L 45/72: {Routing based on the source address} - G06F 9/44505: {Configuring for program initiating, e.g. using registry, configuration files} - H04L 67/02: based on web technology, e.g. hypertext transfer protocol [HTTP] - H04L 67/10: in which an application is distributed across nodes in the network (software deployment G06F8/60; multiprogramming arrangements G06F9/46) - H04L 67/34: {involving the movement of software or configuration parameters (network booting or remote initial program loading [RIPL] G06F9/4416)} - H04W 4/70: Services for machine-to-machine communication [M2M] or machine type communication [MTC] - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) - H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72) ## Abstract A device receives a configuration file that includes an object concerning a Hypertext Transfer Protocol (HTTP) route. The object includes a parameter, related to the HTTP route, that includes one or more elements related to the HTTP route, and includes an attribute related to an HTTP action. The device parses the configuration file to recognize the object, and parses the object to recognize the parameter. The device creates the HTTP route based on the parameter. The HTTP route includes information concerning the one or more elements related to the HTTP route and the attribute related to the HTTP action, and sends the HTTP route to a server, causing the server to perform an operation based on the HTTP route. ## Claims ### Claim 1 A method, comprising: receiving, by a device, a configuration file; identifying, by the device, one or more parameters relating to one or more objects of the configuration file; identifying, by the device, one or more path elements relating to a parameter of the one or more parameters; and constructing, by the device and based on the one or more path elements, a Hypertext Transfer Protocol (HTTP) path for a HTTP route. ### Claim 2 (depends on 1) The method of claim 1, further comprising: executing the HTTP route to create an endpoint of the HTTP route providing a functionality for an application programming interface. ### Claim 3 (depends on 2) The method of claim 2, wherein the HTTP path represents an address of a location of an application programming interface resource associated with the endpoint. ### Claim 4 (depends on 1) The method of claim 1, wherein the configuration file is created by a user. ### Claim 5 (depends on 1) The method of claim 1, further comprising: adding, based on creating the HTTP path, at least one of an exception handler or an exception handler routine to the HTTP route. ### Claim 6 (depends on 5) The method of claim 5, wherein the at least one of the exception handler or the exception handler routine includes a call to a function upon an error occurring when the device executes the HTTP route to attempt to establish an endpoint of the HTTP route. ### Claim 7 (depends on 5) The method of claim 5, wherein the at least one of the exception handler or the exception handler routine includes a call to a function when the device executes the HTTP route and successfully establishes an endpoint of the HTTP route. ### Claim 8 A device, comprising: one or more memories; and one or more processors, coupled to the one or more memories, configured to: receive a configuration file; identify one or more parameters relating to one or more objects of the configuration file; identify one or more path elements relating to a parameter of the one or more parameters; and constructing, based on the one or more path elements, a Hypertext Transfer Protocol (HTTP) path for a HTTP route. ### Claim 9 (depends on 8) The device of claim 8, wherein the one or more processors are further configured to: assign a unique identifier to the HTTP route to distinguish the HTTP route from another HTTP route. ### Claim 10 (depends on 8) The device of claim 8, wherein the one or more processors, to identify the one or more parameters, are configured to: identify a plurality of parameters, including the one or more parameters, relating to the one or more objects of the configuration file; and identify a first parameter of the plurality of parameters, wherein the one or more path elements relate to the first parameter. ### Claim 11 (depends on 8) The device of claim 8, wherein the HTTP route is unique to the one or more objects. ### Claim 12 (depends on 8) The device of claim 8, wherein the one or more processors are further configured to: add, based on creating the HTTP path, core logic, required to complete the HTTP route, to the HTTP route. ### Claim 13 (depends on 8) The device of claim 8, wherein the one or more processors are further configured to: create a route file comprising the HTTP path; and send the route file to another device to cause the other device to execute the HTTP path. ### Claim 14 A non-transitory computer-readable medium storing a set of instructions, the set of instructions comprising: one or more instructions that, when executed by one or more processors of a device, cause the device to: receive a configuration file; identify one or more parameters relating to one or more objects of the configuration file; identify one or more path elements relating to a parameter of the one or more parameters; and construct, based on the one or more path elements, a Hypertext Transfer Protocol (HTTP) path for a HTTP route. ### Claim 15 (depends on 14) The non-transitory computer-readable medium of claim 14, wherein the HTTP route comprises an endpoint providing a functionality for an application programming interface. ### Claim 16 (depends on 15) The non-transitory computer-readable medium of claim 15, wherein the HTTP path represents an address of a location of an application programming interface resource associated with the endpoint. ### Claim 17 (depends on 14) The non-transitory computer-readable medium of claim 14, wherein the one or more instructions that, when executed by the one or more processors of the device, cause the device to: add at least one of an exception handler or an exception handler routine to the HTTP route. ### Claim 18 (depends on 14) The non-transitory computer-readable medium of claim 14, wherein the one or more instructions, that cause the device to identify the one or more parameters, cause the device to: identify a plurality of parameters, including the one or more parameters, relating to the one or more objects of the configuration file; and identify a first parameter of the plurality of parameters, wherein the one or more path elements relate to the first parameter. ### Claim 19 (depends on 14) The non-transitory computer-readable medium of claim 14, wherein the one or more instructions further cause the device to: add, based on creating the HTTP path, core logic, required to complete the HTTP route, to the HTTP route. ### Claim 20 (depends on 14) The non-transitory computer-readable medium of claim 14, wherein the one or more instructions further cause the device to: create a route file comprising the HTTP path; and send the route file to another device to cause the other device to execute the HTTP path.