How to provide API JSON schema per endpoint? - json

I have a Spring Boot application which serves REST API to the users. Now I would like to provide a JSON schema for every endpoint separately.
Example:
I have an endpoint /companies which allows searching in companies by name, size and country. I would like to have an endpoint /companies/schema which returns me an automatically generated JSON schema for the /companies endpoint.
I have an endpoint /employees which allows searching in employees by firstName, lastName and age. I would like to have an endpoint /employees/schema which returns me an automatically generated JSON schema for the /employees endpoint.
and so on
I have Swagger in the application, but AFAIK it can generate JSON schema for all endpoints at one page. I didn't find any option to generate it per each endpoint separately.
Any ideas about how to achieve that in the Spring Boot application?

Related

Splunk - splunk rest api returns multiple json records. can we force it to send it as a list

I am trying to use splunk rest api to call the logs to do some dashboarding in our external application.
There will be a java middle ware that will call these api and response will be parsed by the UI. But when i call the splunk rest api it returns multiple Json records but not as a list. Just separate json records , It will be troublesome to parse it as its not a list . How do we make sure the response from splunk rest api is just 1 valid Json that can be parsed?
I am attaching the image for postman call for understanding

POST json data (stored as json files in ADLS) to REST endpoint in Azure Data factory

I have a requirement to POST json data (stored as json files in ADLS) to REST API endpoint. I have to use Azure Data factory for this. I have gone through Microsoft documentation but unable to get a clear idea on it is implementation.
As per my understanding ADF Data Copy activity doesn't support REST API as output/sink service.
Reaching out if anyone could help me with any documentation or reference material that could guide me to implement this. Thanks!
I have repro’d with sample API and was able to post the JSON data from blob storage to the REST endpoint using data flow activity in azure data factory.
Source dataset:
Connect source to json dataset.
Connect sink to rest endpoint.

Extracting data from REST API (JSON) in ADF to Azure Data Lake

I have ADF (Azure Data Factory) calling two REST API's in JSON.
Customer IDs
Customer Data. - Customer ID.
How to extract the Customer data (JSON2) based on Customer ID (JSON1), and store them in Parque file format in Datalake?
You can create a Web activity to send your first request to get Customer IDs. Then you can create a copy data activity which source is REST and sink is your Parque file. Finally you can put Web activity's output into REST's body to send the second request.

How to post/redirect data to another api in aws gateway.I want to GET data also in the same aws api gateway

My question is:
I want to GET data from one api and after filtering the data, I want to POST the data to another API in the same api gateway.
The data is in JSON format and after receiving the data, I filter the data and forward to another api.
I can filter the data, but redirecting the result data to another api, I am struggling with.
How can I do that in aws gateway?
You should use HTTP integration type selecting the POST http method.

Receiving a JSON response from the BOX Api when requesting a ticket

I am trying to request a "ticket" from the Box API in order to authenticate a user
. Apparently it will only send back an XML response. I am sure it has something to do with the fact that BOX is still using the 1.0 API for this user authentication process. Is there a way to receive a JSON response for the 1.0 API or use the 2.0 API for this process?
https://www.box.com/api/1.0/rest?action=get_ticket&api_key={api key}
returns XML response.
https://www.box.com/api/2.0/rest?action=get_ticket&api_key={api key}
returns an error in JSON format.
This endpoint currently does not return JSON. We are moving our authentication system to OAuth2, which will return both JSON and XML as the rest of the V2 API does.