I'm developing a Trino solution and I'm looking for the REST API documentation.
I already looked on their official documentation here but there are a lot of endpoints that are not listed on this page (Like /v1/status or /v1/query).
Is there any full documentation of the REST API available?
Thank you,
Yair
Related
To clarify the title I am not thinking of the registering to a webhook through APIM, but to utilize APIM as my documentation for all API related information.
In our setup we wanted to also expose information about possible json objects from our webhooks and saw that this exists in OAS3.1. And azure APIM supports OAS3.1 for import. However importing a test webhook results in an error saying that it isn’t supported
This example was taken from OAS GitHub. So I know I can cheat and creat a dummy endpoint to allow people to view the documentation - but it is not ideal for our use case.
So the questions are:
how to expose the webhook documentation?
am I missing something in Microsoft documentation because I cannot see that it should not be allowed what I wanted to do?
I'm using the DocuSign eSignature API, and am generating client code with the help of the openapi codegen (via these https://github.com/docusign/OpenAPI-Specifications).
Now I have to use the DocuSign Manage API (https://developers.docusign.com/docs/admin-api/), too, but I can't find any Swagger / OpenAPI definition for that?
Is it somewhere hidden, does it not exists, and are there plans to make it available at one point? Are there any other options, SDKs, anything or do I have to make these calls "manually"?
Unfortunately, the Swagger file for the Admin API is not yet available.
That's also why DocuSign doesn't yet have SDKs for the API yet.
I don't have access to any scheduling information on it.
I suggest that you handle any Admin API calls you need to do manually for now.
What language are you creating SDKs for with CodeGen? (Please answer in a comment or by editing your original question.)
In the Standard Twitter API it is possible to filter the tweets so that only the most popular ones are shown using this parameter in the Twitter API request:
result_type: 'popular'
However, in the Premium Twitter API this operator is missing.
Do you know how I can get that same filter using the fullarchive Premium Twitter API endpoint?
I know I could look at every tweet's number of retweets, but I'm looking for a more automatic solution to reduce the number of requests that I have to make.
I'm using it in a Node.Js app, so as there's no up-to-date Twitter module I'm using the direct REST request endpoint.
Realistically, the only thing you can do here is to do some manual checks of your own to establish "popularity" - there is no operator combination that you can pass in to premium search that would give back something similar to what was available in the legacy standard search.
I'm investigating Amazon Pinpoint as an SMS campaign engine which we would integrate via the REST APIs.
Having reviewed the documentation about Monetization events, they are only discussed in the context of iOS/Android SDKs or the JavaScript SDK.
https://docs.aws.amazon.com/mobileanalytics/latest/ug/defining-a-monetization-event-sdk.html
The REST API documentation does not specifically mention Monetization events.
https://docs.aws.amazon.com/pinpoint/latest/apireference/rest-api-events.html#rest-api-events-attributes-eventsrequest-table
Is it possible to use the REST API to create a monetization event? If possible, I'm assuming it is a particular value of EventType which I need to use for a monetisation event but this is not documented anywhere.
Thanks!
Michael
Has anyone tried to fetch all comments across media objects given an access token/user id?
The published API expects a media-id :
https://api.instagram.com/v1/media/{mediaid}/comments?access_token=ACCESS_TOKEN
Thanks for the help.
No bulk comment API for Instagram. I don't think it would be supported as well. - it was there for FB graph API v1.0 and removed in v2.0 after. And now every Instagram API is being migrated to FB graph API: https://developers.facebook.com/docs/instagram-api/reference/user
trend seem to favour that it won't be supported.