You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
but also it wasn't clear at first if there's pagination or not. I guess the way to paginate in a way is to use before and after right? When using before I also had trouble getting the date syntax right. This worked for me ?before=2023-06-28T15:00:00Z but it would be nice to have this in the docs as well.
Edit: An additional thing to make clear can be the pinid field. In the response it is requestId and not pinId. I assumed it is the pin.cid in the response which is the CID of the pin. In the Estuary dashboard it name "Pin ID" whereas in the API response it's requestId.
The text was updated successfully, but these errors were encountered:
While trying to get our all pins, I noticed the parameters for the endpoint
/pinning/pins
is missing in the OpenAPI spec (and SwaggerUI).I figured out by looking at the code
estuary/api/v1/pinning.go
Lines 42 to 49 in 38ab623
but also it wasn't clear at first if there's pagination or not. I guess the way to paginate in a way is to use
before
andafter
right? When usingbefore
I also had trouble getting the date syntax right. This worked for me?before=2023-06-28T15:00:00Z
but it would be nice to have this in the docs as well.Edit: An additional thing to make clear can be the
pinid
field. In the response it isrequestId
and notpinId
. I assumed it is thepin.cid
in the response which is the CID of the pin. In the Estuary dashboard it name "Pin ID" whereas in the API response it'srequestId
.The text was updated successfully, but these errors were encountered: