This website uses Cookies. Click Accept to agree to our website's cookie use as described in our Privacy Policy. Click Preferences to customize your cookie settings.
Drupal based developer portals support the concept of companies. It is
frequently used as an abstraction for app ownership. Instead of an app
being directly owned by a single developer, an app can be owned by a
company, and a company administrator ca...
The Apigee Integrated Developer Portal is a quick, simple to use portal
that you can use to document and manage access to your APIs, and foster
your app developer community. It offers a rich set of features such as
self-service registration, auto-gen...
Following on @Kurt Kanaskie's excellent compilation of resource paths
useful for setting custom roles
(https://community.apigee.com/questions/51264/is-there-a-definitive-list-of-resource-paths-for-s.html),
here is a list of resource paths related to ...
100 APIs is probably way too many, especially if there's not a lot of
shared logic amongst them.One way you could split your APIs is to create
new API proxies with more "specialised" basepaths.Eg: If your original
API has /basepath as the basepath an...
Perhaps the simplest way to do this is to require that cliend Id and
secret be sent as a basic authorization header or as form parameters
client_id and client_secret. You can then use the OAuthV2 policy
(operation=GenerateAccessToken, grant type=clie...
Products make it easier to assign different attributes (eg: allocated
quota) to the same APIs. In your example, I'd actually define 3
different products.If, however, you prefer to go ahead and allocate
quotas per client, I'd add custom attributes to ...
You'll need to generate an API Key, and then add it in the x-api-key
header. Once you're more familiar with the platform, you'll find it's
very easy to configure where to get the API key from.Regarding
generating an API Key, you'll need to familiaris...