API Documentation
Files
Groups
Gateways
x402
Create API Key
Copy
curl --request POST \
--url https://api.pinata.cloud/v3/api_keys \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '
{
"keyname": "A test",
"permissions": {
"admin": true
},
"maxUses": 2
}
'Copy
{
"JWT": "JWT",
"pinata_api_key": "key",
"pinata_api_secret": "secret"
}API Keys
Create API Key
org:write
POST
/
api_keys
Create API Key
Copy
curl --request POST \
--url https://api.pinata.cloud/v3/api_keys \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '
{
"keyname": "A test",
"permissions": {
"admin": true
},
"maxUses": 2
}
'Copy
{
"JWT": "JWT",
"pinata_api_key": "key",
"pinata_api_secret": "secret"
}Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Body
application/json
Name of the API key
Show child attributes
Show child attributes
Provides full access to permissions
Provide an array of scopes in the form org:<RESOURCE>:<PERMISSION>. Resources include files, groups, gateways, and analytics. Permissions are either read or write (write includes read permissions)
Legacy endpoints
These properties are to be used with legacy endpoints, any V3 endpoints should use resources instead
Show child attributes
Show child attributes
Show child attributes
Show child attributes
Response
200 - application/json
OK
The response is of type object.
⌘I