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
The curl example in Step 5 Get an access token for the Infisical API points to the hosted Infisical API (https://app.infisical.com/api/v1...), while Step 6 Fetch back secret points to a localhost URL, presumably for a self-hosted solution: http://localhost:8080/api/v3....
I would suggest keeping them consistent one way or the other (both pointing to the hosted API URL or both pointing to the self-hosted API URL). I assume the primary consumer reading these docs is trying out the hosted version, so it probably makes sense to use that URL, maybe with a callout underneath about swapping out the base API URL if you're running it locally or self-hosting.
One other point of feedback is a note about the workspaceId parameter that the /api/v3/secrets endpoint takes. I guessed that it takes the Project Id copied from Secret Managers > Example Project > Settings and that seems to work, but it was not obvious since the terminology differs (I didn't see Workspace noted anywhere in the UI)
The text was updated successfully, but these errors were encountered:
Uh oh!
There was an error while loading. Please reload this page.
Path: /documentation/getting-started/api
The
curl
example in Step 5Get an access token for the Infisical API
points to the hosted Infisical API (https://app.infisical.com/api/v1...
), while Step 6Fetch back secret
points to a localhost URL, presumably for a self-hosted solution:http://localhost:8080/api/v3...
.I would suggest keeping them consistent one way or the other (both pointing to the hosted API URL or both pointing to the self-hosted API URL). I assume the primary consumer reading these docs is trying out the hosted version, so it probably makes sense to use that URL, maybe with a callout underneath about swapping out the base API URL if you're running it locally or self-hosting.
One other point of feedback is a note about the
workspaceId
parameter that the/api/v3/secrets
endpoint takes. I guessed that it takes the Project Id copied fromSecret Managers > Example Project > Settings
and that seems to work, but it was not obvious since the terminology differs (I didn't seeWorkspace
noted anywhere in the UI)The text was updated successfully, but these errors were encountered: