Allow Interactions to have separate endpoints
It would be nice instead of sending all interactions to single Endpoint, you could route it. Either allow sending to {base_url}/{command} as toggle option or allow completely separate endpoints defined in JSON for each command.
Most Serverless setups like Lambdas/Functions let you have separate endpoints to keep code base nice and tidy.
-
Endpoints usually have brief descriptions similar to the overall resource so it might make sense to give each endpoint more visual weight in your documentation. Redoc.ly: Transform your API definition into interactive documentation, fast But if they're substantially unique (with different responses, parameters, and error.
The endpoint is arguably the most important aspect of API documentation because this is what developers will implement to make their requests.
0 -
MyFedLoan is like your personal guide for managing federal student loans. They help you choose repayment plans, handle payments, and keep your loan account on track. Think of them as your go-to support team, making it easier to navigate the world of student loan repayment with confidence and clarity.
0 -
Instead of sending all interactions to a single endpoint, it would be beneficial to enable routing. Consider allowing a toggle option for sending to `{base_url}/{command}` or defining separate endpoints in a JSON configuration for each command. This approach aligns with serverless setups like AWS Lambda, which typically use separate endpoints to maintain a clean and organized codebase.
0
Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.
Kommentare
3 Kommentare