igrantio-api-api-keyslisted
Install: claude install-skill L3-iGrant/skills
# iGrant.io OID4VC API - API Keys
## When to use
Use this skill when the task is one of these:
- Make an API key so that a server can call the OID4VCI and OpenID4VP
endpoints without a user session.
- Change the name, the scopes, or the lifetime of a key.
- Delete a key, or list the keys of the organisation.
- Point a key at a sandbox organisation, or back at the main wallet.
An API key replaces a bearer access token on the OID4VC endpoints. Send it as
`Authorization: ApiKey <apiKey>`. The key lives only on the server side, in an
environment variable or a secret manager. The browser never sees it.
## Prerequisites
- An **iGrant.io Organisation Wallet Suite (OWS) API key**. Get it from
[support@igrant.io](mailto:support@igrant.io). Keep it on the server, in
an environment variable or a secret manager. The browser never sees it.
- The **OWS environment** the key belongs to. The default is **demo**
(`https://demo-api.igrant.io`). Use **staging**
(`https://staging-api.igrant.io`) only when the integrator asks for it.
A key works only in its own environment.
## Ask the integrator first
Ask one question at a time. Wait for the answer. Give the recommended
default with each question. Look up facts in the project (framework,
environment variables, an existing backend) instead of asking for them.
Record the answers before you write code.
1. **Environment** - demo or staging? _Default demo
(`https://demo-api.igrant.io`); a switch later is a configuration
change.