Get API Keys

get

https://Use API Lookup for a base URL/apps/{app}/apiKeys

Lists the API keys generated for an application.

Access Control:

The calling principal must have "read" action permission for the resource "{app}" in the "account" service.
The calling principal MUST NOT include a project scope.

Path Params

app

string

required

HRN identifying the application. Must be URL-encoded, if reserved characters ":/?#[]@!$&'()*+,;=" are used. see https://tools.ietf.org/html/rfc3986#section-2.2.

Query Params

pageToken

string

If there are more records than 'limit' (between 1 and 100), and there are multiple pages of records, 'pageToken' allows for retrieval of individual pages. In order to retrieve subsequent pages, the client should provide the pageToken returned in the result from the previous API call as input to the following API call.

Example: If the result for a call to GET /items returns {..., "pageToken": "abcdefg"}, in order to retrieve the next page of 'items' the client should call GET /items?pageToken=abcdefg

limit

integer

0 to 100

Defaults to 100

Number of records to return. Default is 100 records. Maximum is 100 records.

Headers

X-Correlation-ID

string

Correlates HTTP requests between a client and server. If not present in the incoming request, it will be generated. This header and value will be included in all loglines including access logs. It will also be propagated to downstream services and returned in the response.

X-Request-ID

string

The unique for the request, used to track this request within the service. X-Request-ID value is NOT propagated to the downstream services.

Responses

404

404660 - No app exists with the given id.

429

429003 - Request blocked because of too many requests made. Wait for a while before making a new request.

200OK